/**

   * @(#)SimpleService.java

   *

   */





public class SimpleService



   {



   public String getStringMessage()



   { return "This web service works !"; }





   public int getInt()



   { return 42; }





   public int echoInt(int c)



   { return c;}



   }

• Separate implementation and definition
• Definition in Java instead of a new language
• No additional configuration files since class generation is derived from the remote object
• Industry standards

• A dispatcher based on one servlet per Web service to provide better performance, controlled access and scalability.
• A SOAP 1.1 compliant engine sitting on top of HTTP with fast SOAP message construction and parsing, and an XML stream parser that is eight to 10 times faster than the Apache Soap Server 2.x.
• Support for collection classes, elements, basic types and complex types such as arrays.
• An efficient registry-based type mapper that holds information about Java types and their XML mappings for use in Marshalling/DeMarshalling and handling non-supported complex types.
• Easy deployment in a standard J2EE archive (WAR) for J2EE-compliant application servers, including Tomcat, Sun RI and the SilverStream Application Server.

• Using Project::Project Settings::Classpath we'll add the jbroker-web.jar archive to our project classpath (in this case pointing to C:\jbrokerWeb10-beta\lib\jbroker-web.jar.

• Generate stubs (This will take care of the client stub and test client generation.)
• Generate tie-based skeletons (A SilverStream implementation of a Web service can optionally include a SOAP tie class generated by the Web service wizard. The tie class supports delegation. If you already have an implementation class for a Web service, you can extend a tie class and add code to your subclass that sets the target for delegation to be your implementation class. This design model is particularly useful if you want an existing implementation object to support multiple protocols. For example, if you already have a remote object that supports IIOP calls, you may want to use delegation to allow that object to support SOAP as well.)
• Generate skeletons (This will be generated anyway if tie-based skeletons are generated because they inherit from the earlier.)
• Generate a WSDL file (This will be created from the signature of the selected method in the initial class and the SOAP options selected in the current panel.)

• The remote interface generator creates a Java remote interface (an interface that extends java.rmi.Remote) from an existing Java class or JavaBeans component. This remote interface is then used as input to the other compilers.
• The rmi2soap compiler transforms Java remote interfaces into SOAP stubs and skeletons.
• The rmi2wsdl compiler transforms Java remote interfaces into WSDL documents.
• The wsdl2java compiler transforms WSDL documents into Java remote interfaces. (This one is not used for "Generate objects to create a new Web service," but it is the main compiler for "Generate objects to use an existing Web service.")

   public void process(String[] args)



   {



   try



   {



   SimpleService_REMOTE remote = getRemote(args);





   

        // The following code has been generated for your testing convenience. In

        // order to successfully test your Web Service, you must uncomment one or

        // more of these lines and supply meaningful arguments where necessary.

        // Once you have modified the test method(s) below, compile this class and

        // execute it from a command line with your class path set appropriately.

   



   System.out.println("Test Result = " + remote.getStringMessage());



   System.out.println("Test Result = " + remote.echoInt(42));



   }



   catch (Exception _e)



   {



   System.out.println("*** Error Executing Generated    Test Client ***");



   _e.printStackTrace();



   }



   }

public SimpleService_REMOTE getRemote(String[]args) throws Exception
{

   String lookup = "xmlrpc:soap:SimpleService_REMOTE";

	 // JNDI lookup for the client stub (must be in the client classpath)

   InitialContext ctx = new InitialContext();

 	// the remote returned is ready to be used as if

	// the client application was directly talking to the remote object

   return (SimpleService_REMOTE)ctx.lookup(lookup);

}