At 12:55 11/10/00 +0100, you wrote:
>"Berin Loritsch" <[EMAIL PROTECTED]> writes:
>
>> The new configuration system will have a way to not only type check and
validate
>> your Configuration objects, but prepopulate things like the class attribute
>> so that the administrator doesn't have to see that--it's the developer's
job.
>>
>> It's slow going, so don't expect it in the next Avalon release....
>>
>
>Isn't population part of configuration ? Why should the developer deal with
>things that is clearly within your admins domain ?
population is part of assemblers role. Assembler is the one that
"assembles" the server application. When Berin talks about developer I
believe he means developer as both assembler and block writer. I believe
the reason for seperating these roles is either on Avalon webpage, EJB
specification or Enterprise blueprints (can't remember at the moment ;-P~).
Loose definition of admin previously took on roles of assembler, deployer
and maintainer but these are seperated because it is unreasonable for the
roles to be intermingled. The same person can fulfill multiple roles but
that should npot be a requirement.
Cheers,
Pete
*------------------------------------------------------*
| "Nearly all men can stand adversity, but if you want |
| to test a man's character, give him power." |
| -Abraham Lincoln |
*------------------------------------------------------*
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
