[esb-issues] [JBoss JIRA] Created: (JBESB-3029) JBoss4ESBDeployer: does not support schema imports/includes for exploded archives.
JBoss4ESBDeployer: does not support schema imports/includes for exploded archives.
----------------------------------------------------------------------------------
Key: JBESB-3029
URL: https://jira.jboss.org/jira/browse/JBESB-3029
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.6
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.8
Jeff DeLong reported this issue to me. Thanks Jeff!
When deploying a .esb archive exploded the schema imports/includes do not work. This is
because the getSchemas() method in JBoss4ESBDeployer cannot handle a deployment that is a
'-esb.xml' file but instead currently only handles directory or a zip archived
ending with '.esb'.
We need to add support for deployments of exploded archives where the deployment
deployment file is a '-esb.xml' file.
This can be seen by running the publish_as_webservice quickstart:
ant -Ddeploy.exploded.requested=true deploy
As a solution we could for example add the following to getSchemas() in
JBoss4ESBDeployer:
final String fileName = file.getName();
if (fileName.endsWith(".esb"))
return getSchemasFromArchive(file);
if (fileName.endsWith("-esb.xml"))
{
final File metaInf = file.getParentFile();
final File deploymentRoot = metaInf.getParentFile();
return getSchemasFromDirectory(deploymentRoot);
}
--
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