One solution is to use the jsf-spring integration. http://jsf-spring.sourceforge.net/
This allows you to create JSF managed beans that implement InitializingBean (and DisposableBean), and you can put your initialization into afterPropertiesSet(). This is how I do it. I think Shale may also have something that can do this, but I haven't used it yet. Unfortunately, such bean initialization/disposal methods didn't make it into the JSF spec -- maybe in JSF 2.0. :) On 9/23/05, Walter Snel <[EMAIL PROTECTED]> wrote: > Hi, > > I'm struggling with an initialization problem. I guess it's not > particularly JSF related. It's more dependency injection related. However, > I hope someone could still assist me. > > I'm developping a small application that leverages the JSP managed beans / > managed properties facilities in a recursive way. Too be precise: I have a > bean called 'editor' which has managed property which is a map called > 'subcomponents'. This map again refers to diverse managed beans. > > As soon as the editor is needed all subcomponents are automatically > created by the ManagedBeanBuilder and placed in the map. It all works > fine, I can even nest further if I want to, no problems. > > However, now it turns out that my 'editor' needs an initialization step > prior to its usage. This initialization should only be performed once, but > no sooner than the whole tree is built. > > How can I pull this trick off ? Is there anything in the framework that > allows me to ask if a particular tree was completely built ? > > Help is much appreciated ! > Walter Snel >
