Nazrul,
The strategy for AMX is on the table at this point, at least for V3
final. For Prelude, we could continue as-is (labor required),
presumably so that GUI can work on anything newly added.
My functional spec (not yet published) is to move to a completely
generic AMX which requires no developer effort whatsoever, though
possibly optional features. This really is a key requirement for a
modular, pluggable system.
So yes, the deployment team could add AMX interfaces, but I'm loathe
to extend the existing model should we settle on the generic approach.
Lloyd
On Jul 15, 2008, at 6:55 PM, Nazrul Islam wrote:
> glassfish_at_javadesktop.org wrote:
>> Please provide us comments/feedback on the proposed deployment
>> features in Glassfish v3 Prelude release.
>>
>> The deployment one-pager can be found here:
>> http://wiki.glassfish.java.net/Wiki.jsp?page=Deploymentv3PreludeOnePager
>>
> Thank you for starting this thread. For application management, here
> are some comments:
> URL: http://wiki.glassfish.java.net/Wiki.jsp?page=AppMgtv3PreludeOnePager
>
> 1) Please clarify the proposed configuration changes to domain.xml.
> 2) Administration Infrastructure spec does not cover the changes for
> AMX (or CLI). Please specify the proposed new AMX interfaces.
> 3) Will there be an api that will inform clients (GUI, CLI) that
> certain changes requires application to be restarted or redeployed?
> An example usage would be great.
> 4) Section 4.1 suggests that we may need re-deployment of
> applications. Are we planning to support edit of deployment
> descriptors also? If it is only domain.xml configuration, why would
> you need to redeploy?
> --
> Nazrul Islam - (408) 276-6468 - Sun Microsystems, Inc.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>