yes but this doesn't really work.
Because if you guys are going to use wicket-extentions.jar
Don't you have the same problem then?
There is not only one wicket.properties. There can be multiple (in every
wicket component jar file there is)
johan
Scott Sauyet wrote:
Davide Savazzi wrote:
Hi, I've subscribed to this ml yesterday so I've read this thread in
the archive (maybe I've missed something)... but I've solved this
problem removing wicket.properties from the wicket jar and putting it
in tomcat/shared/classes
It seems to work :)
Thanks. I woke up this morning with that exact thought. Slightly
more work to upgrade Wicket versions, but it will certainly save some
headaches.
-- Scott
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle
Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing
& QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
