Bhakti Mehta's Blog: Community: Java Web Services and XML Archives

Posted by bhaktimehta on May 12, 2008 at 12:56 PM | Permalink | Comments (5)

Glassfish v3 will be the next major release of the GlassFish application server. The focus of the release is modularization, enablement of non Java EE containers
and embedability. GlassFish v3 builds on the strength of GlassFish v2 but takes a completely new approach, providing a highly modular, lightweight, extensible architecture.

GlassFish v3 Technology Preview 2 (TP2) is a milestone release of the GlassFish v3 Application Server. You can find the TP2 glassfish preview bundle here.
This page provides a brief description of TP2, and points to the information you need to get started. Here is the information on what is part of TP2

Metro will be available as an Update Center module in V3 as part of the TP2

This is a preliminary guide on how to work with Metro in the current development v3 builds.
Note: This can be subjected to change in future.

Steps to install and run v3.

1. Unzip gfv3-preview2.zip downloaded from  here.

This is the web distribution for v3 and does not have support for EJBs. For TP2 we will only support JAXWS deployment ie.webservices with webapps
whose versions are 2.3 or 2.4. Support for
JSR 109 based services is in progress and will be available after TP2.

2. Run glassfish-v3tp2/bin/updatetool.bat

You get a prompt like this

The software needed for this command (updatetool.bat) is not installed.
Press any key to install the necessary software, or Ctrl-C to quit.
After software installation is completed you may re-run this command.

Press any key to continue . . .

It downloads the necessary files

Platform: windows-i386
Software repository: http://pkg.glassfish.org/dev/windows/gf3000_2000/
Installing pkg packages...
Installing: python2.4-minimal@2.4.4,0-6.564:20080425T194712Z
python2.4-minimal@2.4.4,0-6.564:20080425T194712Z: manifest file doesn't exist ye
t, fetching from server
python2.4-minimal@2.4.4,0-6.564:20080425T194712Z: downloading files.............
................................................................................
..........................................................................
python2.4-minimal@2.4.4,0-6.564:20080425T194712Z: installing files...
Installing: pkg@0.1.4,0-6.564:20080425T194710Z
pkg@0.1.4,0-6.564:20080425T194710Z: manifest file doesn't exist yet, fetching fr
om server
pkg@0.1.4,0-6.564:20080425T194710Z: downloading files...........................
........................................
pkg@0.1.4,0-6.564:20080425T194710Z: installing files...
Installing updatetool packages...
Installing: wxpython2.8-minimal@2.8.7.1,0-6.564:20080425T194728Z
wxpython2.8-minimal@2.8.7.1,0-6.564:20080425T194728Z: manifest file doesn't exis
t yet, fetching from server
wxpython2.8-minimal@2.8.7.1,0-6.564:20080425T194728Z: downloading files.........
.............................................................
Installing: updatetool@2.0,0-6.564:20080425T194726Z
updatetool@2.0,0-6.564:20080425T194726Z: manifest file doesn't exist yet, fetch
ng from server
updatetool@2.0,0-6.564:20080425T194726Z: downloading files.....................
................................................................
updatetool@2.0,0-6.564:20080425T194726Z: installing files...
Update Center initialization complete.

This installs the UpdateCenter

3.Run glassfish-v3tp2/bin/updatetool.bat again 
and that brings up the gui like this
click on the Available Add-ons

4. Select Metro Web Services Stack and click install

This will copy webservices-rt.jar, webservices-tools.jar,webservices-api.jar and jsr109-impl.jar to
glassfishv3-tp2/glassfish/modules folder. Next you can start the GF using

glassfishv3-tp2/glassfish/bin/asadmin start-domain domain1

5. Deploy your war like this 
glassfishv3-tp2/glassfish/bin/asadmin deploy foo.war

You can try metro samples from https://metro.dev.java.net/
Please give us feedback if this works for you . You can file your bugs under https://glassfish.dev.java.net/issues/ category webservices and version v3.

Additional Information
Project Metro

V3 Engineers Guide

V3 Build Instructions

Developing Webservices from wsdl using Netbeans

Posted by bhaktimehta on March 05, 2008 at 11:31 AM | Permalink | Comments (5)

The following blog shows how you can easily create a Webservices project in Glassfish v2 using Netbeans 6.0 from an existing wsdl.
Download Netbeans 6.0 from here
To Start
Select File->Create new Project->Web

Click on finish

Next Right Click on WebServiceFromWsdl project and select new WebService from wsdl
Here is the wsdl and its schema for this blog

Here is how the screen looks like

Click on finish

This is how the generated WebService Design tab looks like
design tab.jpg

You can implement the methods for the service by selecting the Source tab

Right Click on the WebServiceFromWsdl project and call Run
You will see the project deployed in GF

