[
https://issues.jboss.org/browse/JBESB-3578?page=com.atlassian.jira.plugin...
]
Its Me commented on JBESB-3578:
-------------------------------
If you use InXSD instead of OutXSD ( which does seem like the logical approach ), the
project will not deploy.
You'll receive errors that it is unable to load the XSDs. Looks like its trying to
build a URI/path that is based on WSDL, ESB file and the Services category name ( e.g.,
<services category="xxx" ) when deployed. Well, in the project, there is no
directory with the name of the services category name.
To recreate, do the following:
1. Create 3 XSDs, where 1 is the primary and calls the other two XSDs using xs:import.
Each XSD has its own
target namespace. The forum posting provides a sample of what the first XSD should
look like.
2. Create jboss-esb.xml that contains:
- providers
- inbound listener for JMS message
- ESB listener
- services
- <actions inXsd="yourfirst.xsd" validate="true">
- display message using org.jboss.soa.esb.actions.SystemPrintln
3. Send valid and invalid XML into your queue, the message will always.
Take the same example and try it with the other actions noted in the 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:
http://www.atlassian.com/software/jira