I take it you tried something like this in your client
client = new ServiceClient(cfgCntxt, null);
stuff
client.engageModule("rampart");
client.engageModule("addressing");
(you may not care about the addressing)
Brian
-----Original Message-----
From: Robert Hall (JIRA) [mailto:[email protected]]
Sent: Wednesday, November 20, 2013 5:24 PM
To: [email protected]
Subject: [jira] [Created] (AXIS2-5618) Unable to engage rampart at client side
when using it as a classpath resource
Robert Hall created AXIS2-5618:
----------------------------------
Summary: Unable to engage rampart at client side when using it as
a classpath resource
Key: AXIS2-5618
URL: https://issues.apache.org/jira/browse/AXIS2-5618
Project: Axis2
Issue Type: Bug
Components: client-api
Affects Versions: 1.5.2
Environment: Mac OS, Java 1.6, Liferay portal
Reporter: Robert Hall
I have a bug in which I cannot access rampart from the classpath. I'm using
Axis2 for client webservices in a deployment environment, I can't access a
repository/modules folder with the rampart.mar file as I can when running a
test client from the command line. I've tried placing the rampart file
directly on the classpath and in a modules folder on the classpath.
I try and engage rampart with
contextWSStub._getServiceClient()..engageModule(new QName("rampart")); but to
no avail, at run time I get org.apache.axis2.AxisFault: Unable to engage module
: rampart
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4158 / Virus Database: 3629/6851 - Release Date: 11/20/13
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4158 / Virus Database: 3629/6851 - Release Date: 11/20/13
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
