Sorry for the previous null post. I did have one question. My client does
run in a separate VM as the server and the only way I was able to get this
to work was to pass the session id back to the client from the server (using
ehcache to cache the subject on the server) and than rebuild the subject on
the server on all subsequent calls using code I found on an earlier post.
Seems to be that the SecureRemotingInvocationFactory/Executor should have
done that for me but with the client running in a separate vm from the
server I kept getting exceptions on the client about my application not
being configured properly and missing a security manager. My question is if
you are running in two separate vms are you required to create a security
manager in each vm and "share" a session cache that can be accessed by both
vms to get this working. I am still a bit confused because all the examples
I have seen dont need to pass the session id around. It seems that
something was doing this beind the scenes and the only thing I can think of
is the SecureRemoting hooks.
--
View this message in context:
http://n2.nabble.com/Evaluation-Question-tp4251098p4256601.html
Sent from the Shiro User mailing list archive at Nabble.com.
