I opened WW-1700 to cover this.
* https://issues.apache.org/struts/browse/WW-1700
-Ted.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
As it turns out, the new API is being used by the StrutsObjectFactory.
I'll put off rolling 2.0.5 until Sunday, in case anyone has a chance
to look at refactoring the new API out of StrutsObjectFactory.
Worse case, Nial has fixed the license headers, so we can roll it
again either way.
If anyon
OK, I'll try to roll 2.0.5 tonight, so that we can vote over the
weekend, and try to get at least another beta out.
-Ted.
On 2/1/07, Bob Lee <[EMAIL PROTECTED]> wrote:
I'm cool with that. I'm not going to finish it by this weekend--I'm working
feverishly toward a Guice release, and I plan on us
I'm cool with that. I'm not going to finish it by this weekend--I'm working
feverishly toward a Guice release, and I plan on using Guice in the API
anyway (we won't need *Aware interfaces).
Bob
On 2/1/07, Ted Husted <[EMAIL PROTECTED]> wrote:
I tend to agree. Unless someone says they are ready
Ted Husted wrote:
I tend to agree. Unless someone says they are ready, willing, and
ablle to resolve the "new API" this weekend, lets just pull it out and
roll 2.0.5 now.
+1
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For a
I tend to agree. Unless someone says they are ready, willing, and
ablle to resolve the "new API" this weekend, lets just pull it out and
roll 2.0.5 now.
We can then slate the "new API" for 2.1.x, along with the AJAX/Dojo plugin.
(Which, I believe, would be *plenty* for a 2.1.x, without getting i
Yeah, I think we really need a commitment from Bob or someone else
willing to really finish this effort. If no one signs up, I'm all for
pull it out into the sandbox. Right now, there are too many duplicate
classes and code that is very confusing as a developer. Personally, I
think this shou
