glassfish
  1. glassfish
  2. GLASSFISH-15110

unclear warning "setRuntimeDDPresent method not implemented" from verifier

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 3.1_b33
    • Fix Version/s: not determined
    • Component/s: verifier
    • Labels:
      None
    • Environment:

      Windows XP

      Description

      Check the output from the verifier. Am I supposed to implement a "setRuntimeDDPresent" method somewhere to make my application Java EE compliant?? That's the impression the tool is giving.

      D:\tests\GFv3.1\glassfish-3.1-b33-12_10_2010\glassfish3\glassfish>bin\verifier d:\shared\JavaEE\ExitTestAppClient.ear
      INFO: Total time to parse domain.xml: 101 milliseconds
      INFO: Cannot find javadb client jar file, derby jdbc driver will not be available by default.
      INFO: Verifying: [ d:\shared\JavaEE\ExitTestAppClient.ear ]
      WARNING: setRuntimeDDPresent method not implemented
      INFO: Verifying: [ ExitTestEjb_jar ]
      WARNING: setRuntimeDDPresent method not implemented
      INFO: Verifying: [ Client_jar ]
      WARNING: setRuntimeDDPresent method not implemented
      INFO:

      1. of Failures : 0
      2. of Warnings : 0
      3. of Errors : 0
        INFO: No errors found in the archive.

        Activity

        Dies Koper created issue -
        Hide
        Dies Koper added a comment -

        Ah, I accidentally attached a different test app. But this app gives the same message.
        (Note that the error about the missing class is expected. It's just that that should have been the only error displayed.)

        Show
        Dies Koper added a comment - Ah, I accidentally attached a different test app. But this app gives the same message. (Note that the error about the missing class is expected. It's just that that should have been the only error displayed.)
        Sanjeeb Sahoo made changes -
        Field Original Value New Value
        Fix Version/s 3.2 [ 10969 ]
        Hide
        Sanjeeb Sahoo added a comment -

        Since those warning and info message do not appear in the final report, I don't think it is a serious issue and indeed the submitter has already classified it as a MINOR issue. So, targeting it for 4.0. 3.1 is pretty close to release date and 3.2 will probably have different release requirement.

        Show
        Sanjeeb Sahoo added a comment - Since those warning and info message do not appear in the final report, I don't think it is a serious issue and indeed the submitter has already classified it as a MINOR issue. So, targeting it for 4.0. 3.1 is pretty close to release date and 3.2 will probably have different release requirement.
        Sanjeeb Sahoo made changes -
        Fix Version/s 4.0 [ 10970 ]
        Fix Version/s 3.2 [ 10969 ]
        Sanjeeb Sahoo made changes -
        Comment [ Since those warning and info message does not appear in the final report, I don't think it is a serious issue and indeed the submitter has already classified it as a MINOR issue. So, targeting it for 3.2. 3.1 is pretty close to release date. ]
        Sanjeeb Sahoo made changes -
        Fix Version/s not determined [ 11149 ]
        Fix Version/s 4.0 [ 10970 ]

          People

          • Assignee:
            Sanjeeb Sahoo
            Reporter:
            Dies Koper
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: