Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.0
    • Fix Version/s: milestone 1
    • Component/s: migrationtool
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      11

      Description

      If you attempt to use Migration Tool with Java SE 6(JDK), then the
      java.lang.NoSuchMethodError is thrown. See the attached exception.log

        Activity

        Hide
        sekhar added a comment -

        Created an attachment (id=10)
        java.lang.NoSuchMethodError exception stack trace

        Show
        sekhar added a comment - Created an attachment (id=10) java.lang.NoSuchMethodError exception stack trace
        Hide
        sekhar added a comment -

        The problem is caused because Java SE 6 bundles JAXB and so does Migration Tool.
        The two versions are different and the mismatch is causing the exception. The
        problem can show if for e.g. Migration Tool is used with a GlassFish
        distribution that has Java SE 6 bundled such as the Java EE + JDK bundle from
        http://java.sun.com/javaee/downloads/index.jsp

        The workaround is to use Migration Tool with GlassFish + Java SE 5 (JDK) i.e.
        download GlassFish distribution without Java SE bundled and Java SE 5 separately
        and set Migration Tool env vars - J2EE_HOME and JAVA_HOME accordingly.

        Alternately, if Java EE + JDK bundle has been downloaded from
        http://java.sun.com/javaee/downloads/index.jsp , then download Java SE 5 (JDK)
        and set JAVA_HOME accordingly. This seems to override the JDK 6 installed with
        Java EE + JDK bundle. I verified Migration Tool runs successfully but I don't
        know what if any are the problems with this approach.

        Show
        sekhar added a comment - The problem is caused because Java SE 6 bundles JAXB and so does Migration Tool. The two versions are different and the mismatch is causing the exception. The problem can show if for e.g. Migration Tool is used with a GlassFish distribution that has Java SE 6 bundled such as the Java EE + JDK bundle from http://java.sun.com/javaee/downloads/index.jsp The workaround is to use Migration Tool with GlassFish + Java SE 5 (JDK) i.e. download GlassFish distribution without Java SE bundled and Java SE 5 separately and set Migration Tool env vars - J2EE_HOME and JAVA_HOME accordingly. Alternately, if Java EE + JDK bundle has been downloaded from http://java.sun.com/javaee/downloads/index.jsp , then download Java SE 5 (JDK) and set JAVA_HOME accordingly. This seems to override the JDK 6 installed with Java EE + JDK bundle. I verified Migration Tool runs successfully but I don't know what if any are the problems with this approach.

          People

          • Assignee:
            sekhar
            Reporter:
            sekhar
          • Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: