Chris,
That should be fine as long as your SessionManager is properly
re-entrant/thread safe.
Dan
On Sunday 03 February 2008, Chris Campbell wrote:
If I understand the code correctly, the HttpConduit holds the
session in a private field with no accessor method, and manages the
session
Basically we store the stateful information into the message context,
and the interceptor get the stateful information from the message context.
Maybe you can put your own SessionManager into the message context and
pass it to the interceptor that you use.
Willem.
Chris Campbell wrote:
If I
It is not easy to share the http conduit between the different proxy,
since you need to hack the HttpTransportFactory and handle
theconfiguration of the http conduit.
I don't think using the interceptor could resolve the problem that you
met. Because when you using the
interceptor to hold the
If I understand the code correctly, the HttpConduit holds the
session in a private field with no accessor method, and manages the
session itself. So I think I have to use an interceptor to set the
cookie on the other proxies.
My current work around (I think similar to what you suggested) is to
On Friday 01 February 2008, Chris Campbell wrote:
I am using CXFServlet in tomcat, and intend to load balance
instances of them with apache mod_jk, and want to use sticky sessions.
I figure I have to create a session somewhere, as I do not see a
session created (JSESSIONID ?) automatically.
The problem is that I get a different session for different
endpoints, maybe its how I set the client up? I do set the client up
in java code rather than with xml config, so maybe I am doing
something wrong there. Is it possible that each service interface is
getting a different http-conduit?
Oh. Yea. That would definitely do it. Good catch. Each client proxy
holds it's own conduit and thus the cookie for the session is stored
there is unique for each proxy.
Most likely, you will need to do some cookie management your self. Grab
the protocol headers from the response
Yes , CXF do not share the http conduit between the different client proxy.
If you want to share the session between the client proxy, I am afraid
you need to hack the CXF http conduit code to handle the cookie in you
application code.
Willem.
Chris Campbell wrote:
The problem is that I get
That would have to be on the client side, correct? I think I would
need to have a client side inInterceptor to do that.
I tend to load the proxies as needed, is there a way to probe the
bus to get any other loaded proxies so that a lazily instantiated
proxy can get a previously acquired session
