On Mon, Jun 2, 2008 at 3:10 AM, Musachy Barroso <[EMAIL PROTECTED]> wrote:
> Sounds good. I think the OSGi plugin could make it to 2.2, and it
> would be nice to make a list of things that are missing/wanted to work
> on them (one of them is making Convention work with OSGi), I would
> work on this
Sounds good. I think the OSGi plugin could make it to 2.2, and it
would be nice to make a list of things that are missing/wanted to work
on them (one of them is making Convention work with OSGi), I would
work on this.
What is "Built-in command line tool like Grails" going to do?
Anyway, further b
+1
I will create a copy of REST and Codebehind into the sandbox with my
local changes and keep playing with them.
musachy
On Sun, Jun 1, 2008 at 2:25 AM, Don Brown <[EMAIL PROTECTED]> wrote:
> With 2.1.2 beta out the door, I think it is time we consider the
> branch feature-complete, which means
+1
On Sun, Jun 1, 2008 at 2:25 AM, Don Brown <[EMAIL PROTECTED]> wrote:
> With 2.1.2 beta out the door, I think it is time we consider the
> branch feature-complete, which means our focus should now be on
> working out the bugs so we can get a stable, GA-quality 2.1.x release
> ASAP.
>
> I'm goi
In terms of new features, I would like to see the Scope plugin integrated
into the core similar to the plan for Convention. This seems like an
essential service for a modern mvc framework. However, the plugin as it
stands is not feature complete. I believe the following features would make
it g
Are we dumping pre-1.5 support for 2.1 given that Sun say that 1.4.2
will be EOLed to the general public by the end of October this year?
It would be a little wasteful of manpower to support something in the
core that the vender says will be dead a few months after we go GA.
Don Brown wrote:
I don't like the jump in version numbers of advertisement sake. I'd
rather just keep on going with 2.3, etc.
In terms of JSR 303, Commons Validator 2 is being worked on for that.
On 6/1/08, Don Brown <[EMAIL PROTECTED]> wrote:
> Struts 2 desperately needs a public roadmap, IMO, so here's a quick
Struts 2 desperately needs a public roadmap, IMO, so here's a quick
strawman to get the discussion started:
Struts 2.1
* New plugins: REST, Dojo, DWR, Portlet, JUnit, and TestNG
* Internal API cleanups
Struts 2.2
* Finalize zero configuration strategy with new Conventions plugin
anyway,
i am not follow the REST feature
but i can see the ZeroConfig/CodeBehind/SmartURL/JSON vs current REST
is a smiliar but different world
anyone can share what should we do for this case?
i think this is good for us that investing our time, to know, which
one is depreciated and which one
