You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Santosh Raghavan (JIRA)" <ji...@apache.org> on 2007/08/17 21:14:30 UTC
[jira] Updated: (RAMPART-74) org.apachException in thread "main"
java.lang.NoSuchMethodError with Rampart 1.2
[ https://issues.apache.org/jira/browse/RAMPART-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Santosh Raghavan updated RAMPART-74:
------------------------------------
Description:
I saw quite a lot of folks having similar error. I thought I would post up details.
I enabled rampart1.2 on the Axis2 on the Tomcat Server. I created a test client that included a Timestamp in the header. When I executed the client I got this Error:
2007-08-17 13:27:16,211 DEBUG axis2client.TestAxis2Client - Request = <helloAxis2:Request xmlns:helloAxis2="http://localhost:8080/axis2/helloAxis2/">Homer Simpson</helloAxis2:Request>
2007-08-17 13:27:16,251 DEBUG org.apachException in thread "main" java.lang.NoSuchMethodError: org.apache.axis2.context.MessageContext.isEngaged(Ljavax/xml/namespace/QName;)Z
at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:53)
at org.apache.axis2.engine.Phase.invoke(Phase.java:383)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:433)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330)
at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:520)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:500)
at axis2client.TestAxis2Client.main(TestAxis2Client.java:51)
It turns out that axis2-security-1.1.jar conflicts with rampart-core-1.2.jar. If you remove the axis2-security-1.1.jar from the class path the problem goes away. axis2-security-1.1.jar comes with rampart 1.1, and it was left over in my lib directory.
Technically this is not a bug, just a config issue.
Santy
was:
I saw quite a lot of folks having similar error. I thought I would post up details.
I enabled rampart1.2 on the Axis2 on the Tomcat Server. I created a test client that included a Timestamp in the header. When I executed the client I got this Error:
2007-08-17 13:27:16,211 DEBUG axis2client.TestAxis2Client - Request = <helloAxis2:Request xmlns:helloAxis2="http://localhost:8080/axis2/helloAxis2/">Homer Simpson</helloAxis2:Request>
2007-08-17 13:27:16,251 DEBUG org.apachException in thread "main" java.lang.NoSuchMethodError: org.apache.axis2.context.MessageContext.isEngaged(Ljavax/xml/namespace/QName;)Z
at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:53)
at org.apache.axis2.engine.Phase.invoke(Phase.java:383)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:433)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330)
at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:520)
at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:500)
at axis2client.TestAxis2Client.main(TestAxis2Client.java:51)
It turns out that axis2-security-1.1.jar conflicts with rampart-core-1.2.jar. If you remove the axis2-security-1.1.jar from the class path the problem goes away. axis2-security-1.1.jar comes with rampart 1.1, and it was left over in my lib directory.
> org.apachException in thread "main" java.lang.NoSuchMethodError with Rampart 1.2
> --------------------------------------------------------------------------------
>
> Key: RAMPART-74
> URL: https://issues.apache.org/jira/browse/RAMPART-74
> Project: Rampart
> Issue Type: Bug
> Environment: Axis1.2, Rampart 1.2 on Tomcat
> Simple Client Executed from Within eclipse.
> Reporter: Santosh Raghavan
> Priority: Trivial
>
> I saw quite a lot of folks having similar error. I thought I would post up details.
> I enabled rampart1.2 on the Axis2 on the Tomcat Server. I created a test client that included a Timestamp in the header. When I executed the client I got this Error:
> 2007-08-17 13:27:16,211 DEBUG axis2client.TestAxis2Client - Request = <helloAxis2:Request xmlns:helloAxis2="http://localhost:8080/axis2/helloAxis2/">Homer Simpson</helloAxis2:Request>
> 2007-08-17 13:27:16,251 DEBUG org.apachException in thread "main" java.lang.NoSuchMethodError: org.apache.axis2.context.MessageContext.isEngaged(Ljavax/xml/namespace/QName;)Z
> at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:53)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:383)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:433)
> at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330)
> at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)
> at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:520)
> at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:500)
> at axis2client.TestAxis2Client.main(TestAxis2Client.java:51)
> It turns out that axis2-security-1.1.jar conflicts with rampart-core-1.2.jar. If you remove the axis2-security-1.1.jar from the class path the problem goes away. axis2-security-1.1.jar comes with rampart 1.1, and it was left over in my lib directory.
> Technically this is not a bug, just a config issue.
> Santy
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.