I don't think so. The problem I am trying to solve in this case is that I have a Dispatcher that performs authentication and authorization in the Tapestry request pipeline (I'm very new to T5 so I hope I'm using sane terms there). In the dev environment I need the implementation to not have external dependencies.
Thanks, -- Glenn On Fri, 2008-03-21 at 16:29 -0700, Ben Tomasini wrote: > Glenn, > > What requires you to have separate implementations for each > environment? Is it configuration data that you could move into a > properties file that lives the in the classpath of your container? > > Ben > > On Fri, Mar 21, 2008 at 4:02 PM, Glenn Sudduth <[EMAIL PROTECTED]> wrote: > > (This seems like a pretty basic question, but I haven't been able to > > ferret out the answer so here goes ...) > > > > What is a good way to have Tapestry 5 IoC determine which implementation > > of a particular service to load at runtime? With Spring I accomplish > > this by creating multiple versions of the bean definition/config file. > > Then have the (Maven) build process select the appropriate config based > > on the build profile I specify (dev, test, prod) and copy it in place so > > that Spring reads it when it starts up. > > Thanks, > > -- > > Glenn > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
