sorted by: recent | see :
popular
Content Tagged with JAX-WS + WSIT
Bidirectional / Callback Service
GlassFish Web Services Stack Tango with JavaSE6
|
The Web services stack in GlassFish V2 uses JAX-WS 2.1 and JAXB 2.1 as the core Web services platform. WSIT extends this core by providing an implementation of key WS-* specifications. Since JavaSE 6 has Web services support through the JAX-WS 2.0 and JAXB 2.0 specifications, it allows to build basic Web services using only JavaSE 6 but does not have any of the WSIT capabilities. But now that's possible! Fabian explained how a WSIT endpoint be easily deployed using the JAX-WS Endpoint API. In a follow up post, I provide a detailed writeup with complete working code. |
GlassFish Web services stack "tango" nicely on Tomcat, Jetty and JavaSE 6.
Stateful Web services Magic in GlassFish
|
TheServerSide is excited about the Stateful Web services support in GlassFish. Here is a quote from a recent article It's almost magical how easy the code is, to use a stateful SOAP service in this manner. Another user commented: Looks as great as Microsoft breaking 8+3 limit in filenames. |
Stateful Web services support in JAX-WS 2.1 were announced last year and customers have found the programming model dead simple. This extension to JAX-WS RI uses WS-Addressing behind the scene to maintain multiple instances of a service. And because a key goal of Project Tango's is to be interoperable with Microsoft .NET 3.0 framework, this support is interoperable as well. You can see the complete sever-side code on JAX-WS and client-side code on .NET 3.0 in an entry linked from Kohsuke's detailed entry.
Post a comment/question at JAX-WS forum if you would like to see more improvements in this area.
Now also on Jetty... the GlassFish Web Services stack
|
One of the principles of GlassFish is to encourage the adoption of its components, and, as part of that, we attempt to make those components portable. Vivek had already reported that JAX-WS 2.1 only depended on Servlet 2.4 and would run on Jetty (and others), and now Arun provides the specific instructions to achieve this, including the WSIT/Tango features. |
Ask the Experts Session on WSIT and Project Tango
|
Ask the Experts (April 30-May 1): WSIT and Project Tango.
Post it during this session from April 30 to May 4 on the Ask the Experts page and get answers from Sun experts Arun Gupta, Harold Carr, and Marek Potociar. |
websvc: Web Services Interoperability Technology (WSIT)
Vivek Pandey's Blog: MTOM in JAXWS 2.0 RI EA3
//get the binding and enable mtom
bookmark this on del.icio.us
-
posted
by seamus7delicious
to
jax-ws
MTOM
wsit
- more about this bookmark...
Harold Carr's Blog
Harold Carr is the engineering lead for enterprise web services interoperability at Sun Microsystems - enabling atomic transactions, reliable messaging and security between Java and Windows Communications Foundation.
Harold Carr's Blog
wsit: Project Tango
JAX-WS: del.icio.us/tag/jax-ws
microsoft
webservices
sun
jax-ws
interoperability
interop
WSIT
Why would I need to be reliable?
|
Hopefully, this is not going to start a REST vs. WS-* debate, but there are a few arguments from the WS-* side which usually RESTafarians agree to:
|
You may not need any of the above (in which case a RESTful approach may be more appropriate), but you if think you need reliability, Mike Grogan has a nice and short explanation on why you would want to use WS-ReliableMessaging and how the developer is impacted when using WSIT, the JAX-WS extension for many WS-* specifications.
WSIT is now in Milestone 3 which works with GlassFish 2 b33c. Install is described here. WSIT M3 is also the build that will be part of the upcoming GlassFish v2 beta release.
Note also that Arun is running a series of nice ScreenCasts for GlassFish JAX-WS and WSIT. The latest one is also about WS-ReliableMessaging.
messaging
reliable
glassfish
jax-ws
WSIT
ws-rm
reliablemessaging
