I'm the same, I have only every used just @MountPath on its own, but if those other strategies existed I assumed that someone must have used them.
I like the 1.5 port as it is, and now that its done hopefully others using it will try and upgrade to 1.5 and if they can somehow put forward use cases for the strategies then I guess it can be put back in. But from what I've read on the new mapper in 1.5 it seems to obsolete the need for all the other strategies. On Wed, Jul 20, 2011 at 11:34 PM, Ron Smits <[email protected]> wrote: > If all the different strategies stay in, would it not be good to have some > more real world like examples. In the different applications we have done > until now we have only used the normal @mountpath. > > Ron > On Jul 20, 2011 3:17 PM, "Steve Mactaggart" <[email protected]> > wrote: > > Looks pretty much like the changes I made, I just wasn't confident enough > > that my mount code was going to work well enough in the cases related to > > removal of the different coding strategies. > > > > I'll have to grab the latest source and see how it compares. > > > > On Wed, Jul 20, 2011 at 4:15 PM, Martin Grigorov <[email protected] > >wrote: > > > >> The source is at > >> > https://github.com/wicketstuff/core/tree/master/jdk-1.5-parent/annotation > . > >> It is already migrated to 1.5 and it will be available at Maven repos > >> with the next release. > >> > >> On Wed, Jul 20, 2011 at 7:03 AM, Steve Mactaggart > >> <[email protected]> wrote: > >> > Excellent. > >> > > >> > From the work I did at the time I was investigating the move to 1.5 it > >> seems > >> > that most of the different Strategies have been removed in 1.5 and can > be > >> > nearly completely controlled using only the @MountPath annotation. > >> > > >> > We never needed to use things like the HybridMountStrategy, so It was > >> hard > >> > for me to know what they were supposed to do and so I have a local > copy > >> of > >> > the annotations updated enough for us to test that they can be used to > >> mount > >> > our pages in 1.5. > >> > > >> > Just FYI we decided to NOT upgrade to 1.5 until its final, (business > >> > reasons) but apart from some corner cases that I think we would be > able > >> to > >> > get around, with some effort, the move to 1.5 is a doable process. The > >> > biggest changes we had was getting the annotations sub-project updated > to > >> > work with 1.5 and getting a wiquery build for the right 1.5-RC.. > >> > > >> > If you want to see the hack's I've done, or even want to discuss my > >> research > >> > please let me know and I'll pass on what I can. > >> > > >> > Steve > >> > > >> > On Wed, Jul 20, 2011 at 1:41 PM, Donohoe Digital <[email protected]> > >> wrote: > >> > > >> >> Hi Steve, > >> >> > >> >> I'm the original developer of wicketstuff-annotation and am getting > back > >> >> into Wicket development after a long hiatus. I'll probably be looking > >> into > >> >> this over the next month or so. > >> >> > >> >> I tried to bring up the old wiki page for this and it doesn't seem to > be > >> >> working. It looks like wicketstuff is now using git, so I'll have to > >> >> figure > >> >> out where the source lives. > >> >> > >> >> -Doug Donohoe > >> >> > >> >> -- > >> >> View this message in context: > >> >> > >> > > http://apache-wicket.1842946.n4.nabble.com/State-of-wicketstuff-Annotations-tp3587286p3679935.html > >> >> Sent from the Forum for Wicket Core developers mailing list archive > at > >> >> Nabble.com. > >> >> > >> > > >> > >> > >> > >> -- > >> Martin Grigorov > >> jWeekend > >> Training, Consulting, Development > >> http://jWeekend.com > >> >
