Ohh,
Well, its really on the server. I only do the following on the client
System.setProperty("shiro.session.id", StringUtil.safeString(result));
This is what was suggested to me (I think by you) on the client side so that
the org.apache.shiro.spring.remoting.SecureRemoteInvocationFactory would
have it available. This was because I actually have a swing login screen and
couldn't set the SESSION_ID on one of the jnlp arguments. That is basically
all I have that is shiro related on the client. Should I be doing more
there?
Brian
--
View this message in context:
http://shiro-user.582556.n2.nabble.com/SessionListeners-with-Spring-and-a-Swing-Desktop-tp5715272p5731169.html
Sent from the Shiro User mailing list archive at Nabble.com.
