Java Web Services and XML
Sun's Project Tango is now out in the wild. Come see us at JavaOne.
Read more about it. Try it out. Talk with us. Help develop it.
See the Early Access catalog solutions for programming business processes in BPEL, with more to come.
The JAX-WS 2.0 RI final release is now available on java.net.
JAXB 2.0 (JSR-222) has passed the JCP final approval ballot. That means it's ready to ship!
JAX-WS provides a pluggable framework to extend the runtime processing capabilities through handlers. Handlers are message interceptors that can do pre-processing/post-processing of the messages to complement your Web Service. JAX-WS defines two types of handlers, logical handlers and protocol handlers. Protocol handlers are specific to a protocol and may access or change the protocol specific aspects of a message. Logical handlers are protocol-agnostic and act only on the payload of the message.
I made improvements to the java.net maven repository daemon, so that more Sun jars can be posted.
Following JAXB jars in the maven repository, we pushed SAAJ and JAX-WS API jar and the RI to the maven repository.
POMs of those jars are written in haste, so if you find any mistake (in particular in its dependencies), please let me know so that we can fix it.
I hope you Maven users out there...
As you may know, JAX-WS supports the W3C Message Transmission Optimization Mechanism (MTOM) to accelerate the transmission of binary payloads in XML messages. With MTOM, binary data is transmitted as MIME attachments to avoid the expensive base64 encoding. How much faster is MTOM in practice? When should I use MTOM then? I'll take the latest JAX-WS for a spin in an attempt to answer these questions.
I have created an object to pass dynamic data to and from Web Services. I am blogging it because I want to know how others feel about this type of object.
Versioning of Web Services is difficult with many different factors to consider, which is beyond the scope of this blog. Lets say it is safe to say that you need to make Web Services backwards compatible for as long as possible. To do...
Sometimes, Invoking Web Services require exchange of additional information or metadata. This metadata forms the context of message exchange. Few of the common questions I hear while creating Web Services using JAX-WS are, how do I convey this metadata with other parts of the application and how do I configure the binding to behave in a certain way.
I downloaded and installed Glassfish
build. This is the first time I'm downloading and installing Glassfish on my
machine so here is my experience so far.
Ignoring the installation instructions (with a "I know it"
attitude) and realizing the downloaded bundle extension is ".jar"
I ran the install command as:
java -jar glassfish-installer-9.0-b42....
JSR 224 (JAX-WS) was approved yesterday! You can view the result on the
The Java Community Process(SM) Program - JSRs: Java Specification Requests - results
JAX-WS is part of the Glassfish Project
One thing people often get confused about JAXB is with respect to how it handles classes that derive from your base class. Today, I'm going to shed some light on it.
Project Tango is a Sun initiative focused on delivering interoperable Web services technologies. Web Services Interoperability Technology (WSIT) is an open-source implementation of next generation Web services technologies that deliver interoperability between Java EE and .Net to help you build, deploy, and maintain Composite Applications for your Service Oriented Architecture. It is focused on four main categories: Messaging, Metadata, Security, and Quality-of-Service (QoS).
John Yates wrote an great article on JAX-WS. He does a very good job of describing the architecture of JAX-WS and how to use JAX-WS.
The JAX-RPC sources for Glassfish are now on Java.net. This repository will now be actively used for all JAX-RPC work going into Glassfish.
Let me talk about a little technique to make your JAXB life little easier...
The Sun Java Streaming XML Parser (SJSXP) FCS version 1.0 is now available in binary and source forms from Java.net. This parser is an implemenation of JSR 173, submitted to the JCP by BEA. We liked this parser and the StAX API so much that we've made it a key component of our Web services stack in Glassfish. I'd like to share with you some pointers where you can find the implementation and also talk briefly about performance.
Welcome Bhakti to blogosphere.
And quite an impressive way to start the blog by explaining the WS-Reliable
Messaging protocol, defining stack and developer responsibilities in Project
Tango, delivery vehicle and updates from the WCF
WS-Reliable Messaging source and binaries will be available on java.net
with support for Glassfish.
Technorati: Web Services
In the real world, challenges are encountered in delivering messages. There can be network/connection problems.
Consequently, messages can be lost or delivered out of order. Web Services Reliable Messaging (WS RM) provides a mechanism
to ensure a layer of reliability between potentially unreliable or intermittently connected networks.
WS-I Testing Tools determine conformance with WS-I
Basic Profile 1.1 (BP 1.1) and Simple
SOAP Binding Profile 1.0 (SSBP 1.0). The testing tools download bundle comes
with two tools that facilitate the
process, they are Monitor and Analyzer. The bundle comes with a
command-line version of these tools but for easier integration with Ant
build scripts, ant
tasks for these tools is available here....