Me again, > That is an interface (Messages is not) Huuh!! Bad, faux pas! I have to correct myself in fact Messages IS an interface. But no matter it does not work. Bye
----- original Nachricht -------- Betreff: Re: Re: Re: [T5] Sending Email from Tapestry Gesendet: Sa, 19. Apr 2008 Von: nille hammer<[EMAIL PROTECTED]> > Hi Thiago, > > I am aware of the difference between App.properties and page specific > properties. As my App.properties tends to grow significantly, I try to keep > everything local unless it is needed by at least two components/pages. > > BTW, using Messages as a parameter to a build method in AppModule. does not > work. The ioc-container throws a RuntimeException: No service implements the > interface org.apache.tapestry.ioc.Messages. So I tried ComponentResources. > That is an interface (Messages is not) and provides a method getMessages(). > That led to the same result. I also added Annotation @Inject, no success. > Until now I haven´t managed to get a hand on my ConfirmationMailSender via > the ioc-Container. What I´m doing now ist calling new > ConfirmationMailSender(this.messages) from within the page that uses it. > That might not be ideal, but it works pretty well. > > So any one who knows how to provide a message catalogue to a service builder > method, please do not hesitate to enlight me. > > Thanks and good night, > nillehammer > > ----- original Nachricht -------- > > Betreff: Re: Re: [T5] Sending Email from Tapestry > Gesendet: Fr, 18. Apr 2008 > Von: Thiago HP<[EMAIL PROTECTED]> > > > On 4/18/08, nille hammer <[EMAIL PROTECTED]> wrote: > > > > > Hi Thiago, > > > > Hi, Nille! > > > > > thanks for the advice that makes perfect sense! What is left is my > first > > question, where does Tapestry how to choose the right message catalogue? > If > > I injected the ConfirmationMailSender in my BookingSummary Page would > > Tapestry use it´s message catalogue? So would I have to put the localized > > messages into BookingSummary.properties? > > > > I suggest you to put your localized messages in app.properties, being > > app the name of the Tapestry servlet filter in you web.xml (answer for > > your first question). But you could also put them in > > BookingSummary.properties, but then they would only be used in that > > page, not in the rest of your application (answer for your second e > > third questions). Tapestry, the web framework, always looks first in > > the page-specific properties file first and then in the global one > > after. > > > > All I'm saying here is valid for Tapestry web applications. I'm not > > sure (and I can't find out now, unfortunately) what would be the name > > of the properties file in a non-web application using Tapestry-IoC. > > > > -- > > Thiago > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --- original Nachricht Ende ---- > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --- original Nachricht Ende ---- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
