You should only deploy portable artifacts (i.e. beans, mapping.xml)
Scan the generated output for com.sun. you won't need any of those
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4016643#4016643
Reply to the post :
akirainoue,
I've got exactly the same problem, running on JBoss 5.0.0.Beta.
This answer seems to suggest, you could use jboss client stack instead of jwsdp:
http://www.jboss.com/index.html?module=bbop=viewtopict=76440
Did you find any other solution to the problem?
View the original post :
Depending on how your client is packaged (EAR, JAR, WAR), you could scope your
deployment to prevent this, but as mentioned, the best alternative would be to
use JBossWS instead.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4015090#4015090
Reply to the post
