Martin, Sorry I don't have OSX either. I just recall having the same error some time ago and it was because I did not engage it (client) programmatically. I am not sure how one uses modules on the client side though it may be possible. I have so far avoided use of xml configuration on the client side.
Brian -----Original Message----- From: Martin Gainty (JIRA) [mailto:[email protected]] Sent: Friday, November 22, 2013 8:37 AM To: [email protected] Subject: [jira] [Commented] (AXIS2-5618) Unable to engage rampart at client side when using it as a classpath resource [ https://issues.apache.org/jira/browse/AXIS2-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13829971#comment-13829971 ] Martin Gainty commented on AXIS2-5618: -------------------------------------- build..package..and deploy routines are implemented by Maven pom.xm and are thus version/classifier specific 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 : <properties> <axis2.version>1.7.0-SNAPSHOT</axis2.version> <axiom.version>1.2.15-SNAPSHOT</axiom.version> <!-- here is axiom --> <wss4j.version>1.6.4</wss4j.version> <opensaml.version>2.5.1-1</opensaml.version> <bcprov.jdk15.version>140</bcprov.jdk15.version> <!-- distribution properties --> <dist.dir>rampart-${project.version}</dist.dir> <failIfNoTests>false</failIfNoTests> <jacoco.version>0.6.1.201212231917</jacoco.version> </properties> <!-- Since Rampart depends on DOOM, but axiom-dom is not a transitive dependency, we need to manage the Axiom version. --> <dependency> <groupId>org.apache.ws.commons.axiom</groupId> <artifactId>axiom-api</artifactId> <version>${axiom.version}</version> </dependency> Many Thanks for identifying this bug Robert (and Brian) Martin-- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
