You'll have to declare those classes where you want to use your service as services too, i.e. you either have to write a buildXXX method in your AppModule or do a binder.bind(). You can then either use the @InjectService annotation to inject your service or just write a constructor with the desired service as a paramater and Tapestry will do the rest for you.
Uli Am Do, 3.07.2008, 09:40, schrieb Udo Abel: > Hi, > > in my app, I have a service which works OK in pages and component classes, > but of course a lot of business logic is outside of those classes in > separate packages, where I need that service, too. > > But if I simple @Inject it as in page classes, it does not work (i.e. is > null). > > Is the injection limited to pages (maybe because they get transformed on > startup)? Or do I need to do something else for injection outside of > pages? > > Thanks, > Udo. > -- > Psssst! Schon vom neuen GMX MultiMessenger gehört? > Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger > > --------------------------------------------------------------------- > 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]
