No, not generally. If its needed you would have to use a META-INF/jboss-structure.xml to instruct the structure deployers to add it. You then have to specify the complete classpath though. Don't know if the latest classloading deployers have a simpler syntax for this.

<structure>
 <context>
 <path name=""/>
 <metaDataPath>
 <path name="META-INF"/>
 </metaDataPath>
 <classpath>
 <path name=""/>
 <path name="lib" suffixes=".jar"/>
 </classpath>
 </context>
 <context>
 <path name="jbosstest-web.war" />
 <metaDataPath>
 <path name="WEB-INF"/>
 </metaDataPath>
 <classpath>
 <path name="jbosstest-web.war/WEB-INF/classes"/>
 <path name="jbosstest-web.war/WEB-INF/lib" suffixes=".jar"/>
 </classpath>
 </context>
 <context>
 <path name="wars/notjbosstest-web.war" />
 <metaDataPath>
 <path name="WEB-INF"/>
 </metaDataPath>
 <classpath>
 <path name="wars/notjbosstest-web.war/WEB-INF/classes"/>
 </classpath>
 </context>
 <context>
 <path name="jbosstest-web-ejbs.jar" />
 <metaDataPath>
 <path name="META-INF"/>
 </metaDataPath>
 <classpath>
 <path name="jbosstest-web-ejbs.jar"/>
 </classpath>
 </context>
 <context>
 <path name="cts.jar" />
 <metaDataPath>
 <path name="META-INF"/>
 </metaDataPath>
 <classpath>
 <path name="cts.jar"/>
 </classpath>
 </context>
 <context>
 <path name="websubdir/relative.jar" />
 <metaDataPath>
 <path name="META-INF"/>
 </metaDataPath>
 <classpath>
 <path name="websubdir/relative.jar"/>
 </classpath>
 </context>
 <context>
 <path name="scripts/security-config-service.xml" />
 </context>
</structure>

This looks like a problem with the new SARDeployer.

 protected ServiceDeployment parse(VFSDeploymentUnit unit, VirtualFile file, Document document) throws Exception
 {
 ServiceDeploymentParser parser = new ServiceDeploymentParser(document);
 ServiceDeployment parsed = parser.parse();

 InputStream is = openStreamAndValidate(file);
 Object parsed = null;
 try
 {
// HERE Doesn't know the file url
 parsed = unmarshaller.unmarshal(is, resolver);

"scott.stark@jboss.org" wrote:
No, not generally. If its needed you would have to use a META-INF/jboss-structure.xml to instruct the structure deployers to add it. You then have to specify the complete classpath though. Don't know if the latest classloading deployers have a simpler syntax for this.

"adrian@jboss.org" wrote:
This looks like a problem with the new SARDeployer.

 InputStream is = openStreamAndValidate(file);
 try
 {
 DocumentBuilder parser = getDocumentBuilderFactory().newDocumentBuilder();
 InputSource source = new InputSource(is);
 source.setSystemId(file.toURI().toString());
 parser.setEntityResolver(new JBossEntityResolver());

// HERE it passes the stream instead of the source :-)
 return parser.parse(is);

Bug report: http://jira.jboss.com/jira/browse/JBDEPLOY-47

"adrian@jboss.org" wrote:
Bug report: http://jira.jboss.com/jira/browse/JBDEPLOY-47

"alesj" wrote:

"adrian@jboss.org" wrote:
Bug report: http://jira.jboss.com/jira/browse/JBDEPLOY-47

What would a test for this look like?

<ejb-jar xmlns="whatever" xmlns:xi="http://www.w3.org/2001/XInclude">
 <xi:include href="included.xml"/>
</ejb-jar>

<enterprise-beans>
...

In JBossXBHelper, should I change the code this way:

 //parsed = unmarshaller.unmarshal(is, resolver);
 parsed = unmarshaller.unmarshal(file.toURL().toString(), resolver);

I 'missing' better stream handling in both JBossXBHelper parse methods.
Since we're going 'around the corner' to get what we already have at that point - a file and its stream.
Since if we pass in URL, it's probably some code deeper in unmarshaller that opens connection/stream on top of that vfs's url, meaning it goes all the way to recreating whole vfs structure ...

Jaxb and jaxp deployers already have this done via (Input|Dom)Source.

Should I open JBossXB issue?

Yes, I didn't know it would use systemId as the base for entity resolutions when InputStream/Reader is passed in.

I've now have this:

<jboss-include xmlns="urn:jboss:include:1.0" name="mymetadata" xmlns:xi="http://www.w3.org/2001/XInclude">

 <jboss-test>test1</jboss-test>
 <xi:include href="included.xml"/>

</jboss-include>

<?xml version="1.0" encoding="UTF-8"?>
<jboss-test>test2</jboss-test>

Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: jboss-test not found as a child of {urn:jboss:include:1.0}jboss-include
 at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:201)
 at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:181)
 at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:190)
 at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:164)
 at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132)
 at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118)
 at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:185)
 at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:336)

@JBossXmlSchema(namespace="urn:jboss:include:1.0", elementFormDefault=XmlNsForm.QUALIFIED)
@XmlRootElement(name="jboss-include", namespace = "urn:jboss:include:1.0")
@XmlType(
 name="includeType",
 namespace="urn:jboss:include:1.0",
 propOrder={"others"}
)
public class IncludeMetaData implements Serializable
{
 /** The serialVersionUID */
 private static final long serialVersionUID = 1L;

 private String name;
 private List<TestMetaData> others;

 public String getName()
 {
 return name;
 }

 @XmlAttribute(required = true)
 public void setName(String name)
 {
 this.name = name;
 }

 public List<TestMetaData> getOthers()
 {
 return others;
 }

 @XmlElement(name = "jboss-test")
 public void setOthers(List<TestMetaData> others)
 {
 this.others = others;
 }
}

@JBossXmlSchema(namespace="urn:jboss:mytest:1.0", elementFormDefault=XmlNsForm.QUALIFIED)
@XmlRootElement(name="jboss-test")
public class TestMetaData implements Serializable
{
 /** The serialVersionUID */
 private static final long serialVersionUID = 1L;
 private String name;

 public String getName()
 {
 return name;
 }

 @XmlAttribute(required = true)
 public void setName(String name)
 {
 this.name = name;
 }
}

Maybe the namespace in the included.xml?