Hi Thiago,
That's actually a clever solution, but seems a bit hacky and I'm not
sure how it will also use the usual Index(_en).properties files?
I solved it at the moment with adding a new binding prefix where i pass
the key and property value like following:
On Wed, 12 Aug 2015 11:37:29 -0300, Nathan Quirynen
nat...@pensionarchitects.be wrote:
Hi Thiago,
Hi!
That's actually a clever solution, but seems a bit hacky and I'm not
sure how it will also use the usual Index(_en).properties files?
If you create a Locale(en, 120) and a message
We are running Tapestry 5.2.6 in production and I'd like to be able to add
content to the head html area from components other than the main page layout
container. For example, a particular page component might need to populate a
meta element, or even change the page title or add an additional
On 12/08/15 17:36, Thiago H de Paula Figueiredo wrote:
On Wed, 12 Aug 2015 11:37:29 -0300, Nathan Quirynen
nat...@pensionarchitects.be wrote:
Hi Thiago,
Hi!
That's actually a clever solution, but seems a bit hacky and I'm
not sure how it will also use the usual Index(_en).properties
So aside from the hibernate library, my problem is that when using
Marker annotations for tagging a service I have to add these
annotations everywhere. It would be nice to be able to define a
default when adding no marker annotation. Now you get the error about
the fact that**dependency
