Cameron Braid wrote:

This would mean searching every sub-directory of every classpath entry (i.e.
jars and folders) This will have a performance impact on the startup time of 
wicket - how
large - I dunno - someone cart to implement and profile ?
We've had a bug in a program: I believe a class reference in a jar file. Java was trying to find it on every request, causing a dramatic decrease in performance. It is no picknick.

Johan will testify to this, as he discovered it (he wasn't the one causing it, mind you). :-)

Martijn



-------------------------------------------------------
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-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to