Uploaded image for project: 'JBoss Web Services'
  1. JBoss Web Services
  2. JBWS-2057

Metro stax integration has a hardcoded dependency

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • jbossws-metro-3.0.1
    • None
    • None
    • None

      The tools scripts in framework somehow try to define a union of all dependencies across stacks.

      1. JBossWS-Metro stack libraries
        WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$LIBDIR/jbossws-metro-client.jar"
      1. JBossWS-Native stack libraries
        WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$LIBDIR/javassist.jar"
        WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$LIBDIR/jboss-xml-binding.jar"
        WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$LIBDIR/jbossws-client.jar"
        WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$LIBDIR/jboss-jaxws.jar"
        WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$LIBDIR/jboss-jaxrpc.jar"
        WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$LIBDIR/jboss-saaj.jar"

      This is incorrect and broken for the stax integration

      Metro uses wstx-asl-3.2.1 which should not be hardcoded anywhere. Instead its version needs to be pulled from
      version.properties.

              rhn-support-hbraun Heiko Braun
              tdiesler@redhat.com Thomas Diesler
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: