James' response:

Hardiman, Piers wrote:

> Please can you explain in a bit more detail how this works?
>
> We are writing code on the server side and generating the WSDL from
> that.
>
> Our example package structure is as follows:
>
> customer                -       contains the delegate class for our 
> connection into an EJB.
> customer.dto    -       all the data transfer objects requiring to be 
> passed through SOAP.
> customer.ws             -       the generated SOAP code.
>
> Currently the SOAP generated code is creating its own copies of the 
> DTOs. We want to output the AXIS webservice code to the separate 
> customer.ws package.
>
> Do you mean that we should use the AXIS generated DTOs to extend our 
> DTOs. We are a bit confused as this causes problems with compilation 
> until we have created the AXIS generated DTOs.
>
> Additionally if we try to create the AXIS code into the same package 
> as the DTOs are already in, it overwrites our code.
>
> Any assistance you could give us would be greatly appreciated.
>
  All I know is what I do, but it works for my webservices.

  I have a class, Item, that has various getters and setters.  I then 
extend that class with ItemServer, that has all the business logic that 
the server side needs.

  When I run wsdl2java Item is not overwritten (I would lose my 
comments), for some reason.
  My options for wsdl2java are:
serverSide='yes', skeletonDeploy='no', noimports='yes', 
typeMappingVersion='1.2', output='stubs', testcase='no'.

  I have all the code from wsdl2java writing to the same place as my 
current code is, so that it can be determined if the java source is 
already present.

  I use java2wsdl first, so that I can ensure that the client and server 
are in sync as to the correct attributes, before I call wsdl2java.

  I don't know what you are doing precisely so it is hard to tell you 
what may be done differently.

-- 
"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

 
**************************************************************************
The information transmitted herewith is sensitive information intended only
for use by the individual or entity to which it is addressed. If the reader
of this message is not the intended recipient, you are hereby notified that
any review, retransmission, dissemination, distribution, copying or other
use of, or taking of any action in reliance upon this information is
strictly prohibited. If you have received this communication in error,
please contact the sender and delete the material from your computer.

Reply via email to