How about better architecture? Using a database instead of a file would be much nicer. With proper caching there's little to no difference in terms of performance than using a file.
Cheers, Adam On 25 November 2010 09:07, andrea.castello [via Apache Wicket] < [email protected]<ml-node%[email protected]> > wrote: > Hi, here's a new episode of my Wicket "upgrade saga". > Hope I'm not disturbing anyone :D > > In my application developed with Wicket 1.3.6 I have a > CarMessages.properties file which was sort of "shared" by two classes > CarListPage and CarDetail, since they use the same messages. > When I upgraded to 1.4 all the labels in CarMessages.properties are not > resolved anymore. > > I solved the problem by creating two new properties file > CarListPage.properties and CarDetail.properties and it all works fine, but > this is kind of awful because I need to duplicate the messages in these two > files. > > Is there any other way I can workaround this problem? > > Thanks, > > Andrea > > ------------------------------ > View message @ > http://apache-wicket.1842946.n4.nabble.com/Shared-message-property-file-not-working-on-1-4-tp3058612p3058612.html > To start a new topic under Apache Wicket, email > [email protected]<ml-node%[email protected]> > To unsubscribe from Apache Wicket, click > here<http://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1842946&code=YWRhbS5zLmdpYmJvbnNAZ21haWwuY29tfDE4NDI5NDZ8LTUzNzMyMDU4OQ==>. > > -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Shared-message-property-file-not-working-on-1-4-tp3058612p3058616.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
