Issue Details (XML | Word | Printable)

Key: GLASSFISH-15110
Type: Bug Bug
Status: Open Open
Priority: Minor Minor
Assignee: Sanjeeb Sahoo
Reporter: Dies Koper
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
glassfish

unclear warning "setRuntimeDDPresent method not implemented" from verifier

Created: 11/Dec/10 05:51 AM   Updated: 11/Mar/13 04:04 AM
Component/s: verifier
Affects Version/s: 3.1_b33
Fix Version/s: not determined

Time Tracking:
Not Specified

File Attachments: 1. File is_classloader-web.war (5 kB) 11/Dec/10 05:51 AM - Dies Koper

Environment:

Windows XP


Tags:
Participants: Dies Koper and Sanjeeb Sahoo


 Description  « Hide

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.


Dies Koper added a comment - 11/Dec/10 05:53 AM

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 added a comment - 11/Dec/10 06:59 AM

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.