Using wscompile for doc/lit

[dannox02]

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,

[jason.greene]

wscompile always generates wrapper elements like this. Just keep your original interface arround and then you can rerun wscompile as many times as you like. When you edit your original interface, as long as you didn't change the name of the struct class, it will generate you a new one with the new parameters. Then you just have to change your implementation to use the new parameters.

The step-by-step doc/literal wiki does this very thing.
http://www.jboss.org/wiki/Wiki.jsp?page=WSDOCServiceStepByStep

-Jason

[thomas.diesler]

Another option is, to start of with a req/res structures in your SEI and do the unwrapping in your impl code.

[dannox02]

Another option is, to start of with a req/res structures in your SEI and do the unwrapping in your impl code.

I think this is what I'm getting at, but I can't figure out how to do that... do you mean I can start with this kind of code:

public interface MathService extends Remote
{
 public AddReply add( AddParams params ) throws RemoteException;
}

And not have to change it after running wscompile?

[thomas.diesler]

yes

[dannox02]

Sounds good! Of course, this leads back to my original question... how? ;-)

I've tried a bunch of different options with wscompile, but it still produces the wrapper classes, and referenes those in the mapping file. How do I run wscompile so that the mapping file does not reference the wrapper types?

Thanks!

[jason.greene]

I don't think there is a way to get wscompile to generate your service like this. However, you can change the jaxrpc-mapping file to use a single object that can be named by whatever name you want.

Sorry, but hopefully we can address this in the future with jbossws tools.

-Jason