Webservice as WAR vs. EJB3

[dode]

Can someone please help me out, I am a bit confused.

I am using JBossAS 4.0.5. When I deploy my webservice as WAR it uses JAX-WS (and works just fine), but when I deploy it as EJB3 in a JAR it uses JAX-RPC (and does not work since I use Collections).

I assume this is intended, but why?

The reason why I tried this is, that I plan to deploy a webservice in a clustered JBossAS setup while all nodes should be able to access the same shared data, and I was wondering if that could be accomplished by deploying the webservice as a clustered, stateful EJB3. Probably great nonsense... any suggestion?

Torsten

[dode]

Sorry, I just figured that all I have to do is to update my JBossAS 4.0.5 to jbossws 2.0.1... now my EJB3 is also using JAX-WS. Very nice!

Now I just need to figure out if it makes sense at all to deploy a webservice as stateful clustered bean. Have to learn about EJB3 but if someone could point me in the right direction I'd be grateful.

Torsten