Java Web Services and XML
I added a new vendor extension in the JAXB RI to increase the flexibility of JAXB. This change allows applications to lazily load classes into JAXBContext, on-demand.
I started posting the JAXB API jar and the JAXB RI that includes some of the proposed changes in 2.1, so that people can play aorund.
I posted an HTML document that go over some of the key proposed changes in JAXB 2.1 maintenance release
Milestone 1was released last week. The scripts to install WSIT
on this release did
not work because of a change in domain.xml script that was breaking the WSIT
install script (wsit-on-glassfish.xml). I fixed the script and got
report this morning that the fix is indeed working (always fun!).
So if you are you installing WSIT on GlassFish v2 Milestone 1 and it's not
Jitu and I have been prototyping an evolution of the JAX-WS pipeline architecture so that it can scale up to 100,000s of concurrent requests, or work nicely with commet-style message processing often see in the AJAX world.
1 release has been available for a few days now.
Follow 4 simple steps
to download the binary release or build from the source and build a secure,
reliable and interoperable Web service using the comprehensive tutorial.
The samples range from simply adding the two numbers to a price
quote service using secure, reliable and brokered trust pattern. All the
samples can be installed...
As of Aug 14, 2006, java.net community has
262,445 members and growing. Each of these members can check out any of the 3131
projects (as of 8/14) and view the underlying source code, web pages and other
content. There are numerous benefits
to become a java.net member. I definitely encourage you to join
the community but in case you choose not to, you can still check out the the
JAXWS 2.0.1 M1 a.k.a. re-architected JAXWS 2.0 RI is out. It brings in major performance improvements and pluggability support...
JAX-WS RI 2.0.1 enables easy monitoring of SOAP Messages transmitted between Client applications and Web Service without changing anything in the client application code.
Updated set of properties are available here.
THE FOLLOWING PROPERTIES ARE PROPRIETARY. THEY CAN AND WILL CHANGE.
We are providing this information to help with development and debugging.
These properties should not be used in deployments.
Assembler exposes multiple system properties to enable SOAP message logging using
Each property, if it's value is set to...
I've started working on the JAXB 2.1 maintenance review (I took over the spec work from Sekhar.) I'm still trying to get up to speed with the process and all, and I hate the UI of FrameMaker, but in the mean time, I posted all change proposals at java.net.
The idea of an MR is that we'd like to make selected easy changes to address the pain of users and technologies that build on top of the...
Edit distance computation, or how the CS undergraduate education is sometimes actually useful.
NetBeans 5.5 with its built-in support for JAX-WS Web Services also provides a nice GUI to customize WSDL to Java bindings easily. All it takes is a few clicks as shown in this blog.
This tool, wsmonitor, is a light-weight, easy to use SOAP and HTTP
traffic monitoring tool. This tool uses port forwarding to capture the SOAP
messages and HTTP headers between a sender and a receiver and displays them
nicely formatted in a graphical user interface. The key features are:
Easy to use
Displays XML- formatted SOAP message
Separate tabs for SOAP and HTTP traffic...
Do you know what's in the WebSphere feature pack for web services?
The JAXP API defines a pluggability layer which allows easy swapping of implementations via the use of system properties and meta-information stored in JAR files. I have recently found that the mechanism by which factory classes are located and loaded still causes a great deal of confusion. I've recently cleaned up this code in JAXP 1.4, available as part of J2SE 6.0 (Mustang), and decided to write a blog explaining how this works.
In my last
blog entry, I described how WS-Addressing Action header value is calculated.
A WSIT-enabled client/endpoint generates/expects the
correct values per W3C Candidate Recommendation. However Microsoft's WCF
(Windows Communication Foundation) client does not
generate the correct value of Action header in all cases. This blog describes
the issue and workaround.
As described in...
WSDL Binding defines
the sequence to follow in order to calculate the value of Action header to be
sent in a client outbound SOAP message or expected in a server inbound SOAP
message. The sequence is explained below:
If wsaw:Action is explicitly
associated with wsdl:input message, then use that. For
An updated WADL specification is now available, here's what's new.
I just posted a new release of the JAXB RI, which is 2.0.2.