wicket caches a lot of this stuff, so i wouldnt worry about performance
-igor
On Wed, Aug 6, 2008 at 1:09 PM, lesterburlap [EMAIL PROTECTED] wrote:
Hi:
I understand how Wicket searches for property keys:
MyPage.properties -
MyComponentA.properties -
MyComponentB.properties -
MyApplication.properties, etc, etc...
Is there any run time efficiency benefit in putting a property from
MyComponentB in the MyPage.properties file (rather than in its own local
file)? Or is it completely negligible?
I like it better in its own local properties file for my own ease of
development + modularity, but was wondering if there's any performance
difference to worry about.
Thanks for any input!
LBB
--
View this message in context:
http://www.nabble.com/properties-files-search-efficiency-tp18858597p18858597.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
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]