You can verify by clicking on http://localhost:8080/WebServiceFromWsdl/RMDemoService?wsdl
This is how the published wsdl will look like

Deploying SOAP 1.2 based webservice in Glassfish

Posted by bhaktimehta on January 29, 2008 at 02:15 PM | Permalink | Comments (6)

The following blog shows how to create and deploy a SOAP 1.2 based webservice in Glassfish v2 using Netbeans 6.0

Download and install Netbeans 6.0 from here.

Click on File->New Project
Choose Web ->WebApplication

Next provide the name of the Web application
choose the Java EE version as Java EE 5

Click on Finish

Next in the Projects tab you will see EchoTest
Right Click on EchoTest and create New WebService

Click Finish

Next we add operations to the service

Click the source tab in the center pane you will see the Echo.java source code

Add the following operation to the source code (This can be done by right clicking Webservices->EchoService->AddOperation)

/**
     * Web service operation
     */
    @WebMethod(operationName = "echoString")
    public String echoString(
            @WebParam(name = "parameter") String parameter) {

        return "hello" + parameter;
    }

Add the following annotation
@javax.xml.ws.BindingType(value="http://java.sun.com/xml/ns/jaxws/2003/05/soap/bindings/HTTP/" )
The above is important because the default binding supported by JAXWS 2.0 is SOAP 1.1 over HTTP.

This is how the source code looks

Right Click on EchoTest project
Do Clean and Build
Do Undeploy and Deploy
You will see the service is deployed at
http://localhost:8080/EchoTest/EchoService?wsdl

Next step build a client

File -> New Project -> Web Application (Same as fig 1)

Name the project as EchoClient

Click Finish
Right click on EchoClientTest and click New Webservice Client

Specify the wsdllocation as shown

Click Finish

Next expand EchoClientTest->WebServiceReferences->EchoService->EchoService->EchoPort->echoString

Drag echoString and drop after line <h2>

This is how the jsp will look

Next Right click and call Run the EchoClientTest

This is what you see when you call http://localhost:8080/EchoClientTest/

Hello World!

Result = hello John Doe

Advanced Tip
If you want to see the soap messages add the following line
in
GF/domains/domain1/confiig/domain.xml in java-config element
<jvm-options>-Dcom.sun.xml.ws.assembler.server=true</jvm-options>

Then stop the GF server and restart it

Next call http://localhost:8080/EchoClientTest/
You can see the following messages in GF/domains/domain1/logs/server.log
Request

<?xml version="1.0" ?>

<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope">

  <S:Body>

    <ns2:echoString xmlns:ns2="http://test/">

      <parameter> John
Doe</parameter>

    </ns2:echoString>

  </S:Body>

</S:Envelope>

Response

<?xml version="1.0" ?>

<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope">

  <S:Body>

    <ns2:echoStringResponse xmlns:ns2="http://test/">

      <return>hello John
Doe</return>

    </ns2:echoStringResponse>

  </S:Body>

</S:Envelope>

]

Overview of Web Services Reliable Messaging

Posted by bhaktimehta on March 31, 2006 at 01:08 PM | Permalink | Comments (0)

WS-Reliable Messaging 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.
It provides an interoperable protocol that a RM (Reliable Messaging) Source and RM Destination use to provide
Application Source and Destination a guarantee that the message that is sent will be delivered.
This guarantee is known as delivery assurance.

There are four basic delivery assurances that endpoints can provide

AtMostOnce:
Messages will be delivered at most once without duplication . It is possible some messages in a sequence may not be
delivered.
AtLeastOnce:
Every message sent will be delivered. Some messages may be delivered more than once.
ExactlyOnce :
Every message sent will be delivered without duplication.
InOrder:
Messages will be delivered in the order that they were sent.

WS RM is one of the enterprise features in Project Tango which is Sun's Java Web Services interoperability project with Microsoft's Windows Communication Foundation (WCF).

In Project Tango, RM is enabled in endpoints by the presence of RM policy assertions in the WSDL. Netbeans IDE
will provide configurable settings to easily enable RM in endpoints as shown in the screen shot below.

Screenshot showing how to enable WS RM in Netbeans Tango module

Screenshot showing how to enable WS RM in Netbeans Tango module

Fig 1 Screenshot of how to configure WS RM for an endpoint using Netbeans

Programming Model for Tango

Developer writes Producers/Consumers using JAX-WS 2.0 apis.
Developer/Deployer supplies config files which would be wsdls containing Policy assertions to enable/control Tango components.
Config file can be written by hand or easily produced by Tango Netbeans Module as shown in Fig 1.

Message exchanges when RM is enabled
This figure shows how the messages are exchanged between RMSource and RM Destination when RM is enabled

Fig 2 Message exchange when RM is enabled using WS RM implementation

