Uploaded image for project: 'Axis2'
  1. Axis2
  2. AXIS2-5618

Unable to engage rampart at client side when using it as a classpath resource

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Not A Problem
    • Affects Version/s: 1.5.2
    • Fix Version/s: None
    • Component/s: client-api
    • Labels:
      None
    • Environment:
      Mac OS, Java 1.6, Liferay portal

      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

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              robertwhall Robert Hall
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: