Uploaded image for project: 'Geronimo'
  1. Geronimo
  2. GERONIMO-606

gbeans in an application plan have no module component in their name

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.0-M3
    • 1.0-M4
    • deployment
    • None

    Description

      If you have gbeans in an application plan their names have no component "J2EEModule=foo". Furthermore, references specifying only the name component will look for a gbean with a "null=null" component instead of J2EEModule=foo. I think this is because the ear-level j2eeContext has no module component, since there isn't really a module.

      What should the "module" component be for a gbean that is in an application but no module? Should we name them
      J2EEApplication=appname,J2EEModule=null
      whereas a gbean in a gbean plan gets
      J2EEApplication=null,J2EEModule=moduleName?

      Attachments

        Activity

          People

            djencks David Jencks
            djencks David Jencks
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: