Originally posted by Eugene Abarquez:
Does this work with Cold Fusion too?
In principle it should, however it depends on which specifications the web service complies with. In general web services are nothing more that XML transmitted via HTTP -
SOAP web services also use the SOAP which itself is XML-based. Problems usually arise when the service uses some encoding-scheme that cannot be expressed in terms of XML Schema, i.e. some additional information is needed on top of the XSDs and WSDL in order to make sense of the data. Another source of problems is when a web service tries to force programming-language specific constructs into the data - constructs that may not necessarily have an equivalent in the client's programming language. As long as everybody treats it simply as an
exchange of XML documents everything should be fine.
Originally posted by Eugene Abarquez:
I've read JDOM is a good option. Is it? Or will I be better off using JAXB?
Whatever you can justify.
JDOM is a java-fied version of DOM and you have to write the code to build and read the XML documents. JDOM is supposed to be easier to use than DOM but will never be part of core Java.
JAXB generates the marshalling and de-marshalling code for you based on the XML schema that you supply. You can further influence the code generation through configuration files. JAXB 2.0 will be part of core Java starting with version 6. The current reference implementation works with version 5. JAXB 1.0 works with version Java version 1.4 and the necessary jars of the reference implementation can be extracted from any JWSDP 1.x (jaxb-api, jaxb-impl, jaxb-libs, jaxb-xjc, relaxngDatatype, xsdlib).
But then again you may not need to work with the XML directly.
JBoss WS module seems to be based on Apache Axis:
JBoss: J2EE Web Services
JBossWS