Having the ability to specify the mount with the page instead of a central location may be interesting. How is this different from specifying to what table an entity is retrieved from? I think having all the things that relate to a specific page in one place is an advantage.
I'm not sure what deserved this outburst, but I think *EXPLORING* the possibility and the consequences of having a mount-annotation are worth it. Just saying you don't like it without arguments or throwing some unrelated arguments around just doesn't cut it. If you don't like it, you don't have to use it. So instead of the "I don't like ..." arguments, please answer the question: What issues would we run into if we were going to implement it? There are probably tons of issues associated with it, for instance (which didn't take me long to come up with): 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. Open questions: - annotated page impossible? - specifying the URL encoding strategy - multiple mounts for the same page - package mounting? - can we override the annotated mount? - how do we work with pages contributed using jars, could we disable the annotated mounts and provide our own? Martijn On Jan 10, 2008 2:28 PM, Eduardo Ito <[EMAIL PROTECTED]> wrote: > I agree... > > What is the *advantage* of putting the mount definition in an annotation? > Following the same pattern, we would create a bunch of annotations > like @PageSettings, @HomePage, etc... argh! > > > > On 1/10/08, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > I suggest we take a look at annotations for: > > > * the mount with a page > > > > A disadvantage to doing that imho is that you'll have those > > definitions scattered throughout. Right now we steer people to do it > > in one place. > > > > Eelco > > > > > -- > Eduardo Issao Ito > Summa Technologies > > "Discipline is never an end in itself, only a means to an end" > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.0 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0
