We still consider the zero-config and codebehind code in Struts 2.0 to be experimental. Going forward, we do not want to leave that code in the core, because we want to stabilize the core.
We were always very clear that the zero-config and codebehind features were experimental and subject to change. I don't believe we need to "deprecate" any of this, since they were never labeled a supported feature. For Struts 2.1, Don's proposal is that we move all of the zero-config code into the codebehind plugin, and merge into that code from SmartURLs plugin, so that there is no "experimental" code in the core. The codebehind plugin for 2.1 would adopt the SmartURLs conventions and annotations. 1 - For 2.1, move zero-config code into codebehind plugin 2 - Merge SmartURLs conventions and annotations into the 2.1 codebehind plugin 3 - Leave the 2.0 SmartURLs plugin at GoogleCode >From 2.1 onward, we would consider the new codebehind conventions to be stable, and, if we want to change the conventions thereafter, then we would take more drastic steps, which could even include bringing out a different plugin under a different name. But, I don't think we need to do that yet. Personally, I would suggest that this is an ideal time to thoroughly exercise and document the new conventions and encourage everyone upgrading from 2.0 to 2.1 to adopt those conventions, and leave the "experimental" conventions behind. Though, I would also like to continue work on the SmartURLs plugin for 2.0, so that we can use that as the basis for testing and documenting the conventions now, until the 2.1 refactoring is complete. -Ted. On 10/10/07, Brian Pontarelli <[EMAIL PROTECTED]> wrote: > > Initially I figured we could pull things from zero-conf, code-behind and > SmartURLs out into the plugin and then work from there. But now I'm > thinking that deprecating all the old code-behind, zero-conf and > SmartURLs stuff were it is at and not supporting it any longer might be > best. Most of this stuff is working as is and allowing folks to use > those features from the current locations shouldn't impact new > development going forward. Therefore, leaving it where it is at should > be fine and then starting a new plugin called convention or something > based on the Struts and SmartURLs code bases in a brand new package. > > OR we could do this: > > 1. Pull out the existing SmartURLs, zero-conf and codebehind into a new > plugin called convention or something. > 2. Deprecate all of it but ensure it works seamlessly. > 3. Create new annotations, classes, etc in a new package > (org.apache.struts2.plugin.convention) based off the existing code. > 4. Update things as needed to get it all working with no mods or > application breakage. > 5. Plan removal dates for the old code. I'd say 2.2 would be fine. > > Thoughts? > > -bp --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
