Axis2
  1. Axis2
  2. AXIS2-3213

Axis2's build.xml file for Axis2.war excludes the axis2-codegen-1.3.jar file needed by Rampart 1.3

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.3, 1.5.2
    • Fix Version/s: 1.5.3, 1.6.0
    • Labels:
      None
    • Environment:
      Axis2 1.3 Rampart 1.3 Windows 2K

      Description

      The build.xml file contained in axis2-1.3/webapp that builds the axis2.war contains the statement "<exclude name="axis2-codegen*.jar"/> ". Unfortunately this file is required to resolve Rampart 1.3's ModulePolicyExtension reference. Clearly the exclusion needs to be removed from the build.xml file.

        Issue Links

          Activity

          Hide
          Deepal Jayasinghe added a comment -

          I can not understand why we need codegen jar at the runtime ?

          Thanks
          Deepal

          Show
          Deepal Jayasinghe added a comment - I can not understand why we need codegen jar at the runtime ? Thanks Deepal
          Hide
          Jon Hanshew added a comment -

          As I mentioned in the comment, "Unfortunately this file is required to
          resolve Rampart 1.3's ModulePolicyExtension reference."

          Rampart uses the ModulePolicyExtension class and it happens to be in
          the codegen-1.3.jar. Don't ask me why. Ask some Rampart guys. Please
          see

          https://issues.apache.org/jira/browse/RAMPART-76

          It was marked "Invalid" correctly by Ruchith Udayanga Fernando (see
          comment in Jira)

          The error is really an Axis2 bug as I have reported.

          Thanks for looking into this matter.

          Jon

          Show
          Jon Hanshew added a comment - As I mentioned in the comment, "Unfortunately this file is required to resolve Rampart 1.3's ModulePolicyExtension reference." Rampart uses the ModulePolicyExtension class and it happens to be in the codegen-1.3.jar. Don't ask me why. Ask some Rampart guys. Please see https://issues.apache.org/jira/browse/RAMPART-76 It was marked "Invalid" correctly by Ruchith Udayanga Fernando (see comment in Jira) The error is really an Axis2 bug as I have reported. Thanks for looking into this matter. Jon
          Hide
          Davanum Srinivas added a comment -

          latest war that i built on trunk seems to have axis2-codegen-SNAPSHOT.jar

          Show
          Davanum Srinivas added a comment - latest war that i built on trunk seems to have axis2-codegen-SNAPSHOT.jar
          Hide
          Tim Williams added a comment -

          With axis2-1.4 it doesn't appear to be fixed. Looking at the create.war target in webapp\build.xml, it seems that the jar is still specifically excluded.

          I built the war by:
          cd %AXIS2_HOME%\webapp
          ant create.war

          --tim

          Show
          Tim Williams added a comment - With axis2-1.4 it doesn't appear to be fixed. Looking at the create.war target in webapp\build.xml, it seems that the jar is still specifically excluded. I built the war by: cd %AXIS2_HOME%\webapp ant create.war --tim
          Hide
          Andreas Veithen added a comment -

          AXIS2-4065 provides some explanation about why the codegen JAR is required at runtime. As reported by Dennis Sosnoski, the issue still exists. BTW, the WAR artifact produced by Maven also includes the codegen JARs, so we might as well include it in the WAR produced by build.xml.

          Show
          Andreas Veithen added a comment - AXIS2-4065 provides some explanation about why the codegen JAR is required at runtime. As reported by Dennis Sosnoski, the issue still exists. BTW, the WAR artifact produced by Maven also includes the codegen JARs, so we might as well include it in the WAR produced by build.xml.

            People

            • Assignee:
              Andreas Veithen
              Reporter:
              Jon Hanshew
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development