axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "robert lazarski" <robertlazar...@gmail.com>
Subject Re: [Axis2] Best way to use skeleton?
Date Tue, 30 May 2006 11:55:15 GMT
For axis2 1.0 and beyond there is a '-ssi' flag you can add that will
generate an interface. So you can now code to that instead of the skeleton.

See this jira for more info:

http://issues.apache.org/jira/browse/AXIS2-655

HTH,
Robert
http://www.braziloutsource.com/

On 5/30/06, vandenberget@aciworldwide.com <vandenberget@aciworldwide.com>
wrote:
>
>
> Hi,
>
> When I generate the server-side code from my wsdl, using wsdl2java, a
> skeleton class is generated that gets invoked by the (generated)
> MessageReceiver. From what I read, I understand that I'm supposed to
> implement my busines logic in the skeleton. But if I would do that, and for
> whatever reason re-run the wsdl2java, the skeleton is regenerated, hence by
> business logic implementation is gone! To me, it seems that in general, one
> should never manually change generated source code.
>
> The only thing I can think of to minimise this problem is to treat the
> skeleton as an entry point, and only call the 'real' business imlementation,
> that I've created myself. However you would then typically end up with a
> skeleton and an implementation class that have identical methods
> (signatures), which doesn't seem very elegant to me.
>
> Can't this be prevented somehow, e.g. by specifying the (existing)
> business class and method when invoking wsdl2java, so that the
> MessageReceiver will call that method, instead of calling the generated
> skeleton?
>
> Thanks,
> Tom
>

Mime
View raw message