JWS (Java Web Services) 2.1 updates JAXB and JAX-WS to 2.1 and adds WSIT to its basic layer. Now JWS 2.1 is supported by GlassFish v2 while JWS 2.0 is built in JDK 6.
One typical issue is definitely how to use JWS 2.1 on JDK 6. It's well known that you can rely on Standard Endorsed Mechanism provided by Java SE, how about updating JWS from 2.0 to 2.1 for JDK 6u1?
I started to read http://www.netbeans.org/kb/55/beginning-jni-part1.html and soon realized that the article was for Windows while my main development machine is Ubuntu. OK, so it means that I don't need to install cygwin and the rest of the instructions in the article should work fine, right? (Un)fortunately, you need more than the difference in case you're a unixer (including Mac OS X).
Maybe I need to post these issues to GF or JAX-WS projects, but would like to share first with this blog.
I simply wanted to demonstrate a service exposed as both SOAP and REST.
1. Firstly, I started with GlassFish V2 M2 with JAX-WS 2.1M1.
After introducing "Java Web Services 2.0" at http://weblogs.java.net/blog/iasandcb/archive/2006/03/java_web_servic.html, I made up my mind to broaden the notion :-)
First of all, I felt I had to revise JWS 2.0 because JAX-WS 2.1 and WSIT came up. JWS 2.0 is a set of:
JAXB 2.1 + JAX-WS 2.1
Secondly, .NET Web Services 2.0 is WCF in .NET framework 3.0.
I have to admit that this combination, Windows PDA and Java ME, isn't that easy to approach in terms of both quality and quantity. Firstly, there isn't so-called "RI (Reference Implementation)" of CLDC or CDC on the (obviously) hostile platform against Java.
While reading NetBeans 5.5 Beta 2 Release Information at http://www.netbeans.org/community/releases/55/index.html, I found that (Java) Web Services 2.0 was used to introduce JAX-WS.
Although the line left "Java" out, I felt really glad to see the term as I suggested at my previous blog at http://weblogs.java.net/blog/iasandcb/archive/2006/03/java_web_servic.html.
I got so much feedback from my recent blog at http://weblogs.java.net/blog/iasandcb/archive/2006/06/serializing_xml.html, and it inspired me to write another.
The most noticeable comment on the blog is to use JAXP transformer to serialize Document, and in fact I couldn't agree on the solution more because I also used it.
TmaxSoft (yes, where I work now) achieved it (of course except the Sun RI :-). See http://java.sun.com/javaee/overview/compatibility.jsp for more details. We are planning to release some preview as well.
Thank you all for your great help, especially Alan, Arthur, and Stephen from the Sun CTS team. I couldn't forget such a beautiful weather in Boston.
P.S. More about this to come, so stay tuned!
Suppose you have an org.w3c.dom.Document instance to output, for example, to a web browser screen or just simply on a Console, then hmm... unfortunately, we used to have no standard way within DOM API (used, not now).
You can download it from https://jaxb.dev.java.net/tck.html . It's still beta, but I hope we can see a final version as JAXB 2.0 spec and RI is also finalized (very soon).