|
Right, got a servlet working as an RMI client under
tomcat 3.2! What seems to be the problem is that:
1.) You do need the -security option with an
editied tomcat.policy file to use RMI
2.) The following policy doesn't work:
grant codeBase
"file:${tomcat.home}/webapps/myapp" {
permission java.security.AllPermission; }; Equally, this doesn't allow SessionExample to work
either. I assume something outside my webapp is trying to access the RMI port or
access the session info. To test this, I put the following in my code - now my
RMI works, as does the SessionExample included with tomcat:
grant {
permission
java.security.AllPermission;
};
Obviously, I now have a wide open servlet engine.
What I have to find out now is what needs permission to create the RMI socket or
read session info....any ideas?
sam
|
