This content has been marked as final.
Show 2 replies
-
1. Re: WSConsume does not support JAX-WS 2.1 with JBossWS 3.0.5
asoldano Apr 28, 2009 11:58 PM (in response to joshua.dev)I'd need to double check what was available in AS 4.2.2, I think the -t 2.1 option was later disabled because the implementation of JAX-WS 2.1 was not complete yet.
For sure you can use the 2.1 target starting from JBossWS Native 3.1.0.GA as the JAX-WS 2.1 has been completed there.
Otherwise (if you cant move to AS 4.2.3 which is the oldest target container supported by JBossWS 3.1.0) try with JBossWS-Metro 3.0.5, which already had full JAX-WS 2.1 impl. -
2. Re: WSConsume does not support JAX-WS 2.1 with JBossWS 3.0.5
joshua.dev Apr 29, 2009 2:13 AM (in response to joshua.dev)Thank you for the answers. I've decided to step back and use JAX-WS 2.0, hopefully integration with external parties won't be a problem.
"alessio.soldano@jboss.com" wrote:
I'd need to double check what was available in AS 4.2.2, I think the -t 2.1 option was later disabled because the implementation of JAX-WS 2.1 was not complete yet.
I am sure I used the "-t 2.1" switch on default install of AS 4.2.2.GA."alessio.soldano@jboss.com" wrote:
For sure you can use the 2.1 target starting from JBossWS Native 3.1.0.GA as the JAX-WS 2.1 has been completed there.
Otherwise (if you cant move to AS 4.2.3 which is the oldest target container supported by JBossWS 3.1.0) try with JBossWS-Metro 3.0.5, which already had full JAX-WS 2.1 impl.
I'll probably have to stay with 4.2.2 now, but I'll take the information about working WS 3.1.0 and JAX-WS 2.1 into accound when I'll be considering AS upgrade.
The Metro stack was giving me some problems after deployment, I briefly went through the exceptions' stacks but had no time to figure out what exactly went wrong.