dev@glassfish.java.net

any thoughts on bug #6342808?

From: Lloyd L Chambers <lloyd.chambers_at_Sun.COM>
Date: Thu, 27 Oct 2005 13:03:08 -0700

Jan,

6342808 "JSR 77 specification violation when deploying sample app
jndi-url.ear"

Deploy sample application 'jndi-url.ear' (I used the GUI). Observe the
following MBeans ("com.sun.appserv:" omitted for clarity):

j2eeType=AppClientModule,name=jndi-urlClient.jar,J2EEServer=server,J2EEApplication=jndi-url,category=runtime

j2eeType=EJBModule,name=jndi-urlEjb.jar,J2EEServer=server,J2EEApplication=jndi-url,category=runtime

j2eeType=J2EEApplication,name=jndi-url,J2EEServer=server,category=runtime
j2eeType=StatefulSessionBean,name=jndi-urlEJB,J2EEServer=server,J2EEApplication=jndi-url,EJBModule=jndi-urlEjb.jar,category=runtime

j2eeType=WebModule,name=//server/jndi-url,J2EEServer=server,J2EEApplication=null


PROBLEM: j2eeType=WebModule,name=//server/jndi-url has
'J2EEApplication=null'. According to the JSR 77 spec, it must have
'J2EEApplication=jndi-url'. Also, there is no 'category=runtime'
property as with the other JSR 77 MBeans associated with this application.

HOWEVER: Is this some kind of special case? The archive 'jndi-url.ear'
doesn't contain any 'war' file. Is there some special case in which a
WebModule is implicitly loaded?
*** (#1 of 1): 2005-10-27 12:41:34 PDT lloyd.chambers_at_sun.com