U're right Carlo!
So any objections / comments if we'd change
these DU processors to include these dependencies?
This is general DU classpath setup problem :(
Rio
On 02/15/2011 12:23 PM, Carlo de Wolf wrote:
This is the web equivalent:
https://github.com/jbossas/jboss-as/blob/master/web/src/main/java/org/jboss/as/web/deployment/WarClassloadingDependencyProcessor.java
Carlo
On 02/15/2011 12:20 PM, Carlo de Wolf wrote:
I agree with the use cases, but I would rather see test cases to
support them.
You are in fact putting them in the wrong location. For an user
deployment to see those modules they need to be added to https://github.com/wolfc/jboss-as/blob/ejb3-domain/ejb3/src/main/java/org/jboss/as/ejb3/deployment/EjbDependencyDeploymentUnitProcessor.java
This branch is still in experimental stage.
Carlo
On 02/15/2011 12:04 PM, Richard Opalka wrote:
I'd
like to change the following AS7 modules
org.jboss.as.web
org.jboss.as.ejb3
to include the following dependencies
<!-- JSR 181 WS MD -->
<module name="javax.jws.api"/>
<!-- JSR 224 JAXWS API -->
<module name="javax.xml.ws.api"/>
<!-- JBossWS SPI -->
<module name="org.jboss.ws.spi" />
<!-- CXF META-INF servicies -->
<module name="org.jboss.ws.cxf.jbossws-cxf-factories"
services="import"/>
<!-- CXF JAXWS API impl -->
<module name="org.jboss.ws.cxf.jbossws-cxf-client"
services="import"/>
It's required by JAX-WS 22 & EE6 specs and TCK to have
JAX-WS client runtime available in Servlets and EJBs
automatically.
I'm also attaching some usecases to demonstrate usecases.
Objections / comments ?
Rio
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Richard Opalka
ropalka@redhat.com
JBoss, by Red Hat
Office: +420 222 365 200
Mobile: +420 731 186 942