You need a client side message interceptor, which is implemented
by adding a behavior to the binding.
The first incoming message is then intercepted, the messagegroupId
header is extracted, and stored as addressing header in a
user-session-context-obj.
>From then on, with each outgoing message
100% true what Deeplal said!
What has said sop far is true. Scope="soapsession" in service.xml, engagement
of addressing at server and client; stop, you develop a .NET client and that's
where the nightmar begins. So develop first a axi2/j client enage addressing
and learn all about scope0"soapse
