Yes, Kedar's spec does say that. But Jerome is the lead on the project
and I think he ultimately sets the standards. Lloyd also has
considerable influence as the AMX architect.
June
Dixie Pine wrote:
> But didn't Kedar say just the opposite, that users /would/ have to
> edit domain.xml for Prelude? Am I hallucinating?
>
> June.Parks_at_Sun.COM wrote:
>> Thanks for the clarification. It is reassuring that direct edits to
>> domain.xml will not be necessary, and that "manual configuration"
>> refers to use of the GUI or CLI. I still think we should have some
>> way of validating domain.xml, however.
>>
>> June
>>
>> Jerome Dochez wrote:
>>>
>>> On Jul 17, 2008, at 5:23 PM, Lloyd Chambers wrote:
>>>
>>>> As far as I know, when a module is added its interface defines any
>>>> required values and any default values (if needed) and everything
>>>> else is null.
>>>>
>>>> So we have value that are:
>>>>
>>>> a) not required (optional)
>>>> b) required and has a default defined by the interface
>>>> c) required, but a default value cannot be defined in advance
>>>>
>>>> Item (c) is the issue.
>>>>
>>>> A module writer should take this into account by gracefully
>>>> degrading service until such time as it is configured via the GUI
>>>> or asadmin. No one should have to edit domain.xml.
>>> I agree. I was giving the GrizzlyService example yesterday, if there
>>> are no configuration, then we don't open a single port...
>>>>
>>>>
>>>> Also, a module should attempt to set defaults for all required
>>>> values, even if that means things like port conflicts might happen.
>>> right.
>>>
>>> Jerome
>>>
>>>>
>>>>
>>>> Lloyd
>>>>
>>>> On Jul 17, 2008, at 1:11 PM, Kedar Mhaswade wrote:
>>>>
>>>>> I agree. But that's what the plan of record had been.
>>>>> I will try to improve the situation, but not for Prelud
>>>>>
>>>>> Thanks.
>>>>>
>>>>> June.Parks_at_Sun.COM wrote:
>>>>>> If I'm reading the spec right, the default domain.xml is minimal,
>>>>>> there is no DTD or schema validation, yet when users add modules
>>>>>> they have to add the module configuration by hand. This is a
>>>>>> recipe for disaster. Such a copy-paste-edit process is highly
>>>>>> error-prone.
>>>>>> If we can tell users what to copy and paste, we can and should
>>>>>> make GF copy and paste for them. When a user adds a standard GF
>>>>>> module using the Update Center, for example the EJB container
>>>>>> module or the Metro module, the installation of that module
>>>>>> should add the module configuration automatically, with defaults
>>>>>> that the user can then change.
>>>>>> June
>>>>>> Kedar Mhaswade wrote:
>>>>>>> Just to let you know that I have received lot of feedback on the
>>>>>>> infrastructure
>>>>>>> review at asarch. People have a lot to comment on.
>>>>>>>
>>>>>>> I have also received feedback comments in the e-mail. I will be
>>>>>>> incorporating
>>>>>>> those comments in a day or two.
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Kedar
>>>>>>>
>>>>>>> (PS - the review is not yet complete)
>>>>>>>
>>>>>>> Lloyd Chambers wrote:
>>>>>>>> Accessible via:
>>>>>>>>
>>>>>>>> https://glassfish.dev.java.net/nonav/v3/admin/planning/prelude/admin-infra-prelude.html
>>>>>>>>
>>>>>>>>
>>>>>>>> ..............................................
>>>>>>>> Lloyd Chambers
>>>>>>>> lloyd.chambers_at_sun.com
>>>>>>>> GlassFish team, admin
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Jul 14, 2008, at 11:09 AM, Lloyd Chambers wrote:
>>>>>>>>
>>>>>>>>> Kedar's spec is now checked into cvs; I keep a "v3-docs" dir
>>>>>>>>> on my machine; 'www/v3/admin/planning' is the checkout-out
>>>>>>>>> hierarchy.
>>>>>>>>>
>>>>>>>>> /v3-docs/www/v3/admin/planning
>>>>>>>>>
>>>>>>>>> /cvs/glassfish/www/v3/admin/planning/prelude/admin-infra-prelude.html,v
>>>>>>>>> <-- admin-infra-prelude.html
>>>>>>>>>
>>>>>>>>> *To check out:*
>>>>>>>>> cvs -d :pserver:YOUR_LOGIN_at_cvs.dev.java.net
>>>>>>>>> <mailto:YOUR_LOGIN_at_cvs.dev.java.net>:/cvs co www/v3
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ... Now I have to find out how can make glassfish.dev.java.net
>>>>>>>>> expose www/v3 as an accessible URL.
>>>>>>>>>
>>>>>>>>> Lloyd
>>>>>>>>> ..............................................
>>>>>>>>> Lloyd Chambers
>>>>>>>>> lloyd.chambers_at_sun.com <mailto:lloyd.chambers_at_sun.com>
>>>>>>>>> GlassFish team, admin
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Jul 13, 2008, at 5:36 PM, Kedar Mhaswade wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I have finally been able to post a "ready for review" draft
>>>>>>>>>> of the functional
>>>>>>>>>> specification to the GlassFish Wiki.
>>>>>>>>>>
>>>>>>>>>> In my view, it is more or less complete description of what
>>>>>>>>>> we have to do
>>>>>>>>>> for GlassFish Prelude. Of course, there will be adjustments
>>>>>>>>>> based on what we
>>>>>>>>>> "can" possibly do. That's what review is for.
>>>>>>>>>>
>>>>>>>>>> The arch review of this spec is scheduled for Wednesday, July
>>>>>>>>>> 16 at 11.00
>>>>>>>>>> a.m. Pacific. There are two things remaining from the spec
>>>>>>>>>> but I am sure
>>>>>>>>>> the review can progress before they are "complete". They are:
>>>>>>>>>>
>>>>>>>>>> 1- accurate list of asadmin commands. This seeds test
>>>>>>>>>> specification,
>>>>>>>>>> documentation and all other teams. It's a must that we agree
>>>>>>>>>> on these.
>>>>>>>>>>
>>>>>>>>>> 2- association of tasks and owners. This is an activity I'll
>>>>>>>>>> do in
>>>>>>>>>> conjunction with Nazrul and others.
>>>>>>>>>>
>>>>>>>>>> Here is the document which tomorrow's discussion revolves
>>>>>>>>>> around:
>>>>>>>>>> http://wiki.glassfish.java.net/attach/V3FunctionalSpecs/admin-infra-prelude.html
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> There are some surprises in the spec and I am sure there is
>>>>>>>>>> lot to discuss.
>>>>>>>>>> I expect many of us to be available tomorrow morning at 10.00
>>>>>>>>>> a.m. Pacific
>>>>>>>>>> for the discussion.
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Kedar
>>>>>>>>>> km_at_dev.java.net
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Sreenivas Munnangi wrote:
>>>>>>>>>>> Hi,
>>>>>>>>>>> Following agenda for next admin iTeam meeting includes
>>>>>>>>>>> discussion on admin strategy for JMX and Security. Pl. come
>>>>>>>>>>> preperaed to discuss.
>>>>>>>>>>> thanks
>>>>>>>>>>> sreeni
>>>>>>>>>>> Agenda for 14jul2008
>>>>>>>>>>> 1. Review of action items
>>>>>>>>>>> 2. V3 Prelude deliverables - Milestone 1 (14jul08), SCF
>>>>>>>>>>> (04aug08)
>>>>>>>>>>> 3. Discussion on overall admin strategy for JMX, security
>>>>>>>>>>> 4. Update by QA, Documentation and Development Teams
>>>>>>>>>>> 5. Customer Interaction, Arch. update if any
>>>>>>>>>>> 6. Open Mic.
>>>>>>>>>>> Meeting Details:
>>>>>>>>>>> Mondays 10-11 AM Pacific
>>>>>>>>>>> (866)545-5227 (US Toll-Free)
>>>>>>>>>>> (865)673-6950 (International-Caller Paid)
>>>>>>>>>>> Access Code: 3535518#
>>>>>>>>>>> Email aliases: admin_at_glassfish.dev.java.net
>>>>>>>>>>> http://wiki.glassfish.java.net/Wiki.jsp?page=GlassFishV2AdminMeetings
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>> admin-help_at_glassfish.dev.java.net
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>>>>>>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>