]
Kevin Conner commented on JBESB-3578:
-------------------------------------
1 - You didn't specify in inXsd so there is nothing to validate against
2 - Already done via JBESB-3538 (in SOA 5.1)
3 - Please provide test case attached to this jira
JBoss ESB validation methods buggy/inconsistent
-----------------------------------------------
Key: JBESB-3578
URL:
https://issues.jboss.org/browse/JBESB-3578
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Environment: Operating System: ANY
Application : JBoss SOA 5.0.2
Reporter: Its Me
So it looks like all of the validation code with JBossESB actions have issues with some
basic operations:
1. <actions mep="OneWay" outXsd="/validate0.xsd"
validate="true">
- No matter if the inbound XML is valid or invalid, the actions are execute and
change in
execution occurs. All actions occur, regardless.
2. SchemaValidationAction
- Does not correctly read XSD that contain <xs:import> statements. ESB will
not be
deployed correctly.
3. XsltAction
- No matter if the inbound XML is valid or invalid, the actions are execute and
change in
execution occurs. All actions occur, regardless.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: