Uploaded image for project: 'Spring Web Services'
  1. Spring Web Services
  2. SWS-727

building a webapp targetting Java 1.5 environment on JDK5 and JDK6 pulled in different dependencies for spring-ws-core 2.0.2

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: 2.0.2, 2.0.3
    • Fix Version/s: 2.0.3
    • Component/s: Core
    • Labels:
      None

      Description

      Building a webapp targetting Java 1.5 envrionment with JDK1.6 as the build environment, doesn't pull in the maven dependency: javax.xml.stream : stax-api, which causes java.lang.ClassNotFoundException: javax.xml.stream.XMLStreamException.

      The expected result will be that the final artifacts from the build should be the same regardless of the Java version of the build environment. The dependencies should be based on the target Java runtime environment not the build environment.

      The following is found in spring-ws-core-2.0.2.RELEASE.pom file:

      <profile>
      <id>jdk15</id>
      <activation>
      <jdk>!1.6</jdk>
      </activation>
      <dependencies>
      <dependency>
      <groupId>javax.xml.stream</groupId>
      <artifactId>stax-api</artifactId>
      </dependency>

        Activity

        dj.meng Dejia Meng created issue -
        Hide
        arjen.poutsma Arjen Poutsma added a comment -

        The problem here is that javax.xml.stream is built into JDK 1.6, and not 1.5. Using JDK-profiles at least makes it easy to build, but they are not fool proof, i.e. you'll still have to think about the libraries for the deployment environment.

        In general, I would not recommend using a different JDK (version) than what deployment uses, but that's another discussion.

        Show
        arjen.poutsma Arjen Poutsma added a comment - The problem here is that javax.xml.stream is built into JDK 1.6, and not 1.5. Using JDK-profiles at least makes it easy to build, but they are not fool proof, i.e. you'll still have to think about the libraries for the deployment environment. In general, I would not recommend using a different JDK (version) than what deployment uses, but that's another discussion.
        arjen.poutsma Arjen Poutsma made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Assignee Arjen Poutsma [ arjen.poutsma ]
        Fix Version/s 2.0.3 [ 12197 ]
        Resolution Won't Fix [ 2 ]
        Hide
        arjen.poutsma Arjen Poutsma added a comment -

        Closing old issues

        Show
        arjen.poutsma Arjen Poutsma added a comment - Closing old issues
        arjen.poutsma Arjen Poutsma made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        42d 7h 3m 1 Arjen Poutsma 06/Oct/11 2:27 AM
        Resolved Resolved Closed Closed
        211d 4h 36m 1 Arjen Poutsma 04/May/12 7:03 AM

          People

          • Assignee:
            arjen.poutsma Arjen Poutsma
            Reporter:
            dj.meng Dejia Meng
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: