If we are going to do major surgery on the annotations, then we should move them to a Struts Annotations plugin. In this way, we can bring out a new and improved annotations plugin for 2.1, and people can choose which set of annotations to use. We do already have some annotations in the public API, and giving people a choice between plugins is an excellent way to provide a migration path.
Also, in that way, work on the new annotations won't hold up the rest of the 2.1. release. I would still like to roll 2.1.0 by the end of the month. I'm away next week, but perhaps we could plan on Sept 30 (unless someone else is available). -Ted. On 9/21/07, Ian Roughley <[EMAIL PROTECTED]> wrote: > Don Brown wrote: > > In this case, the annotations will be likely redone for 2.1 anyways. > > A lot of it is my fault - they have been kinda thrown in there without > > systematic thought, and I had hoped we could fix that for 2.1. I'd > > hate to introduce new annotations only to deprecate them weeks later. > > > My preference would be to wait as well. If for nothing else, to see how > JSR-311 (RESTful web services) flushes out and whether we should adopt > some of the structure of the annotations in Struts2. Has anyone looked > into this JSR? I saw a presentation at Sun Tech Days the other day. I > just need to find some time to see if it could be adopted to the > annotations in s2 now :-) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
