axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Gainty (JIRA)" <>
Subject [jira] [Commented] (AXIS2-5618) Unable to engage rampart at client side when using it as a classpath resource
Date Fri, 22 Nov 2013 13:36:36 GMT


Martin Gainty commented on AXIS2-5618:

build..package..and deploy routines are implemented by Maven pom.xm and are thus version/classifier
If you show us the axiom dependency from the pom.xml in error we can correct
and refactor your error..Here is mine as an example:
rampart pom.xml :
        <axiom.version>1.2.15-SNAPSHOT</axiom.version>   <!-- here is axiom
        <!-- distribution properties -->

<!-- Since Rampart depends on DOOM, but axiom-dom is not a transitive
                 dependency, we need to manage the Axiom version. -->

Many Thanks for identifying this bug Robert (and Brian)

> Unable to engage rampart at client side when using it as a classpath resource
> -----------------------------------------------------------------------------
>                 Key: AXIS2-5618
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message