Jitendra Kotamraju's Blog: April 2007 Archive

Posted by jitu on April 19, 2007 at 06:20 PM | Permalink | Comments (1)

JAX-WS RI 2.1.1 RC1 should work with any StAX implementation. I tried many jax-ws tests with woodstox 3.2.1 version and all of them are passing. Let us know if you face any problems with your application. All you need to do is replace sjsxp.jar with woodstox jar.

Google's AdSense and JAX-WS

Posted by jitu on April 12, 2007 at 11:19 AM | Permalink | Comments (2)

I came across Google's AdSense API Developer's Guide. Disappointed to see that there is no JAX-WS sample client code. So I looked at the Axis client, thought JAX-WS client code would look the same. Indeed, it was the case. First need to create a proxy code. Used JAX-WS's wsimport to create proxy code. The generated code is completely portable and much smaller. Here is the command:

wsimport -p com.google.api.adsense.v2 -d gen https://www.google.com/api/adsense/v2/AccountService?wsdl

This WSDL defines additional headers in soap:binding section. soap:binding changing the porttype by adding additional headers is not a good idea. JAX-WS doesn't capture these in the SEI. The portable way to add these headers to the messages is using SOAP handlers. Using SOAP handlers is a bit complex, but we can add these headers easily using RI's extension. This is similar to what Axis is doing in the axis sample code. But in our code, we could use JAXB !.

ObjectFactory fact = new ObjectFactory();
((WSBindingProvider)accountService).setOutboundHeaders(
    fact.createDeveloperEmail(developerEmail),
    fact.createDeveloperPassword(developerPassword),
    fact.createClientId("ignored"));

The other difference is some types are mapped to List. One can get arrays also by passing customization files to wsimport. Here is the complete sample code using JAX-WS

JAX-WS RI in BEA WebLogic Server 10

Posted by jitu on April 04, 2007 at 01:20 PM | Permalink | Comments (1)

BEA WebLogic Server 10 becomes one more vendor implementation for Java EE 5. Product Overview says

"New core Web services technologies have been implemented including the Java API for XML Web Services (JAX-WS 2.0) and Java API for XML Binding (JAXB 2.0). BEA implements JAX-WS 2.0 based on the GlassFish community project (another blended example), which provides a solid implementation supported by the Java community."

JAX-WS RI is going places. Many application servers, tool kits and frameworks are including RI's implementation of JAX-WS 2.0 based on its quality, performance and extensibility. I wonder what all Pipe/Tubes are there in WebLogic to provide more functionality.

Powered by
Movable Type 3.01D

java.net RSS Feeds