6 Replies Latest reply on Apr 29, 2005 6:23 PM by Jason Greene

    Using wscompile for doc/lit

    Dan Smith Newbie

      This is really a wscompile question, but I thought I'd ask here to see if anyone could help.

      I am able create and deploy a doc/lit service as described in the Wiki, but I find the process to be a real pain. Here's what I'm talking about.

      You create an interface such as:

      public interface MathService extends Remote
      {
       public int add( int a, int b ) throws RemoteException;
      }
      

      Then run the wscompile tool to get the generated server code and mapping files etc. then (this is the annoying part) you have change your interface and implementation to use the complex types generated for you:
      public interface MathService extends Remote
      {
       public MyService_add_ResponseStruct add( MyService_add_RequestStruct req ) throws RemoteException;
      }
      

      Now... if I was done that would be one thing, but now say I want to make a change to my interface. I can't just rerun the wscompile tool on my new class, I have to change it back first.

      Is it possible to just start with an interface such as:
      public interface MathService extends Remote
      {
       public AddReply add( AddParams params ) throws RemoteException;
      }
      

      And keep wscompile from generating it's own complex types? I seem to recall this being how to do it AXIS...

      Anyway, I'd like it if the development of the service was more like that used for RPC style. Is that possible?

      Thanks,