Or instead of putting the code in the constructor you can create an
eagerly loaded build-method which instantiates the service, calls the
method and then returns the service instance.
Something like this:
@EagerLoad
public static PricelistHandler buildPricelistHandler(@Inject
PricelistService pricelistService) {
PricelistHandler pricelistHandler = new PricelistHandler();
initializePricelistHandler(pricelistService);
return pricelistHandler;
}
/Joakim
On Sat, 2009-08-22 at 00:25 +0200, Juan E. Maya wrote:
> U could also start the service by marking as eager or if that's not
> what u want u could use constructor injection and run the method
> inside of the constructor.
>
>
> On Sat, Aug 22, 2009 at 12:12 AM, Joshua Martin<josmar52...@gmail.com> wrote:
> > Is there a way to automatically run a method in a Service Impl right
> > after the service has been bound?
> >
> > As in, my service implementation is providing a service that I'd like
> > to be automatically available when the application starts. I don't
> > want the user to have to go click a button just to get the method to
> > run, and therefore the service to start.
> >
> > --
> > _________________________________
> >
> > Joshua S. Martin
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > For additional commands, e-mail: users-h...@tapestry.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
