Schema migration issues from BE 5.x to BE 5.1.2
Article ID: KB0089060
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Description:
There were schema issues reported after migrating the project to BE 5.1.2 where some of the schemas are not available while referencing them in the events.
Symptoms:
Building EAR with Studio–tools might fail in 5.1.2 because of schema validations at design time and conflicting schemas will appear in warnings section of the problems view.
Cause:
The reason being, in 5.x.x conflicting schemas were not validated, often masking run-time issues. Where as in 5.1.2, there is a design-time validation for conflicting schemas and will ignore the conflicting schemas.
There were schema issues reported after migrating the project to BE 5.1.2 where some of the schemas are not available while referencing them in the events.
Symptoms:
Building EAR with Studio–tools might fail in 5.1.2 because of schema validations at design time and conflicting schemas will appear in warnings section of the problems view.
Cause:
The reason being, in 5.x.x conflicting schemas were not validated, often masking run-time issues. Where as in 5.1.2, there is a design-time validation for conflicting schemas and will ignore the conflicting schemas.
Issue/Introduction
Schema migration issues from BE 5.x to BE 5.1.2
Resolution
Verify your conflicting schemas by going to the Problems View in the Studio and checking for warnings. These warnings will clearly specify the conflicting schema’s information. Usually the Target Namespace should be unique so that BusinessEvents understands the targeted Schema elements. If you have duplicate Target Namespaces then Studio will show a warning and the conflicting schemas will be ignored. Make sure that the Target Namespaces in your Schemas are unique.
Feedback
Yes
No
Powered by
