Stephen McConnell wrote: > > 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.
You're refering to your CascadingConfiguration work? I knew I should have paid more attention when you were discussing that problem... ;) The javadoc for CascadingConfiguration in the scratchpad sounds like it'll do what I need. How exactly do you define a parent configuration? As I understand it, if I've two roles, RoleA and RoleB, with shorthand names A and B respectively, I'd assign both the same parent configuration. I can then override the values of the parent configuration by defining configuration blocks <A/> and <B/> as necessary. Otherwise, they'd just use the values from the parent configuration. BTW, are you planning on building on what you have here (which is an incremental change from what already exists), or are you envisioning something much grander (a change from the ground up)? Thanks, -Mark -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
