Took a look at this, and it seems there's really no hope of getting the headers at least with client.getProperty(CommonsHttpMessageSender.HTTP _HEADERS), because the properties map is is simply implemented in AbstractContext - unless you'd set the headers map in HttpChannel when handling the response.
Kalle On 3/26/07, Tomek Sztelak <[EMAIL PROTECTED]> wrote:
Yep, support for sending custom HTTP headers is build in XFire 1.2.5. But currently i'm not sure if its possible to get header form HTTP response. On 3/24/07, Kalle Korhonen <[EMAIL PROTECTED]> wrote: > I see XFIRE-884 added support for setting http headers. Can I also assume > that the reverse case for getting the headers with > client.getProperty(CommonsHttpMessageSender.HTTP_HEADERS) > should work in 1.2.5? I also read you were going to release 1.2.6shortly > because of some issues with 1.2.5 - is this still the case? > > Kalle > > > > > On 9/27/06, Dan Diephouse <[EMAIL PROTECTED]> wrote: > > Unfortunately, we don't expose access to the HTTP headers right now :-\. > > Its been on the wishlist though - a patch wouldn't be very hard at all > > if you were interested in helping out with this... > > > > - Dan > > > > Mark McCall wrote: > > > Yes, as in HTTP Headers. Sorry I was not clear before. > > > > > > -----Original Message----- > > > From: Dan Diephouse [mailto:[EMAIL PROTECTED] ] > > > Sent: Tuesday, September 26, 2006 11:05 AM > > > To: [email protected] > > > Subject: Re: [xfire-user] Setting HTTP request parameters from a client > > > stub > > > > > > What do you mean arbitrary parameter values? As in HTTP headers? > > > - Dan > > > > > > Mark McCall wrote: > > > > > > > > >> I am considering using XFire client support to generate a client stub > > >> > > > to access a NON-XFire based web service. I need to be able to send some > > > arbitrary parameter values in the Http Request, i.e. separate from the > > > SOAP envelope. How do I do this? > > > > > >> Thanks, > > >> Mark > > >> > > >> > > >> ----------------------------------------- > > >> The information contained in this e-mail message is intended only > > >> for the personal and confidential use of the recipient(s) named > > >> above. This message may be an attorney-client communication and/or > > >> work product and as such is privileged and confidential. If the > > >> reader of this message is not the intended recipient or an agent > > >> responsible for delivering it to the intended recipient, you are > > >> hereby notified that you have received this document in error and > > >> that any review, dissemination, distribution, or copying of this > > >> message is strictly prohibited. If you have received this > > >> communication in error, please notify us immediately by e-mail, and > > >> delete the original message. > > >> > > >> > > >> > --------------------------------------------------------------------- > > >> To unsubscribe from this list please visit: > > >> > > >> http://xircles.codehaus.org/manage_email > > >> > > >> > > >> > > >> > > > > > > > > > > > > > > > -- > > Dan Diephouse > > Envoi Solutions > > http://envoisolutions.com > > http://netzooid.com/blog > > > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > -- ----- When one of our products stops working, we'll blame another vendor within 24 hours. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
