Thanks Paul, I'll try this later.
On 3/15/06, Paul Ferraro <[EMAIL PROTECTED]> wrote: > > > Alternatively, if your initialization logic requires that Tapestry > already be initialized, you can plug into Tapestry's initialization by > contributing to the tapestry.init.ApplicationInitializers configuration > point. > e.g. > <service-point id="MyInitializer" > interface="org.apache.tapestry.services.ApplicationInitializer"> > <invoke-factory> > <construct class="class-name-of-your-initializer"></construct> > </invoke-factory> > </service-point> > > <contribution configuration-id="tapestry.init.ApplicationInitializers"> > <command id="MyInitializer" object="service:MyInitializer" after="*"/> > </contribution> > > Make sure that you've configured your Tapestry servlet to > load-on-startup in your web.xml. > > Paul
