Products | Versions |
---|---|
TIBCO BusinessEvents Enterprise Edition | 6.1.1, 6.1.2, 6.1.2, 6.2.x, |
"Unable to resolve getByExtId" or "Caused by: java.lang.RuntimeException: Function Instance.getByExtId not found. Try validating project before building." or "java.lang.Exception: Error while building EAR"
Open the pom.xml and look for the field: <useLegacyId/>, should see the flag in disabled state, like below:
Disabled state: <configuration> <beProjectDetails> <beHome>/opt/tibco/be/6.2</beHome> <useLegacyId/>Also, the Legacy property in studio.tra file at
BE_HOME/studio/eclipse/configuration
, might be commented out:
# Uncomment below properties to change to Legacy ID mode #be.engine.id.useLegacy=true #TIBCO.BE.function.catalog.getbykeys=false
To fix the issue change the pom.xml to enable legacy id field using the field <useLegacyId>true</useLegacyId>, like below:
Enabled state: <configuration> <beProjectDetails> <beHome>/opt/tibco/be/6.2</beHome> <useLegacyId>true</useLegacyId>
Regenerate the pom.xml.
For studio-tools you need to set the following property in studio-tools.tra for the legacy id usage to be enabled.
java.property.be.engine.id.useLegacy=true
Build should work.
If Legacy property is commented, go to studio.tra file at BE_HOME/studio/eclipse/configuration
and ucomment it:
# Uncomment below properties to change to Legacy ID mode be.engine.id.useLegacy=true #TIBCO.BE.function.catalog.getbykeys=falseThis avoids any Legacy lookup strategy issue in Studio IDE.
TIBCO BusinessEvents® Enterprise Edition 6.2.1 Architects Guide: Storage and Retrieval of Entity Objects - Data Lookup Strategies.
https://docs.tibco.com/pub/businessevents-enterprise/6.2.1/doc/html/Architects-Guide/Data-Lookup-Strategies.htm