Is the API for HTTP headers or SOAP headers? I found an empty method stub in my version of Stub class (1.1 final):

 

    /**

     * Helper method for updating headers from the response.

     *

     * Deprecated, since response headers should not be

     * automatically reflected back into the stub list.

     *

     *

     * @deprecated This method has been changed to a no-op but remains

     *               in the code to keep compatibility with pre-1.1

     *               generated stubs.

     */

     protected void getResponseHeaders(org.apache.axis.client.Call call) throws AxisFault {

     }

 

Thanks,

 

Scott

 

-----Original Message-----
From: Tom Jordahl [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 09, 2004 1:27 PM
To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
Cc: '[EMAIL PROTECTED]'
Subject: RE: Stub.getHeader in axis 1.1 or 1.2

 

 

The right API to use is Sub. getResponseHeader().

 

I added this specifically to get (surprise) the response headers.

 

--
Tom Jordahl
Macromedia Server Development

-----Original Message-----
From: Liu, Scott [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 09, 2004 4:08 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Stub.getHeader in axis 1.1 or 1.2

 

It looks like both getHeader() and Stub.getResponseHeaders() are deprecated in axis 1.1. as discussed a little while ago in the attached message. Does anyone know an alternative way to access soap headers in an Axis client? I have not tried 1.2 yet and do not know if it works there.

 

In my application I can set soap headers in .NET and Axis client and I can get soap headers in .NET but not in my Axis client. Any hints would be helpful.

 

Thanks,

 

Scott

 

> > -----Original Message-----

> > From: Toshiyuki Kimura [mailto:[EMAIL PROTECTED]

> > Sent: Tuesday, October 14, 2003 11:59 PM

> > To: [EMAIL PROTECTED]

> > Subject: RE: Stub.getHeader(namespace, partname) in axis1.1

> >

> > Nan,

> >

> >   Umm..., you mean the headers.size() equals to zero.

> >

> >   It seems the difference is from the modification on

> > "org/apache/axis/wsdl/toJava/JavaStubWriter.java".

> >

> > Here is the log;

> > [It may affect Axis 1.1 final]

> > .........*.........*.........*.........*.........*.........*

> > Revision 1.114 / Fri Apr 11 12:21:24 2003 UTC

> > Changes since 1.113: +0 -2 lines

> >

> > deprecated Stub.getResponseHeaders() and removed code for that

> > method so that response headers are not automatically reflected

> > back into the global header list for the Stub.  The method will

> > remain in the code because pre-1.1 stubs will reference the

> > method. Updated the stub writer to not generate files referencing

> > getResponseHeaders().

> > .........*.........*.........*.........*.........*.........*

> >

> > [It may affect the nightly build (i.e. the current code)]

> > .........*.........*.........*.........*.........*.........*

> > Revision 1.31 / Thu Aug 7 20:38:22 2003 UTC

> > Changes since 1.30: +39 -1 lines

> >

> > Add back in the ability to get response SOAP headers via the Stub.

> > Add a test case to make sure it works.

> >

> > This was removed in April 2003 to fix the problem where response

> > headers would be placed in the same place as request headers.

> > The solution to that went (way) too far, and in Axis 1.1, you can

> > only get response headers if you have the Call object, which you

> > can get from the Service object, which you *can't* get from the

> > Stub object.

> >

> > Solution is to add 2 new Stub APIs:

> >     public SOAPHeaderElement[] getResponseHeaders()

> >     public SOAPHeaderElement getResponseHeader

> >                               (String namespace, String partName)

> >

> > This makes it explicit that the response headers are separate from

> > the request headers.

> > .........*.........*.........*.........*.........*.........*

> >

> >   You'd better use the latest code, if you want to touch

> > the headers from your stub  -  apologies for the detour.

> >

> > --

> > Toshi <[EMAIL PROTECTED]>

Reply via email to