> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Mark Woon
> Sent: Wednesday, 06 March, 2002 00:23
> To: Avalon Developers List
> Subject: Roles and shorthand names
>
>
>
> If I have multiple components that have the same configuration needs
> (ie. a <dbpool> parameter), what's the best way to set up the
> configuration for these components? Right now, I'm writing separate
> configuration blocks for each. It would be nice if I could have the
> different components use the same configuration block. However, since
> these components have different roles, I must assign them separate
> shorthand names.
This isn't an answer - just a comment. I'm currently working on
getting a clean separation of some of these notions as part of the
service package and resolution of a viable mechanisms for defaults
all the up the chain form class meta-info up, through profiles
describing available named instantiation configurations, to roles
reflecting service instance deployment.
Cheers, Steve.
> Am I missing something? What is the the proper way to solve this?
>
> Thanks,
> -Mark
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
