title: JAX-WS client using Applet
body: <p>It seems like I'm falling into a problematic scenario when combining JAX-WS architecture together with session management all that by using Applet client.</p>
  
  <p>In order to maintain session I've added to the client's port the following property <code>BindingProvider.SESSION_MAINTAIN_PROPERTY</code>.</p>
  
  <p>However, the thing is that when I invoke two instances of the applet (accessing the website on two tabs) simultaneously, the session gets mixed between the two clients. My suspicious is that this has to do with the fact that multiple applet instances use the same JVM instance and thus, static code is shared between them. However, I cannot figure out which part is being used in both instances.</p>
  
  <p>I've positively verified that this issue of session mixture only occurs when running instances simultaneously from the same browser, i.e. when JVM static code is shared. In other words, the session management code works correctly in any other case that I've tested.</p>