axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Hall (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AXIS2-5618) Unable to engage rampart at client side when using it as a classpath resource
Date Fri, 22 Nov 2013 02:24:38 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Hall closed AXIS2-5618.
------------------------------


> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message