Re: Howto get locales's messages from a database
Andreas Andreou a écrit : Yep, that's the way... There's also the wiki! http://wiki.apache.org/tapestry/UsingCustomResourceSource YEAH ! That's it ! Thank you Andreas. Cyrille. Cyrille37 wrote: Cyrille37 a écrit : I would like to store locales messages in a database. In my application project, some users can translate messages by them self to create new locales or change some messages. It will be better if they can do that online via a web interface. I think it would not be great and dangerous if they directly edit messages files, so I need to store messages in a database. With a ORM like Hibernate and a cache system, performances should be good enough. Do you know where I've to start ? I've found in the hivemodule.xml of tapestry-4.0.2.jar a contribution : ... Used to provide components (including pages) with access to their own localized messages. Should I look that way to implement my need ?? Cyrille Thanks Cyrille - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Howto get locales's messages from a database
Yep, that's the way... There's also the wiki! http://wiki.apache.org/tapestry/UsingCustomResourceSource Cyrille37 wrote: > Cyrille37 a écrit : >> I would like to store locales messages in a database. >> In my application project, some users can translate messages by them >> self to create new locales or change some messages. >> It will be better if they can do that online via a web interface. >> I think it would not be great and dangerous if they directly edit >> messages files, so I need to store messages in a database. With a ORM >> like Hibernate and a cache system, performances should be good enough. >> >> Do you know where I've to start ? > > I've found in the hivemodule.xml of tapestry-4.0.2.jar a contribution : > > > object="service:ComponentMessagesSource"/> >... > > >Used to provide components (including pages) with access to their > own localized messages. > > > > value="infrastructure:componentPropertySource"/> > > > > > Should I look that way to implement my need ?? > > Cyrille > >> Thanks >> Cyrille >> > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr Tapestry / Tacos developer Open Source / J2EE Consulting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Howto get locales's messages from a database
Cyrille37 a écrit : I would like to store locales messages in a database. In my application project, some users can translate messages by them self to create new locales or change some messages. It will be better if they can do that online via a web interface. I think it would not be great and dangerous if they directly edit messages files, so I need to store messages in a database. With a ORM like Hibernate and a cache system, performances should be good enough. Do you know where I've to start ? I've found in the hivemodule.xml of tapestry-4.0.2.jar a contribution : object="service:ComponentMessagesSource"/> ... Used to provide components (including pages) with access to their own localized messages. value="infrastructure:componentPropertySource"/> Should I look that way to implement my need ?? Cyrille Thanks Cyrille - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Howto get locales's messages from a database
Hello, I would like to store locales messages in a database. In my application project, some users can translate messages by them self to create new locales or change some messages. It will be better if they can do that online via a web interface. I think it would not be great and dangerous if they directly edit messages files, so I need to store messages in a database. With a ORM like Hibernate and a cache system, performances should be good enough. Do you know where I've to start ? Thanks Cyrille - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]