[
https://issues.apache.org/jira/browse/RAMPART-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516196
]
Chad DeBauch commented on RAMPART-63:
-------------------------------------
I have been using Rampart 1.2 with Axis2 1.2 on Websphere Application Server
6.1 successfully. I have not encountered a problem trying to engage the
module. To get Axis2 1.2 to work on Websphere 6.1 you have to change some
setting after you deploy the war in order for it to start up correctly. I
would verify that you are successfully deploying and starting up Axis2 1.2 on
Websphere 6.1 before you try to engage a module.
> Engaging Rampart 1.2 / Rampart 1.1 on Websphere 1.1
> ---------------------------------------------------
>
> Key: RAMPART-63
> URL: https://issues.apache.org/jira/browse/RAMPART-63
> Project: Rampart
> Issue Type: Bug
> Environment: Websphere 6.1
> Reporter: Pavan Madiraju
>
> 1) .I am running into issue while trying to engage Rampart 1.2 on Websphere
> 6.1. After copying the rampart1-2.mar in the modules folder. I see a faulty
> Rampart1.1 module when I click on available modules.
> Here is the error stack that I see on the console.
> B jar started: mejb.jar
> [7/28/07 2:50:46:638 EDT] 00000017 ModuleDeploye I
> org.apache.axis2.deployment.ModuleDeployer deploy Deploying module:
> addressing-1.2
> [7/28/07 2:50:46:689 EDT] 00000016 ApplicationMg A WSVR0221I: Application
> started: ManagementEJB
> [7/28/07 2:50:46:669 EDT] 00000017 ModuleDeploye E
> org.apache.axis2.deployment.ModuleDeployer deploy The rampart-1.2.mar module,
> which is not valid, caused org.apache.rampart.Rampart
>
> org.apache.axis2.deployment.DeploymentException: org.apache.rampart.Rampart
> at
> org.apache.axis2.deployment.repository.util.ArchiveReader.readModuleArchive(ArchiveReader.java:483)
> at
> org.apache.axis2.deployment.ModuleDeployer.deploy(ModuleDeployer.java:70)
> at
> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:587)
> at
> org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:200)
> at
> org.apache.axis2.deployment.RepositoryListener.init2(RepositoryListener.java:63)
> at
> org.apache.axis2.deployment.RepositoryListener.<init>(RepositoryListener.java:58)
> at
> org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:127)
> at
> org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:204)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:60)
> at
> org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:486)
> at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:406)
> at
> com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:185)
> at
> com.ibm.ws.wswebcontainer.servlet.ServletWrapper.init(ServletWrapper.java:316)
> at
> com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1119)
> 2. When I engage Rampart1.1 on Websphere 6.1. I am able to see the rampart
> 1.1 module in the modules list and engaged modules list I get an error for an
> unsecured webservice that was working fine before.
> Following is the error that i get.
> - <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:wsa="http://www.w3.org/2005/08/addressing";>
> - <soapenv:Header>
> <wsa:Action>http://www.w3.org/2005/08/addressing/soap/fault</wsa:Action>
> </soapenv:Header>
> - <soapenv:Body>
> - <soapenv:Fault>
> <faultcode>soapenv:Client</faultcode>
> <faultstring>java.lang.NoSuchMethodError:
> org/apache/axis2/context/MessageContext.isEngaged(Ljavax/xml/namespace/QName;)Z</faultstring>
>
> <detail />
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
