RE: Document/Literal and RPC/Literal

[John Chen <jc...@parasoft.com>]

Does this matter if I am using the wsdd to deploy my Java Service? Do I 
need to add something special to my Java Class if I am deploying a service 
using style="document" and provider="java:RPC" ? Or do I need to add 
something special to my wsdd (such as setting a certain <parameter>)?


John

At 06:15 PM 4/24/2003 -0400, you wrote:
>If you're looking for a shortcut, you might try using Systinet WASP's 
>java2wsdl tool -- it will generate a document/literal WSDL definition from 
>a Java class, including the whole <types> definition for you. (Make sure 
>you install it using Axis compliant containers.) Then you can tweak the 
>generated WSDL to your liking and use Axis wsdl2java -server to generate 
>your Axis server stubs.
>
>Anne
>
> > -----Original Message-----
> > From: Mitch Gitman [mailto:mgitman@usa.net]
> > Sent: Thursday, April 24, 2003 5:33 PM
> > To: axis-user@ws.apache.org
> > Subject: Re: Document/Literal and RPC/Literal
> >
> >
> > Thanks! I had forgotten that wsdl2java generates server source.
> > As long as it
> > all works (of course), manually writing a WSDL and then filling in the
> > generated source would be acceptable. At least for me.
> >
> > In the long run (of course), full doc/lit support in java2wsdl would be
> > preferable. Obviates the above two manual tasks.
> >
> > Steve Loughran <st...@iseran.com> wrote:
> > Mitch Gitman wrote:
> > > Is there a way to use a handcrafted WSDL to change what the Axis service
> > > runtime delivers? On the face of it, that doesn’t make sense; 
> doesn’t
> > > seem possible.
> >
> > yes. you run wsdl2java -server and it creates the appropriate server
> > side stubs for the WSDL, and the .wsdd file to work with your datatypes
> > (which you can customise)
> >
> >
> >