Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-7644

Enforce EE 6 module name requirements within an application

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Critical Critical
    • 6.0.0.M3
    • None
    • None
    • None

      Implement following from EE8.1.1:

      All Java EE modules have a name. The name can be explicitly set in the
      deployment descriptor for the module. If not set, the name of the module is the
      pathname of the module in the ear file with any filename extension (.jar, .war,
      .rar) removed, but with any directory names included. The name of a module
      must be unique within an application. If and only if the name is not unique (e.g.,
      because two names are identical after removing different filename extensions) the
      deployment tool may choose new unique names for any of the conflicting
      modules; module names that do not conflict must not be changed. The algorithm
      for choosing unique names in such a case is product specific.

      Also implement this related bit from EE.8.1.2:

      Similarly, when a stand-alone module is deployed.... The module name can be explicitly set in the module
      deployment descriptor. If not set, the name of the module is the base name of the
      module file with any extension (.war, .jar, .rar) removed and with any directory
      names removed.

              bstansbe@redhat.com Brian Stansberry
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: