Do you mean the namespace of the body element? If so, you can pass it in on the setOperationName() method: call.setOperationName( new QName( ns, opName ) ); Or, one of the call.invoke()'s itself takes a QName as the 1st param. Unfortunately, Axis has changed so much since the book came out that there really is no way to avoid the hurdles you're seeing (and going to see). A lot (most?) of the concepts should have remained the same - but the APIs are still in flux. -Dug
"Newman, Scott" <[EMAIL PROTECTED]> on 03/11/2002 09:29:09 AM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: RE: Getting started Hi Dug Yeah, it confused the heck out of me for a while. Kinda makes you think you know what is going wrong. One question I do have about the new beta candidate, is where do you define your namespace? I had downloaded it, and was testing it out, and I found that the call.NAMESPACE field was no longer there, and that in the setProperty of Call.java does not look for it. For the most part, I'm going through your book, and I don't want to get stumped on little hurdles like this. Do you think it stays pretty true to your book? Newman -----Original Message----- From: Doug Davis [mailto:[EMAIL PROTECTED]] Sent: Monday, March 11, 2002 9:20 AM To: [EMAIL PROTECTED] Subject: RE: Getting started btw - in the latest version the Axis client should throw a much more meaningful exception - hopefully, we've seen the last of those "bad envelope" error messages. Although, you'll have to look inside the AxisFault itself (or do a dumpToString()) - doing a toString() on it won't be enough to see the complete error message - not sure why... -Dug "Newman, Scott" <[EMAIL PROTECTED]> on 03/11/2002 09:14:34 AM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: RE: Getting started Just got over this myself. Try putting axis.jar and logxx.jar into tomcat's commom/lib folder. Also, use tcpmon to forward your soap calls to port 8080 (if that is your tomcat port) and see what your request/response looks like. In my case, the reason I was getting the bad envelope namespace error was because tomcat was throwing an error, and axis was trying to parse it as xml. Newman -----Original Message----- From: Eddie Post [mailto:[EMAIL PROTECTED]] Sent: Monday, March 11, 2002 5:25 AM To: [EMAIL PROTECTED] Subject: Getting started Hellu, I can get the Axis example to work. Everytime I try the wsdd Calculator example With Axis alpha 3 and try to deploy it, I do get the following error: --------------- C:\Ed_soft\Develop\Manual\xml-axis-alpha3\samples\ed>java -cp .;./a xis.jar;./log4j-core.jar;./jaxp.jar;./crimson.jar org.apache.axis.c lient.AdminClient deploy.wsdd Processing file deploy.wsdd AxisFault faultCode: http://xml.apache.org/axis/:Server.userException faultString: org.xml.sax.SAXException: Bad envelope namespace: faultActor: null faultDetail: exceptionName: org.xml.sax.SAXException stackTrace: org.xml.sax.SAXException: Bad envelope namespac e: at org.apache.axis.message.EnvelopeBuilder.startElement(Env elopeBuilder.java:108) --------------- Please some help, Eddie _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