The above figure shows how the Client or Application Source sends a message for reliable delivery.
When RM is enabled, Project Tango's RM Source module is plugged into the JAX-WS remoting system.
The RM Source module keeps copies of messages until their receipt is acknowledged (via the exchange of protocol
messages). Similarly, an RM Destination module acknowledges messages (and may buffer them for order guarantees).
After guaranteeing order (if ordering enabled), the RM Destination allows the message to proceed through the
JAX-WS dispatch for delivery to the Endpoint or Application Destination.

Protocol Messages
The above figure shows the exchanges of protocol messages and application messages between reliable messaging endpoints

The above figure shows the exchanges of protocol messages and application messages between reliable messaging endpoints

Fig 3 Possible application and protocol message exchanges between RM endpoints

The above figure shows how the message exchange takes place between two reliable messaging endpoints
once the initial preconditions are established such as resolving endpoint references, policy exchange and establishing trust.

The RM Source requests creation of a new Sequence by initiating a
CreateSequence/CreateSequenceResponse handshake.
The RM Destination creates the Sequence by returning a CreateSequenceResponse
with globally unique identifier.This sequence id would be used to identify
the sequence and will be sent in all the following messages.
The RM Sources begins sending messages with MessageNumber 1 .
After 3 messages it sends LastMessage token.
The 2nd message is lost in transit
The RM Destination acknowledges receipt of message numbers 1 and 3 in response to LastMessage.
The RM Source retransmits 2nd message which has the same sequence identifier
and message number so that the RM Destination can recognize it as equivalent of earlier message.
The RM Source also includes an AckRequested so RM Destination can expedite the acknowledgement.
RM Destination receives the second transmission and acknowledges the receipt of messages 1,2 ,3.
The RM Source receives the acknowledgement and sends Terminate Sequence to RM Destination.
The RM Destination receives TerminateSequence and reclaims resources associated with the Sequence

Availability
The implementation will be available by JavaOne on Java.net with support for Glassfish and Netbeans IDE.

Plugfest Status
We tested our WS RM implementation with Microsofts WCF at the Plugfest on March 7-9 at Redmond.
We successfully interoperated in the ReliableOneWay and ReliableRoundrip scenarios both as clients and endpoints.

JavaOne 2006
For more information be sure to check out the session on
Reliable and Transacted Web Services between Java™ Technology-Based Project Tango and Microsoft Indigo TS-1603.

Other information
WS-ReliableMessaging specification
WS-RM Policy Assertion

JAXB 2.0 and JAX-WS 2.0 are a part of Mustang (JDK 6.0)

Posted by bhaktimehta on August 08, 2005 at 04:18 PM | Permalink | Comments (2)

Delivering Web Services is one of the primary themes for Mustang (Java SE 6). Our goal is that JSE will provide reasonable support for ease of development for the web services stack. This will primarily be client-side focused with a lightweight server to support callbacks. The main specifications are the Java Architecture for XML-Web Services (JAX-WS) 2.0 (formerly known as JAX-RPC) and Java Architecture for XML Binding (JAXB) 2.0.

JSR 224 is defining JAX-WS 2.0. This is a major update since the JAX-RPC 1.0 specification incorporating new specifications and updates to existing standards. JAX-WS 2.0 now delegates the databinding related tasks to JAXB 2.0.

JSR 222 is defining JAXB 2.0. It adds significantly to JAXB 1.0, including 100% XML schema support, the binding of Java classes to XML schema, the meeting of data binding requirements for JAX-WS 2.0, and schema evolution support. A flexible binding allows an application to bind only parts of an XML document (relevant to the application) to Java.

Mustang has the webservices features integrated as of b40. You can try the latest snapshot from https://mustang.dev.java.net/

We are fixing and integrating bugs on a regular basis. Please let us know about your bugs, you can file them at
http://bugs.sun.com/bugdatabase/index.jsp

There are 4 new scripts added in the jdk6.0/bin which are as follows xjc, schemagen , wsimport and wsgen
To run the JAXB schema compiler you can invoke the xjc as

/path/to/jdk6.0/bin/xjc foo.xsd -p test.foo

Similarly to invoke the schema generator to generate schemas from Java sources

/path/to/jdk6.0/bin/schemagen Foo.java

To generate portable artifacts from wsdls and external jaxws or jaxb binding files you can use wsimport

/path/to/jdk6.0/bin/wsimport stock.wsdl -b stock.xml -b stock.xjb

To generate portable artifacts from Java sources you can use wsgen

/path/to/jdk6.0/bin/wsgen example.Stock

Javadocs for jdk6.0
The javadocs are located at
http://www.java.net/download/jdk6/doc/api/

Forums
http://forums.java.net/jive/forum.jspa?forumID=25

List of Committed bugs in the latest snapshot release
https://mustang.dev.java.net/MustangCommittedBugs.html

More information on JAXB and JAXWS

* JAXB
* JAXWS