The ACEGI authentication example of the airline app is interesting, but i have problem to understand it completly.
The client has a callback handler which sets the username and password. That's ok. But i thought i get something like a session ticket back to call web services. But i doesn't see one.
I also thought i should at something like the session ticket to my wsdl specification.
How does it work in the airline app? Needs the authentication done for every request again in the airline example?
<soap:header use="literal" message="tns:Header" part="mySessionHeader"/>
How can i archive the session key strategy with Spring-WS and ACEGI?