Policy File with AXIS

[Mike Litherland]

Hi,

I'm deploying a web service that forwards messages it gets over SOAP to a JMS topic on a different machine. The code works when calling it not as a web service, but fails with permission issues when called from AXIS.

I think they key is to give it resolve,connect permissions in a policy file, but I'm not sure how to deploy a policy along with a class in Apache AXIS. The AXIS documentation is horribly lacking in many respects so I'm wondering if anybody here has familiarity with doing this. It has to be fairly common to use SOAP as a bridge to JMS, JDBC and other remote services.

Thanks,
Mike Litherland
Cleveland Clinic Foundation

[William Brogden]

If your AXIS service is running under Tomcat, the catalina.policy file is where you can specify that it has specific permissions. I went through this sort of thing trying to get a Tomcat servlet to talk to a JavaSpace. I ended up with this entry in catalina.policy:

grant codeBase "file:${catalina.home}/webapps/javaspace/WEB-INF/classes/-" {
  permission java.security.AllPermission;
};
  

Documentation on this sort of problem is indeed very hard to find. I found the _Professional Apache Tomcat 5_ book (Wrox press) to have the best summary.
Bill

[Mike Litherland]

Bill - thanks for the helpful information. I'll be looking into picking up a copy of the book you recommended.

With a fresh eye after a good night's sleep I realized that I was missing two of the jar files needed for my JMS code to work properly. Once those were placed in the catalina lib directory things proceeded to work. Unfortunately, this was a case of me out looking for a problem and ignoring some of the basics.

Thanks again,
Mike

[William Brogden]

I went through exactly the same thing with JavaSpaces - there was no list of which jar file was essential for which function.
In desperation I just copied all the JARs that came with the toolkit into the ../shared/lib directory. I'm sure many of them are un-needed but which ones?
Bill