JSR 261 (Java API for XML
Web Services Addressing, JAX-WSA) has been operating
under the assumption that it would layer on top of JAX-WS
2.0 (JSR 224). This enabled us to provide WS-Addressing functionality
without delaying the JAX-WS 2.0 EG. The plan was to later make this JSR into a
required component of a future version of the Java web services stack.
After looking at the current state of...
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
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
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...
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...
A new sample is added to WSIT samples that shows an enterprise Web service
enabling integration both within and across boundaries. This sample demonstrates
a price quotation service that provides list price to clients based on the
product identifiers. The client makes a request to a Retail Quote Service (RQS)
which then communicates with multiple Wholesale Quote Service (WQS) to get the...
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