Anne wrote:
> If you're building a service agent in Axis, then you can use java2wsdl
> to generate the WSDL file, although there are still some bugs in this process.
> (The design center for doc/literal assumes that you start with a WSDL file.
> I think this is an invalid assumption, though.)
> What you should do is generate the WSDL, then tweak it so that the WSDL
> is valid, and then run wsdl2java and regen the service agent class.
Thanks! That's what I've ending up doing... No matter how much I Java2WSDL, I can't get
a WSDL document I can live with. (And I'm not totally sure what it's SUPPOSED to look like, so I'm at a distinct disadvantage here.)
> If you prefer to work with Java constructs, you should use an "rpc" provider.
> If you prefer to work with XML constructs, you should use a "message" provider.
> Both are acceptable. One isn't "better" than the other. It depends on how you
> want to write your service code.
Where does the "message" part go? I see it in the WSDD (still on the Axis Users Guide) for the MessageService class, but not in any of the WSDL examples. For WSDL, the choices seem to be RPC, DOCUMENT or WRAPPED. (At least, those are the options when using Java2WSDL.)
--
Wendy Smoak
Applications Systems Analyst, Sr.
Arizona State University, PA, IRM
