[
https://jira.jboss.org/jira/browse/JBESB-3281?page=com.atlassian.jira.plu...
]
Daniel Bevenius commented on JBESB-3281:
----------------------------------------
AS 5.1.x
The schemas are found and added but the paths to them are incorrect. For example, I have
put schemas in a jar name schemas.jar which exist in the jars directory of a esb
deployment. The schema path added then becomes:
path=Quickstart_publish_as_webservice.esb/jars/schemas.jar/types/custom-request-type.xsd
Perhaps the simplest solution should be to cut off the path from the vsf root
(Quickstart_publish_as_webservice.esb above) to the jar (schemas.jar above).
EBWS: Add support for schemas that exist in jar inside of .esb
archives
-----------------------------------------------------------------------
Key: JBESB-3281
URL:
https://jira.jboss.org/jira/browse/JBESB-3281
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Rosetta, Web Services
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Currently the schemas in an .esb deployment can be located in a directory in the .esb
archive. But there is no support for schemas that exist in jars in the deployment.
This task should add support for having schemas in jar files.
For AS 4.2.x JBoss4ESBDeployer needs to support this.
For AS 5.1.x it should enough to drop the jar containing schemas in any directory
configured as a classpath for the deployment of .esb archives (by default the lib and jars
directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira