Web services give you the possibility of loosely coupling your different IT-systems. At least on the paper it seems that you can interchange either the client or server easily.
Only after having changed either part for the first time you might realize that a new Web service implementation on one side means redeveloping also the other.
Main post:
When working with the Webservice stack of JBoss you will have to check on the version you are using, as there has been some changes over the years :
http://community.jboss.org/wiki/WebServiceStacks
| Name | File | JBoss Version | Status | Supported API | Based on |
| JbossWS-3.x | JbossWS Native 3.1.2.SP3-patch-02 jbossws.sar | 5.0+ | JEE 6 | JAX-WS | |
| Apache CXF (not shipped with EAP) 3.1.2.SP3 | 5.0+ | Supported | JEE 6 (1) | JAX-WS | |
| GlassFish Metro (not shipped with EAP) | 5.0+ | JEE 6 | JAX-WS | ||
| JBossWS-2.x sources binaries | jbossws.sar (2.0.1.SP2_CPxx) | EAP 4.3 CPxx | ??? | JEE 5 | JAX-WS |
| JBossWS-1.x | jbossws.sar (1.2.1.GA_CPxx+) | EAP 4.2 CPxx | ??? | JEE 5 | JAX-WS (2) |
| JBossWS4EE | jboss-ws4ee.sar | < 4.0.4 | Maintenance Only | J2EE 1.4 | Axis |
| JBoss.NET | jboss-net.sar | 3.2.x | End of Life | Proprietary | Axis |
(1) JDK 1.6 incorporates the JAXB reference implementation. However, it incorporates an old version of the RI. CXF does not support this version. As of 1.6_04, this is easy to deal with: you must put the versions of JAXB RI (the 'impl' and 'xjc' jars) that we include with CXF in your classpath. As of this writing, these are version 2.1.6.
(2) Yes, JAXWS ... are supported all together starting from JBossWS-1.2.0.GA. Link
(2) Yes, JAXWS ... are supported all together starting from JBossWS-1.2.0.GA. Link
This table was build upon http://community.jboss.org/wiki/WebServiceStacks, http://community.jboss.org/wiki/JBossWS, http://community.jboss.org/wiki/JBossWS-Installation and notes from Alessio Soldano
No comments:
Post a Comment