ClientGen Wizard is one of the coolest wizards to come out of the Workshop 10gR3 release. In fact, we should have it going forward for our future OEPE releases.
There are a lot of cool features to JAX-WS that were incorporated into 10gR3 but the ClientGen wizard is one of my favorites. One of the great things about ClientGen is that it gives you an additional choice to using the more classic Service Control wizard that was part of Beehive and part of prior Workshop releases.
To keep this entry brief I'll write only about invoking the wizard and the first page of the wizard that can be used for selecting an appropriate WSDL that ultimately creates the Client Gen JAR file.
ClientGen can be used in both JAX-RPC and JAX-WS web service projects. I usually put it into a JAX-WS web service project since then I can use other JAX-WS features.
There are two ways to invoke it: 1) from File > New > Other > Web Services > ClientGen Web Service Client or, 2) right-clicking on a WSDL within a web service project.
When invoked from File > New... the 1st page of the wizard displays as shown below. Here you can choose from a local WSDL in either a valid JAX-WS or JAX-RPC project.
If you choose the remote WSDL Location radio button you have the ability to choose a WSDL off the Internet from which a ClientGen JAR will be created. As shown below the remote radio button is chosen and then a user can choose a valid project to place the created ClientGen JAR.
If a user invokes the wizard from right-clicking on a WSDL - the second way of invoking the wizard mentioned above - then he'll have to hit the back button once after the wizard pops since a WSDL is already selected.
If the user uses the second method to invoke the ClientGen wizard by right-clicking on a WSDL in his project then we presume he doesn't need to see the first page of the wizard but we provide the option of going to the first page if he changes his mind of what WSDL to use.
Regardless of the path taken to get to the wizard's WSDL selection page, once the remote WSDL location is selected and a valid WSDL URL is provided, the user must then click Validate WSDL button to make sure that the remote WSDL can be used to create the JAR file. If the WSDL URL is validated then the Next button will be enabled so that the user can choose other features in subsequent pages of the wizard and finally click Finish.
That's it for now. I'll return with another posting on subsequent pages for the wizard in the next few days.
