admin@glassfish.java.net

[Fwd: Returned mail: see transcript for details]

From: Hong Zhang <Hong.Zhang_at_Sun.COM>
Date: Tue, 10 Oct 2006 15:55:23 -0400

Re-send

attached mail follows:



The original message was received at Tue, 10 Oct 2006 13:51:49 -0600 (MDT)
from [192.18.108.178]

   ----- The following addresses had permanent fatal errors -----
<admin_at_dev.glassfish.java.net>
    (reason: 550 Host unknown)

   ----- Transcript of session follows -----
550 5.1.2 <admin_at_dev.glassfish.java.net>... Host unknown (Name server: dev.glassfish.java.net: host not found)

attached mail follows:



Hi,
   I am re-submitting this domain.xml change request for
"extension-module" for glassfish 9.1. I have updated the wiki page with
this information.
   Please see more details or provide comments here in this glassfish
issue:
       https://glassfish.dev.java.net/issues/show_bug.cgi?id=886

   Thanks,

- Hong


We need to support an extensible application type in the domain.xml so
non Java EE applications have a chance to be registered and use our
infrastructure for deployment lifecycle and infrastructure. I would like
to request these DTD changes to the domain.xml to support such use case.

<!ELEMENT applications
   ((lifecycle-module | j2ee-application | ejb-module | web-module
| connector-module | appclient-module | mbean |
extension-module)*)>
<!-- extension-module
 Extension modules are not handled directly by the application server
runtime
 They usually are add-ons container that are installed on top of the basic
 installation. The type of such applicative extensions is used to match
deployed
 artifacts with installed add-ons.

 attributes
   module-type
       String representing the module type. This module type will be used
        by the runtime to find the appropriate add-on container.
--> <!ELEMENT extension-module (description?, property*)>

<!ATTLIST extension-module
   name CDATA #REQUIRED
   location CDATA #REQUIRED
   module-type CDATA #REQUIRED
   object-type %object-type; "user"
   enabled %boolean; "true"
   libraries CDATA #IMPLIED
   availability-enabled %boolean; "false"
   directory-deployed %boolean; "false">