Heiko - any update ? :)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157321#4157321
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157321
___
jboss-user mailing list
jboss-u
So are these two jars ever needed at *runtime* or *compiletime* for users
applications ?
The question is if our AS runtime adapter should explicilty excluded these jars
when being asked which jars should be available to a WAR or EJB project.
View the original post :
http://www.jboss.com/index.
So, conceptually you start with two different classpath settings, depending on
the use case.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155883#4155883
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155883
_
It's the JAXWS API that uses a service loader mechanism to pull the
implementation. You have to make sure that WS invocation don't have the Sun API
(jaxws-rt.jar, jaxws-tools.jar, jaxws-api.jar) on the classpath. JBossWS ships
with it's own impl. of the API wich then delegates to the correct pro
