wsdl2java - shortcomings?

[Josh Rehman <jr...@citysearch.com>]

Hi,

Still new to all this, so I'm not sure if this observation is accurate. 
It seems to be that wsdl2java could vastly improved if all of it's 
concrete classes were generated with delegate code pointing to some user 
specified implimentation. As it stands, I am forced to generate code, 
copy it somewhere else, implement my functionality, and then hope that 
the generated code never changes again (because if it does I have to 
perform a messy merge). This would be generally useful, but especially 
to me because I have some code that already implements the beans I need.

That's the single biggest thing I can think of that would make my life 
easier.

Another thing that would be handy would be to have an option to generate 
soapmonitor code in the wsdd file.

I'm mentioning this stuff in case I suspect/hope that I am missing a 
sublty about Axis that would make this problem trivial.

Thanks kindly,
Josh

Re: wsdl2java - shortcomings?

[Dan Christopherson <da...@nvisia.com>]

Thank you very much. I was surprised when I didn't find anything, but 
once I'd figured out what was going on, I kinda stopped looking, too.

James Black wrote:
> Dan Christopherson wrote:
> 
>> Now if there were (or is) a way to tell wsdl2java to use a different 
>> name for the 'Impl' class (which is a delegate by the way), that would 
>> have saved me some similar consternation and grumbling. 
> 
> 
> In the java2wsdl tag I use
> 
> <java2wsdl
>    implclass="my.implementation.class'
>  <mapping ... />
> </java2wsdl>
> 

Re: wsdl2java - shortcomings?

[James Black <jb...@ieee.org>]

Dan Christopherson wrote:

> Now if there were (or is) a way to tell wsdl2java to use a different 
> name for the 'Impl' class (which is a delegate by the way), that would 
> have saved me some similar consternation and grumbling. 

 In the java2wsdl tag I use

<java2wsdl
    implclass="my.implementation.class'
  <mapping ... />
</java2wsdl>

-- 
"We do not lose our identity in our relations with others; in part, at least, we achieve our identity by those relations." Tony Blair, 1993

Re: wsdl2java - shortcomings?

[Dan Christopherson <da...@nvisia.com>]

Josh Rehman wrote:
> Hi,
> 
> Still new to all this, so I'm not sure if this observation is accurate. 
> It seems to be that wsdl2java could vastly improved if all of it's 
> concrete classes were generated with delegate code pointing to some user 
> specified implimentation. As it stands, I am forced to generate code, 
> copy it somewhere else, implement my functionality, and then hope that 
> the generated code never changes again (because if it does I have to 
> perform a messy merge). This would be generally useful, but especially 
> to me because I have some code that already implements the beans I need.
> 

Well, what we've done is name our service implementation 
BlahServiceImpl, which is what wsdl2java generates. when we call the 
wsdl2java ant task, we set up the output directories so that it will 
find our Impl class and wsdl2java just reports that it found a 
BlahServiceImpl and won't generate a new one. We generate the client 
stubs and server skeletons with every build this way.

Now if there were (or is) a way to tell wsdl2java to use a different 
name for the 'Impl' class (which is a delegate by the way), that would 
have saved me some similar consternation and grumbling.

-danch