Uhm... ok, maybe I didn't articulate that properly. I guess I was looking for something simple but exactly like the spring-client and spring examples. Seriously man, exactly like those example except without jsp's and with a swing login/logout. That's it. Not the world. Just an example of how you guys suggest setting the sessionId in the remoteInvocationFactory after those remote services have already been injected during initialization.
I have a bad feeling that I am going to lose the ability to inject all of my remote services during initialization and have to manually do it after I login because the SESSIONID is final and there is no setter. But, I am hoping you have a mechanism for this. Maybe even a class that I can extend of which I would inject during init and then it would use a dynamic method to retrieve the nice new session id I just got back from my swing based login. I sure hope I am missing something very obvious so really just an example that shows how to keep my dependency injection of all my spring remote services and still set that sessionId dynamically is all I need. It should only be a few lines of code and maybe point me to a few classes And I didn't feel I was reading into it. I feel examples are meant to provide developers a quick start to common problems. To have a jsp login to launch a webstart app is not common, or so I believe. Actually, webstart provides a mechanism to bypass a browser altogether once it has been run and this was very appealing to me and I am aware to many others. Plus the spring-hibernate very clearly demonstrates the jsp based approach. So the injecting of the sessionId into the remoteInvocationFactory AFTER getting it back from a call in a desktop app is very sorely missing. -- View this message in context: http://shiro-user.582556.n2.nabble.com/Best-way-to-associate-Session-to-SecureRemoteInvocationFactory-tp5541140p5541440.html Sent from the Shiro User mailing list archive at Nabble.com.
