Hi,
I haven't profiled StaticResourceReference but I get uncomfortable over
its use. Why is it that we must construct a new object in order to bind
a static resource to a URL? What happens if that resource is already
bound and no work needs to be done? We just created an object for nothing...
Isn't there a way we can somehow refactor this in terms of invoking a
method on some preexisting object instead of having to construct a new
object per resource? Or maybe, better yet, we should have something
equivilent to StaticResourceReference.valueOf() which is a static method
which either returns a reference to the preexisting
StaticResourceReference or returns a new object if one did not already
exist. This would be similar to Integer.valueOf() versus new Integer().
Gili
--
http://www.desktopbeautifier.com/
-------------------------------------------------------
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
