Thx for the help.
Is there any way to avoid copying the cookies from one proxy to another?
I'm sure most clients can do it though I haven't tried with C# .net yet -
that makes up the bulk of my web service clients.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Stateful-web-s
I have a few questions.
Regarding the code to publish BankImpl:
Endpoint ep = Endpoint.publish("http://localhost:8080/BankAccount";,
new BankAccountImpl());
W3CEndpointReference er =
(W3CEndpointReference)ep.getEndpointReference();
Endpoint.publish("http://localhost:8080/
Thank you making the changes.
I look forwards to seeing this in a future release.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Stateful-web-services-with-CXF-tp3212822p3227581.html
Sent from the cxf-user mailing list archive at Nabble.com.
This is close to what I want:
http://cxf.apache.org/docs/multiplexed-endpointreferences.html
Except the "Number" class isn't really stateful. It can get an instanceId
from the message context. I guess you could use that to look into some kind
of HashMap that contains the state data you need but
That looks like an improvement - squeaky wheel gets a greasin
So how do we programatically return a new instance of a stateful bean from
within a WS method.
So, for example, we have the classic "Bank" web service bean that has a
"getAccount" WS method. The "getAccount" method returns a stateful
I guess we can "simulate" sessions by having the client call a web service
method that returns a session ID cookie and then the client can resend that
session cookie (JSESSIONID?).
Hardly ideal because not all WS clients are capable of sending cookies.
--
View this message in context:
http://cx
CXF has almost no documentation on this important matter - I find that
strange.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Stateful-web-services-with-CXF-tp3212822p3214136.html
Sent from the cxf-user mailing list archive at Nabble.com.
The "solution" you provided seems like more of a work around than a real
solution.
Why doesn't CXF simply support the "@Stateful" annotation ?
--
View this message in context:
http://cxf.547215.n5.nabble.com/Stateful-web-services-with-CXF-tp3212822p3212882.html
Sent from the cxf-user mailing li
I was reading how to do stateful web services using Metro:
https://metro.dev.java.net/1.4/docs/statefulWebservice.html
It uses the @Stateful annotation and returns and endpoint to the user that
maintains the state.
I don't see how this can be done with CXF, or at least it's not documented
well.
