> Pro's: > - a long list of mounts becomes unmanagable > - easy to add a mount: work on a page, slap on the annotation and you > have your mount done > - locality of the configuration > > Con's > - distributed configuration, so hard to see the 'big picture' (though > a mounts page listing all mounts would help) > - scanning of classpath at startup (though spring, struts, etc are > doing that already) > - multiple mounts at same position harder to detect, though that is > already possible.
I agree with the pros and cons. The classpath scanning for classes may be tricky. It should be one of the first things to explore then. If we can pull this off reliably, we should solve this generically, so that annotation processors can be layered and possibly plugged in by users. > Open questions: > - annotated page impossible? What do you mean? > - specifying the URL encoding strategy That might actually be sweet. > - multiple mounts for the same page > - package mounting? > - can we override the annotated mount? No way. Such annotations should be 1-1 to a page, and only concrete pages. > - how do we work with pages contributed using jars, could we disable > the annotated mounts and provide our own? Generic libraries should probably never have this. For people who break up their apps in multiple projects (jars), we should just allow these annotations. Eelco
