The problem about scanning the classpath could be reduced if the developer
declares in package-info.java the information for that package, like if it
has Web Pages (annotated web pages) or any other relative information.
This way, the framework would just scan for metadata at package level and if
it finds something, then scans all the classes inside of it.
Any thoughts?
On Jan 15, 2008 6:57 AM, Mark Derricutt <[EMAIL PROTECTED]> wrote:
> I like the idea, and for smaller projects it could be good.
>
> As an aside, you can already do the following:
>
> mount("/main", PackageName.forClass(AlohaPage.class));
>
> Whats the harm in extending this:
>
> mount("/main", PackageScanner.forClass(AlohaPage.class, WicketPage.class
> ));
>
> which scans the package (and subpackages maybe) for classes with the
> supplied annotation if we wanted flexibility. Because we're scanning just
> a
> known package, we can speed up the process and not scan -everything-.
>
> How about something like that?
>
>
>
> On 1/11/08, Nino Saturnino Martinez Vazquez Wael <[EMAIL PROTECTED]>
> wrote:
> > +10 for exploring, you just never know what handy feature turns up:) I
> > meant to say that to in my previous mail.
> >
>
--
Bruno Borges
blog.brunoborges.com.br
+55 1185657739
"The glory of great men should always be
measured by the means they have used to
acquire it."
- Francois de La Rochefoucauld
