PROTECTED] wrote:
I'm going to start working on the SmartURLs port. Here's what I'm planning:
1. Deprecate all the current codebehind annotations and classes
I'm still not convinced this is a good idea, but as I said, I'll
reserve judgment till the merge branch is ready.
2. Create a new package
than to
trunk? I'm using/improving Codebehind right now in some of the new
features both in core and the rest plugin. I'd also like a chance to
fully review the changes before we dump the old.
On 12/6/07, Brian Pontarelli [EMAIL PROTECTED] wrote:
I'm going to start working on the SmartURLs
Pontarelli [EMAIL PROTECTED] wrote:
I'm going to start working on the SmartURLs port. Here's what I'm planning:
1. Deprecate all the current codebehind annotations and classes
I'm still not convinced this is a good idea, but as I said, I'll
reserve judgment till the merge branch is ready
As long as it's a deprecation and not deletion, I think it will be
fine. i.e. in 2.1.x you can configure the app to use the old mechanism.
The only other (really small picky thing) is the name codebehind.
What I see Brian doing to providing mapping and configuration. When I
think of
I'm going to start working on the SmartURLs port. Here's what I'm planning:
1. Deprecate all the current codebehind annotations and classes
2. Create a new package named org.apache.struts2.plugin.codebehind
3. Move the SmartURLs classes over (simple re-package)
4. Move annotations
