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

2013-11-22 Thread Martin Gainty (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13829971#comment-13829971 ] Martin Gainty commented on AXIS2-5618: -- build..package..and deploy routines are

RE: [jira] [Commented] (AXIS2-5618) Unable to engage rampart at client side when using it as a classpath resource

2013-11-22 Thread Brian Reinhold
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

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

2013-11-22 Thread Robert Hall (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13830177#comment-13830177 ] Robert Hall commented on AXIS2-5618: I actually don't have a pom.xml, the 3rd party

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

2013-11-21 Thread Martin Gainty (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13829580#comment-13829580 ] Martin Gainty commented on AXIS2-5618: -- 'standard location for axis2 modules' is

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

2013-11-21 Thread Robert Hall (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13829595#comment-13829595 ] Robert Hall commented on AXIS2-5618: I resolved it..i was using a generated client