One thing which bothered me a couple of times already on this list. With the neat tapestry-spring integration, why don't you just use Spring to configure Spring services? The little xml used for configuring acegi is in my personal view more readable than the contributions in a service class and it got even less with 2.0. And you don't need any changes to Tapestry itself.
Regards, Otho 2008/5/7 Robin Helgelin <[EMAIL PROTECTED]>: > On Tue, May 6, 2008 at 11:04 PM, Howard Lewis Ship <[EMAIL PROTECTED]> > wrote: > > I've been thinking for a while about adding remove() and replace() > > methods to OrderedConfiguration and MappedConfiguration, and adding > > other methods to OrderedConfiguration to allow minor tweaks to > > dependencies. It just hasn't been a priority. It also leads to > > ambiguities ... what if you remove and replace? Or replace multiple > > times? > > Any ideas on how to solve this with the current available releases? > > As for your question, maybe services can declare the configuration > entry non-removable/non-replaceable, such as internal Tapestry > services? > > -- > regards, > Robin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
