[AXIS2-5618] Unable to engage rampart at client side when using it as a classpath resource

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 1.5.2
• Component/s: client-api
• Environment: Mac OS, Java 1.6, Liferay portal
• Assignee: Unassigned
• Reporter: Robert Hall
• Created: 20/Nov/13 22:23
• Updated: 22/Nov/13 18:06
• Resolved: 22/Nov/13 02:23

Description

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