I am trying to create a communication between two web services; an external web service and an internal web service. I've created a client.jar file for the internal web service. This client.jar file works perfectly fine when I use it in my web applications to call methods from the internal web services stub code, but when I try to call the same methods from my external web service, I get a sealing violation.
logs 2009-02-18 20:46:04,791 ERROR [mil.disa.wbbr.revokeService. impl.ExternalRevokeServiceImpl] - RevokeServiceImpl::getExternalStatus - exception:java.lang.SecurityException: sealing violation: package org.apache.axis2.addressing is sealed 2009-02-18 20:46:04,791 ERROR [mil.disa.wbbr.revokeService.impl.ExternalRevokeServiceImpl] - RevokeServiceImpl::getExternalStatus - message:sealing violation: package org.apache.axis2.addressing is sealed code static String target = "http://10.1.2.12:1683/axis2/services/RevocationServer";; RevocationServerStub stub = new RevocationServerStub(target); RevocationStatus[] revStatus = stub.getRevocationStatus(uuid); <- This is what causes the error. I started to track down the jars to find out where the package "org.apache.axis2.addressing" was located and I found it in two places. WEB-INF/modules/addressing-1.4.mar has a package called org/apache/axis2/addressing/ WEB-INF/lib/axis2-kernel-1.4.jar also has a package called org/apache/axis2/addressing/ I suspect that one of the web service calls is triggering a method to call/include one of those packages which is sealed. Has anyone else run across this issue and found a solution? Joe -- View this message in context: http://www.nabble.com/Sealing-Violation-tp22089545p22089545.html Sent from the Axis - User mailing list archive at Nabble.com.
