Damitha,

Thanks for your reply, it's extremely helpful.

Is there any support or guidance available for building on OS X?

If session management doesn't work for us, Is there a working syntax for explicitly setting a cookie header in the HTTP headers for a request? I tried several ways of creating a header and adding it to the options for the stub/service client, but was not successful. The examples of creating and adding headers are all Java and it appears that the set_property constants (like HTTPConstants.HTTP_HEADERS) are only present for the Java version, and that support for these properties isn't present in Axis2 C.

Jim



On 9/15/2010 10:26 PM, Damitha Kumarage wrote:
Hi Jim,
Axis2/C has session support working. But I don't think any released version has this support. Try 1.7.0 release candidate at [1]. At client side session support you don't have to do any configuration/coding. You need to set axis2_options_set_manage_session() only if you are using libcurl transport. But this is not the default transport.

Damitha

[1] http://people.apache.org/~shankar/axis2c/1.7.0-RC2/

jim wrote:
I need to use Axis2C on OS X. I've gotten things working, sort of, but have stumbled on cookie support. The server I'll be accessing sets a cookie on an initial call, then expects it on subsequent calls.

As far as I can see, I should be setting the options on the stub/service client so that 'manage session' = true. I've tried accomplishing this with axis_options_set_manage_session(). But, no cookie shows up in my requests

I've tried explicitly adding a cookie HTTP header, by following examples I've found for adding headers to the stub/service client options. The exact syntax of the examples varies; but I never get a header in the HTTP request.

Does cookie/session support work? Is it just a matter of getting the right syntax? Or is AxisC not able to handle cookies?

Any responses will earn my undying gratitude...

Jim Hughes

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]






---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to