Title: RE: Need WSDL for this SOAP message

Anne wrote:
>  I'm not sure I understand why you're using the call interface. 

I started with the Client code for example3.  That's what it uses.  I'll go see if there's a better example to start with.

> The main reason that you want to use WRAPPED 
> is so that you can invoke your service using something like this:
> string ResponseInfo = service.SubscriptionRequest( usedId, password );
> You should compile your WSDL file with wsdl2java and generate your client interface.

I did WSDL2Java, but in addition to the JavaBeans for the input/output messages, it generates four files full of RMI stuff.  I don't need RMI, I need a simple client for testing.  I will look at it again on Monday, maybe it's simpler than it looks.  My one brief foray into RMI for a class project was not very much fun.

I tried changing the allowedMethods as you suggested in the other message, but I still get No Such Operation unless the child tag of <body> matches the operation (or method?) name.  I think the child tag of <body> should be <subscription> or possibly <SubscriptionAttributes> so something's still wrong.

As it's officially the weekend here, I'm giving up on this until Monday.  Thanks again for your help. 

--
Wendy Smoak
Applications Systems Analyst, Sr.
Arizona State University, PA, IRM

Reply via email to