Use it then. Inject the factory via @SpringBean. On Fri, Apr 24, 2009 at 9:56 AM, cretzel <mailinglists...@gmail.com> wrote: > > We are using Spring. > > > Liam Clarke-Hutchinson-3 wrote: >> >> Are you using an IoC container at all? >> >> On 4/24/09, Nick Wiedenbrück <mailinglists...@googlemail.com> wrote: >>> Hi, >>> >>> I'm having many Components (DropDowns, ChoiceRenderers, ...) that are >>> reused >>> in different places in my application. For example I have one >>> ChoiceRenderer for persons, one for accounts and so on. I want to >>> centralize the creation of these components in a factory in order to >>> decople >>> the clients. For example I'm thinking about a ChoiceRendererFactory with >>> methods createPersonChoiceRenderer() and createAccountChoiceRenderer(). >>> >>> Now, my question is where to put this factory. I need a central place, >>> where >>> the can find the factory. Is it a good idea to have a method >>> createChoiceRendererFactory() on my Application class? >>> >>> Regards, >>> Nick >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> >> > > -- > View this message in context: > http://www.nabble.com/Factory-for-Components-tp23212875p23216937.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
-- Marcelo Morales --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
