I'm curious to know how much extra time is added to the application
startup by doing the class path scanning. Particularly for larger
projects. I just find that when doing development the faster an
application starts the better.
John
Doug Donohoe wrote:
Thanks. I'm not sure if class path scanning is needed. To be honest,
I haven't looked at the internals of 'mount' yet...
-Doug
jwcarman wrote:
On Sat, May 3, 2008 at 9:20 AM, Doug Donohoe <[EMAIL PROTECTED]> wrote:
3) Use Annotations to handle mounting. Instead of putting all mount
logic
in the Application class, you could annotate your pages with something
like
@Mount( strategy=foo.class, params=x,y,z ). Then upon initialization,
Wicket could scan the class path and auto-mount these annotated pages.
Scanning the classpath is pretty easy using some spring-core
functionality.
I don't know if the Spring license is compatible with Apache, so this
might
need to be a contrib feature.
Spring uses the Apache License, v2
