I admit I didn't research in-depth what you've suggested, but from the
quoted piece it seems that your suggestion will find all subclasses of
ResourceReference. But to actually test that all resources are properly
mapped, it would be necessary to locate all invocations of the
ResourceReference constructors and scan their parameters. I have hard time
imagining how it could possibly work without resorting to AspectJ (or AOP in

Also the same problem may be relevant for e.g. Image() and possibly other

Basically, unless I completely misunderstand what you're suggesting, I don't
really see how such scanning might work.

Martijn Dashorst wrote:
> Take a look at the spring component scanner for an implementation of
> how to search the class path. Then it is just a series of
> ResourceReference.class.isAssignableFrom(clz) queries and applying
> your specific logic.

View this message in context: 
Sent from the Wicket - User mailing list archive at Nabble.com.

To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to