See https://jira.jboss.org/jira/browse/JBWS-1439 for more details, but essentially, there are some classpath issues with an out of the box JBoss 4.2.x and jdk6 when trying to use JBossWS (Implementation of JAX-WS stack in JBoss Application Server.)
If you run into these problems, there is a simple fix. Copy the conflicting jars into the endorsed directory:
cp -t $JBOSS_HOME/lib/endorsed $JBOSS_HOME/server/all/lib/jboss-jaxrpc.jar \ $JBOSS_HOME/server/all/lib/jboss-saaj.jar
Fixing the wsdl soap address brokenness
Another problem you might run into is that the default wsdl generated will end up using whatever hostname JBoss thinks it is. This is not necessarily the hostname that is accessible remotely.
To get around this, modify:
$JBOSS_HOME/server/$instanceName/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml
By commenting out the webServiceHost property in WSServerConfig