You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Jeromy Evans <je...@blueskyminds.com.au> on 2008/03/20 08:08:25 UTC
If I had 1000 hours to give...
It's been quiet lately so I thought I'd throw something out there.
If you could give 1000 hours to the Struts 2 project, what would you do?
I would like to it become the SOA framework of choice through :
- SEO-friendly URLs become the default and users never have to think
about it again;
- allow action methods to be bound to an http method and allow results
to be easily bound to the result code and requested content type (as per
REST plugin)
- support content in the request (eg text/xml or text/json
content-type), deserialize and set the model of the action (the reverse
of the REST plugin)
- allow actions to be pojos and delete ActionSupport (without losing
implicit i18n and validation functionality)
- allow hot deployment & run-time management of actions (OSGi??)
- refactor UIBean & XWork component so there's only one model and one
template per tag and they're easy to unit test (code-generate the
wrappers/template models/taglibs)
- action scope and component scope become first-class concepts
(integrate the plugins)
- add run-time developer tools; configuration browser becomes standard
in developer mode and add a resource bundle browser
- delete all ajax-like tags and funky tags; add standard interceptors &
models to ease integration with the client-side libraries, groovy,
grails, JSF, struts1 (and others?). tags move to plugin.
- I don't have an opinion about portal support but I'm sure it's important
I think I ran out of hours already!
cheers,
Jeromy Evans
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: If I had 1000 hours to give...
Posted by Philip Luppens <ph...@gmail.com>.
My quick list:
- rewrite XWork; simpler, more flexible: annotations, generics,
classpath scanning, pluggable expression language and validation.
- take a step back, and follow a bunch of new developers to see where
the documentation is lacking.
- I don't like the ajax theme at all - it's a real pain to get it to
work cross-browser, it feels clunky no matter what you do; I prefer
using a gwt front-end, and S2 on the backend. One battle at a time,
guys.
- performance is still a bit of a problem. With the tuning page
solutions, things are acceptable, but we're still (way) below S1 and
Stripes when doing complex pages with big forms). I should get working
on the performance testing issue, but lost most of my efforts when my
server crashed, and haven't found time ever since.
- tools, tools, tools .. there are some efforts underway (S2 plugin
for IntelliJ, which looks really promising, S2 plugin for NetBeans,
pretty quiet afaict, but nothing for Eclipse/MyEclipse). I realize
we're no IDE devs, but maybe we can assist those who are ?
- full OSGi/plugin support in XW, full reloading in dev mode for S2
apps similar to Grails.
There are a million things I'd like to do, but as it stands today, I
can hardly find a spare 100 minutes.
Phil
On Thu, Mar 20, 2008 at 6:31 PM, James Mitchell <jm...@gmail.com> wrote:
> Here's my list:
>
> - Create a struts2-jror-plugin that let's me develop/deploy my RoR app as a
> standard Java Web Application (via JRuby)
>
> This would allow me to deploy my apps under the corporate-approved stamp for
> Struts 2 ... yet still get (almost) all the wonderful benefits of true rapid
> and agile development under Ruby on Rails.
>
> My $0.02
>
> On Thu, Mar 20, 2008 at 1:06 PM, Brian Pontarelli <br...@pontarelli.com>
> wrote:
>
>
>
> > Here's my list:
> >
> > - Collapse XWork into Struts
> > - Rewrite XWork to be a servlet workflow engine and less abstract (i.e.
> > remove thread locals and contexts)
> > - Fix nasty circular XWork injections and setter injections
> > - Generics
> > - Update all public APIs no matter how infrequently used and then hard
> > API freeze until 4.0 (assuming all this work would be 3.0)
> > - Rewrite tags with better support for writing new/custom tags inside
> > apps and other frameworks
> > - Rewrite XWork container with Guice 2.0 (once released)
> > - Drop OGNL in favor of a UEL that supports type conversion (nothing
> > does this really well quite yet)
> > - Make actions easier to write (no getters/setters, support Groovy,
> > support reloading)
> > - Make form prepare better and reusable across actions and results
> > - Support real code-behind that reuses actions to display and submit a
> > form and distinguishes between GET and POST with no coding
> > - Rewrite all docs top down to cover all configuration, usages, etc.
> > including javadocs and online docs
> >
> > How much is 1000 hours anyways? I think this is like a years worth of
> > work or something. ;)
> >
> > -bp
> >
> >
> >
> > Jeromy Evans wrote:
> > > It's been quiet lately so I thought I'd throw something out there.
> > >
> > > If you could give 1000 hours to the Struts 2 project, what would you do?
> > >
> > > I would like to it become the SOA framework of choice through :
> > > - SEO-friendly URLs become the default and users never have to think
> > > about it again;
> > > - allow action methods to be bound to an http method and allow results
> > > to be easily bound to the result code and requested content type (as
> > > per REST plugin)
> > > - support content in the request (eg text/xml or text/json
> > > content-type), deserialize and set the model of the action (the
> > > reverse of the REST plugin)
> > > - allow actions to be pojos and delete ActionSupport (without losing
> > > implicit i18n and validation functionality)
> > > - allow hot deployment & run-time management of actions (OSGi??)
> > > - refactor UIBean & XWork component so there's only one model and one
> > > template per tag and they're easy to unit test (code-generate the
> > > wrappers/template models/taglibs)
> > > - action scope and component scope become first-class concepts
> > > (integrate the plugins)
> > > - add run-time developer tools; configuration browser becomes standard
> > > in developer mode and add a resource bundle browser
> > > - delete all ajax-like tags and funky tags; add standard interceptors
> > > & models to ease integration with the client-side libraries, groovy,
> > > grails, JSF, struts1 (and others?). tags move to plugin.
> > > - I don't have an opinion about portal support but I'm sure it's
> > > important
> > >
> > > I think I ran out of hours already!
> > >
> > > cheers,
> > > Jeromy Evans
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > > For additional commands, e-mail: dev-help@struts.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
>
> --
> James Mitchell
>
--
Software Architect - Hydrodesk
"We cannot change the cards we are dealt, just how we play the hand."
- Randy Pausch
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: If I had 1000 hours to give...
Posted by James Mitchell <jm...@gmail.com>.
Here's my list:
- Create a struts2-jror-plugin that let's me develop/deploy my RoR app as a
standard Java Web Application (via JRuby)
This would allow me to deploy my apps under the corporate-approved stamp for
Struts 2 ... yet still get (almost) all the wonderful benefits of true rapid
and agile development under Ruby on Rails.
My $0.02
On Thu, Mar 20, 2008 at 1:06 PM, Brian Pontarelli <br...@pontarelli.com>
wrote:
> Here's my list:
>
> - Collapse XWork into Struts
> - Rewrite XWork to be a servlet workflow engine and less abstract (i.e.
> remove thread locals and contexts)
> - Fix nasty circular XWork injections and setter injections
> - Generics
> - Update all public APIs no matter how infrequently used and then hard
> API freeze until 4.0 (assuming all this work would be 3.0)
> - Rewrite tags with better support for writing new/custom tags inside
> apps and other frameworks
> - Rewrite XWork container with Guice 2.0 (once released)
> - Drop OGNL in favor of a UEL that supports type conversion (nothing
> does this really well quite yet)
> - Make actions easier to write (no getters/setters, support Groovy,
> support reloading)
> - Make form prepare better and reusable across actions and results
> - Support real code-behind that reuses actions to display and submit a
> form and distinguishes between GET and POST with no coding
> - Rewrite all docs top down to cover all configuration, usages, etc.
> including javadocs and online docs
>
> How much is 1000 hours anyways? I think this is like a years worth of
> work or something. ;)
>
> -bp
>
>
>
> Jeromy Evans wrote:
> > It's been quiet lately so I thought I'd throw something out there.
> >
> > If you could give 1000 hours to the Struts 2 project, what would you do?
> >
> > I would like to it become the SOA framework of choice through :
> > - SEO-friendly URLs become the default and users never have to think
> > about it again;
> > - allow action methods to be bound to an http method and allow results
> > to be easily bound to the result code and requested content type (as
> > per REST plugin)
> > - support content in the request (eg text/xml or text/json
> > content-type), deserialize and set the model of the action (the
> > reverse of the REST plugin)
> > - allow actions to be pojos and delete ActionSupport (without losing
> > implicit i18n and validation functionality)
> > - allow hot deployment & run-time management of actions (OSGi??)
> > - refactor UIBean & XWork component so there's only one model and one
> > template per tag and they're easy to unit test (code-generate the
> > wrappers/template models/taglibs)
> > - action scope and component scope become first-class concepts
> > (integrate the plugins)
> > - add run-time developer tools; configuration browser becomes standard
> > in developer mode and add a resource bundle browser
> > - delete all ajax-like tags and funky tags; add standard interceptors
> > & models to ease integration with the client-side libraries, groovy,
> > grails, JSF, struts1 (and others?). tags move to plugin.
> > - I don't have an opinion about portal support but I'm sure it's
> > important
> >
> > I think I ran out of hours already!
> >
> > cheers,
> > Jeromy Evans
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
James Mitchell
Re: If I had 1000 hours to give...
Posted by Brian Pontarelli <br...@pontarelli.com>.
Here's my list:
- Collapse XWork into Struts
- Rewrite XWork to be a servlet workflow engine and less abstract (i.e.
remove thread locals and contexts)
- Fix nasty circular XWork injections and setter injections
- Generics
- Update all public APIs no matter how infrequently used and then hard
API freeze until 4.0 (assuming all this work would be 3.0)
- Rewrite tags with better support for writing new/custom tags inside
apps and other frameworks
- Rewrite XWork container with Guice 2.0 (once released)
- Drop OGNL in favor of a UEL that supports type conversion (nothing
does this really well quite yet)
- Make actions easier to write (no getters/setters, support Groovy,
support reloading)
- Make form prepare better and reusable across actions and results
- Support real code-behind that reuses actions to display and submit a
form and distinguishes between GET and POST with no coding
- Rewrite all docs top down to cover all configuration, usages, etc.
including javadocs and online docs
How much is 1000 hours anyways? I think this is like a years worth of
work or something. ;)
-bp
Jeromy Evans wrote:
> It's been quiet lately so I thought I'd throw something out there.
>
> If you could give 1000 hours to the Struts 2 project, what would you do?
>
> I would like to it become the SOA framework of choice through :
> - SEO-friendly URLs become the default and users never have to think
> about it again;
> - allow action methods to be bound to an http method and allow results
> to be easily bound to the result code and requested content type (as
> per REST plugin)
> - support content in the request (eg text/xml or text/json
> content-type), deserialize and set the model of the action (the
> reverse of the REST plugin)
> - allow actions to be pojos and delete ActionSupport (without losing
> implicit i18n and validation functionality)
> - allow hot deployment & run-time management of actions (OSGi??)
> - refactor UIBean & XWork component so there's only one model and one
> template per tag and they're easy to unit test (code-generate the
> wrappers/template models/taglibs)
> - action scope and component scope become first-class concepts
> (integrate the plugins)
> - add run-time developer tools; configuration browser becomes standard
> in developer mode and add a resource bundle browser
> - delete all ajax-like tags and funky tags; add standard interceptors
> & models to ease integration with the client-side libraries, groovy,
> grails, JSF, struts1 (and others?). tags move to plugin.
> - I don't have an opinion about portal support but I'm sure it's
> important
>
> I think I ran out of hours already!
>
> cheers,
> Jeromy Evans
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: If I had 1000 hours to give...
Posted by Jeromy Evans <je...@blueskyminds.com.au>.
jelmer wrote:
>
> Second, I always thought of the custom tags and ognl as a core part of the
> framework and also it's core strength. Seeing people on this list discus
> removing it makes me ... somewhat nervous. Why would be the reasons to do
> this. Everything from formatting, typeconversion to databinding uses ognl
> under the hood and provides a lot of flexibility
>
>
jelmer, I think you'll find mixed opinions of OGNL here and technical
debate appears to be encouraged.
Personally, I like OGNL as a language and only have minor issues with
the implementation that have been mentioned before and are being slowly
addressed by that project. The use of OGNL throughout Struts 2 seems to
be a common concern because, in retrospect, the expression language,
typeconversion, formmatting etc should be more easily pluggable. As
usual, at the time it was probably the right decision or there was no
alternative, and as usual, as new developers come along there's new
opinions on how it could be done better.
The purpose of this thread was to tease out some of those ideas and
observe the interests of some of the developers. The main point I take
away from the thread is that Struts 2 is a different thing to different
people and if anything that speaks highly for its core original
architecture. Focus, however, is also very important.
A page was started that listed the OGNL issues for Struts 2 and as you
can see they're not huge:
http://cwiki.apache.org/S2WIKI/ognl-replacement.html
regards,
Jeromy Evans
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: If I had 1000 hours to give...
Posted by Adam Hardy <ah...@cyberspaceroad.com>.
Do you mean my email makes you nervous? The dev@struts.apache.org is a public
list for the discussion of the development of struts, and this thread is titled
"If I had a 1000 hours to give..." with the implication the subject is future
directions. Why do you have a nervous reaction to my desire for the kind of
taglibrary I described?
Perhaps you should read through a few of the threads from this list on a mailing
list archive site to allay whatever anxieties you have. I can assure you that my
comments are not going to provoke the immediate launch of Struts 3 with a whole
new set of dependencies that might make your struts-based code base redundant,
assuming that this is what you are nervous about - perhaps you could clarify
your point?
jelmer on 23/03/08 18:10, wrote:
> First off I was under the impression that the jstl was already supported
> through means of the StrutsRequestWrapper, correct ?
>
> Second, I always thought of the custom tags and ognl as a core part of the
> framework and also it's core strength. Seeing people on this list discus
> removing it makes me ... somewhat nervous. Why would be the reasons to do
> this. Everything from formatting, typeconversion to databinding uses ognl
> under the hood and provides a lot of flexibility
>
> On 3/23/08, Adam Hardy <ah...@cyberspaceroad.com> wrote:
>> It's a dependency, not a requirement, to be precise although I guess you
>> meant
>> that. To create a stripped-down struts, I'd ditch OGNL and do the
>> conversion and
>> formatting with some other way. Bear in mind, OGNL is used all over for
>> other
>> stuff too, but I did say I'd also ditch that.
>>
>> Bob Tiernay on 21/03/08 15:56, wrote:
>>> Really??? I didn't realize OGNL was a requirement for tags to perform
>>> conversion and formatting.
>>>
>>> --------------------------------------------------
>>> From: "James Mitchell" <jm...@gmail.com>
>>> Sent: Friday, March 21, 2008 9:58 AM
>>> To: "Struts Developers List" <de...@struts.apache.org>
>>> Subject: Re: If I had 1000 hours to give...
>>>
>>>> No it doesn't, but then neither does the Struts tags if "no OGNL" :)
>>>>
>>>> On Fri, Mar 21, 2008 at 9:45 AM, Adam Hardy <
>>>> ahardy.struts@cyberspaceroad.com> wrote:
>>>>
>>>>> Really??? I don't think jsp:getProperty does conversion and formatting
>> -
>>>>> does it?
>>>>>
>>>>> James Mitchell on 20/03/08 16:49, wrote:
>>>>>> Actually, and not trying to be funny here, but ... that's available
>>>>> today...
>>>>>> <jsp:getProperty name="myBean" property="foo"/>
>>>>>>
>>>>>> http://java.sun.com/products/jsp/tags/11/tags11.html
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Mar 20, 2008 at 11:42 AM, Adam Hardy <
>>>>>> ahardy.struts@cyberspaceroad.com> wrote:
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> in fact, i'd write a new taglibrary with just lightweight support
>> for
>>>>> form
>>>>>>> properties, conversion, and formatting. No HTML, no Ajax, no OGNL,
>> no
>>>>>>> value stack.
>>>>>>>
>>>>>>> Then I'd do a session of performance testing to see what the
>>>>> improvement
>>>>>>> was
>>>>>>> (did somebody else suggest that?).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: If I had 1000 hours to give...
Posted by jelmer <jk...@gmail.com>.
First off I was under the impression that the jstl was already supported
through means of the StrutsRequestWrapper, correct ?
Second, I always thought of the custom tags and ognl as a core part of the
framework and also it's core strength. Seeing people on this list discus
removing it makes me ... somewhat nervous. Why would be the reasons to do
this. Everything from formatting, typeconversion to databinding uses ognl
under the hood and provides a lot of flexibility
On 3/23/08, Adam Hardy <ah...@cyberspaceroad.com> wrote:
>
> It's a dependency, not a requirement, to be precise although I guess you
> meant
> that. To create a stripped-down struts, I'd ditch OGNL and do the
> conversion and
> formatting with some other way. Bear in mind, OGNL is used all over for
> other
> stuff too, but I did say I'd also ditch that.
>
> Bob Tiernay on 21/03/08 15:56, wrote:
> > Really??? I didn't realize OGNL was a requirement for tags to perform
> > conversion and formatting.
> >
> > --------------------------------------------------
> > From: "James Mitchell" <jm...@gmail.com>
> > Sent: Friday, March 21, 2008 9:58 AM
> > To: "Struts Developers List" <de...@struts.apache.org>
> > Subject: Re: If I had 1000 hours to give...
> >
> >> No it doesn't, but then neither does the Struts tags if "no OGNL" :)
> >>
> >> On Fri, Mar 21, 2008 at 9:45 AM, Adam Hardy <
> >> ahardy.struts@cyberspaceroad.com> wrote:
> >>
> >>> Really??? I don't think jsp:getProperty does conversion and formatting
> -
> >>> does it?
> >>>
> >>> James Mitchell on 20/03/08 16:49, wrote:
> >>> > Actually, and not trying to be funny here, but ... that's available
> >>> today...
> >>> >
> >>> > <jsp:getProperty name="myBean" property="foo"/>
> >>> >
> >>> > http://java.sun.com/products/jsp/tags/11/tags11.html
> >>> >
> >>> >
> >>> >
> >>> > On Thu, Mar 20, 2008 at 11:42 AM, Adam Hardy <
> >>> > ahardy.struts@cyberspaceroad.com> wrote:
> >>> >
> >>> >> +1
> >>> >>
> >>> >> in fact, i'd write a new taglibrary with just lightweight support
> for
> >>> form
> >>> >> properties, conversion, and formatting. No HTML, no Ajax, no OGNL,
> no
> >>> >> value stack.
> >>> >>
> >>> >> Then I'd do a session of performance testing to see what the
> >>> improvement
> >>> >> was
> >>> >> (did somebody else suggest that?).
> >>> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: If I had 1000 hours to give...
Posted by Adam Hardy <ah...@cyberspaceroad.com>.
It's a dependency, not a requirement, to be precise although I guess you meant
that. To create a stripped-down struts, I'd ditch OGNL and do the conversion and
formatting with some other way. Bear in mind, OGNL is used all over for other
stuff too, but I did say I'd also ditch that.
Bob Tiernay on 21/03/08 15:56, wrote:
> Really??? I didn't realize OGNL was a requirement for tags to perform
> conversion and formatting.
>
> --------------------------------------------------
> From: "James Mitchell" <jm...@gmail.com>
> Sent: Friday, March 21, 2008 9:58 AM
> To: "Struts Developers List" <de...@struts.apache.org>
> Subject: Re: If I had 1000 hours to give...
>
>> No it doesn't, but then neither does the Struts tags if "no OGNL" :)
>>
>> On Fri, Mar 21, 2008 at 9:45 AM, Adam Hardy <
>> ahardy.struts@cyberspaceroad.com> wrote:
>>
>>> Really??? I don't think jsp:getProperty does conversion and formatting -
>>> does it?
>>>
>>> James Mitchell on 20/03/08 16:49, wrote:
>>> > Actually, and not trying to be funny here, but ... that's available
>>> today...
>>> >
>>> > <jsp:getProperty name="myBean" property="foo"/>
>>> >
>>> > http://java.sun.com/products/jsp/tags/11/tags11.html
>>> >
>>> >
>>> >
>>> > On Thu, Mar 20, 2008 at 11:42 AM, Adam Hardy <
>>> > ahardy.struts@cyberspaceroad.com> wrote:
>>> >
>>> >> +1
>>> >>
>>> >> in fact, i'd write a new taglibrary with just lightweight support for
>>> form
>>> >> properties, conversion, and formatting. No HTML, no Ajax, no OGNL, no
>>> >> value stack.
>>> >>
>>> >> Then I'd do a session of performance testing to see what the
>>> improvement
>>> >> was
>>> >> (did somebody else suggest that?).
>>> >>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: If I had 1000 hours to give...
Posted by Bob Tiernay <bt...@hotmail.com>.
Really??? I didn't realize OGNL was a requirement for tags to perform
conversion and formatting.
--------------------------------------------------
From: "James Mitchell" <jm...@gmail.com>
Sent: Friday, March 21, 2008 9:58 AM
To: "Struts Developers List" <de...@struts.apache.org>
Subject: Re: If I had 1000 hours to give...
> No it doesn't, but then neither does the Struts tags if "no OGNL" :)
>
> On Fri, Mar 21, 2008 at 9:45 AM, Adam Hardy <
> ahardy.struts@cyberspaceroad.com> wrote:
>
>> Really??? I don't think jsp:getProperty does conversion and formatting -
>> does it?
>>
>> James Mitchell on 20/03/08 16:49, wrote:
>> > Actually, and not trying to be funny here, but ... that's available
>> today...
>> >
>> > <jsp:getProperty name="myBean" property="foo"/>
>> >
>> > http://java.sun.com/products/jsp/tags/11/tags11.html
>> >
>> >
>> >
>> > On Thu, Mar 20, 2008 at 11:42 AM, Adam Hardy <
>> > ahardy.struts@cyberspaceroad.com> wrote:
>> >
>> >> +1
>> >>
>> >> in fact, i'd write a new taglibrary with just lightweight support for
>> form
>> >> properties, conversion, and formatting. No HTML, no Ajax, no OGNL, no
>> >> value stack.
>> >>
>> >> Then I'd do a session of performance testing to see what the
>> improvement
>> >> was
>> >> (did somebody else suggest that?).
>> >>
>> >>
>> >> Antonio Petrelli on 20/03/08 07:54, wrote:
>> >>> Just one item:
>> >>> - allow the use of JSTL, instead of special tags.
>> >>> If it is already possible, well, forgive me :-)
>> >>>
>> >>> Antonio
>> >>>
>> >>> 2008/3/20, Al Sutton <al...@alsutton.com>:
>> >>>> My list;
>> >>>>
>> >>>> - Overhaul the AJAX plugins so that we're up to date on dojo and we
>> >> have a
>> >>>> framework for adding other AJAX library plug-ins whilst maintaining
>> >>>> a
>> >> core
>> >>>> tag set.
>> >>>> - Overhaul message passing so that action errors and action messages
>> >> could
>> >>>> be persisted through redirects with no user configuration or
>> validation
>> >>>> issues.
>> >>>> - Overhaul zero configuration to allow results to be defined at
>> method
>> >>>> level
>> >>>> - Complete the move to Generics.
>> >>>> - Thrash the framework through a profiler to look for optimization
>> >>>> opportunities.
>> >>>> - and with the spare time; build a school in a third work country
>> >>>> :).
>> >>>>
>> >>>>
>> >>>> Al.
>> >>>>
>> >>>>
>> >>>> ----- Original Message -----
>> >>>> From: "Jeromy Evans" <je...@blueskyminds.com.au>
>> >>>> To: "Struts Developers List" <de...@struts.apache.org>
>> >>>> Sent: Thursday, March 20, 2008 7:08 AM
>> >>>> Subject: If I had 1000 hours to give...
>> >>>>
>> >>>>
>> >>>>> It's been quiet lately so I thought I'd throw something out there.
>> >>>>>
>> >>>>> If you could give 1000 hours to the Struts 2 project, what would
>> >>>>> you
>> >> do?
>> >>>>> I would like to it become the SOA framework of choice through :
>> >>>>> - SEO-friendly URLs become the default and users never have to
>> >>>>> think
>> >>>> about
>> >>>>> it again;
>> >>>>> - allow action methods to be bound to an http method and allow
>> results
>> >>>> to
>> >>>>> be easily bound to the result code and requested content type (as
>> per
>> >>>> REST
>> >>>>> plugin)
>> >>>>> - support content in the request (eg text/xml or text/json
>> >>>> content-type),
>> >>>>> deserialize and set the model of the action (the reverse of the
>> >>>>> REST
>> >>>>> plugin)
>> >>>>> - allow actions to be pojos and delete ActionSupport (without
>> >>>>> losing
>> >>>>> implicit i18n and validation functionality)
>> >>>>> - allow hot deployment & run-time management of actions (OSGi??)
>> >>>>> - refactor UIBean & XWork component so there's only one model and
>> one
>> >>>>> template per tag and they're easy to unit test (code-generate the
>> >>>>> wrappers/template models/taglibs)
>> >>>>> - action scope and component scope become first-class concepts
>> >>>> (integrate
>> >>>>> the plugins)
>> >>>>> - add run-time developer tools; configuration browser becomes
>> standard
>> >>>> in
>> >>>>> developer mode and add a resource bundle browser
>> >>>>> - delete all ajax-like tags and funky tags; add standard
>> interceptors
>> >> &
>> >>>>> models to ease integration with the client-side libraries, groovy,
>> >>>> grails,
>> >>>>> JSF, struts1 (and others?). tags move to plugin.
>> >>>>> - I don't have an opinion about portal support but I'm sure it's
>> >>>> important
>> >>>>> I think I ran out of hours already!
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
>
> --
> James Mitchell
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: If I had 1000 hours to give...
Posted by James Mitchell <jm...@gmail.com>.
No it doesn't, but then neither does the Struts tags if "no OGNL" :)
On Fri, Mar 21, 2008 at 9:45 AM, Adam Hardy <
ahardy.struts@cyberspaceroad.com> wrote:
> Really??? I don't think jsp:getProperty does conversion and formatting -
> does it?
>
> James Mitchell on 20/03/08 16:49, wrote:
> > Actually, and not trying to be funny here, but ... that's available
> today...
> >
> > <jsp:getProperty name="myBean" property="foo"/>
> >
> > http://java.sun.com/products/jsp/tags/11/tags11.html
> >
> >
> >
> > On Thu, Mar 20, 2008 at 11:42 AM, Adam Hardy <
> > ahardy.struts@cyberspaceroad.com> wrote:
> >
> >> +1
> >>
> >> in fact, i'd write a new taglibrary with just lightweight support for
> form
> >> properties, conversion, and formatting. No HTML, no Ajax, no OGNL, no
> >> value stack.
> >>
> >> Then I'd do a session of performance testing to see what the
> improvement
> >> was
> >> (did somebody else suggest that?).
> >>
> >>
> >> Antonio Petrelli on 20/03/08 07:54, wrote:
> >>> Just one item:
> >>> - allow the use of JSTL, instead of special tags.
> >>> If it is already possible, well, forgive me :-)
> >>>
> >>> Antonio
> >>>
> >>> 2008/3/20, Al Sutton <al...@alsutton.com>:
> >>>> My list;
> >>>>
> >>>> - Overhaul the AJAX plugins so that we're up to date on dojo and we
> >> have a
> >>>> framework for adding other AJAX library plug-ins whilst maintaining a
> >> core
> >>>> tag set.
> >>>> - Overhaul message passing so that action errors and action messages
> >> could
> >>>> be persisted through redirects with no user configuration or
> validation
> >>>> issues.
> >>>> - Overhaul zero configuration to allow results to be defined at
> method
> >>>> level
> >>>> - Complete the move to Generics.
> >>>> - Thrash the framework through a profiler to look for optimization
> >>>> opportunities.
> >>>> - and with the spare time; build a school in a third work country :).
> >>>>
> >>>>
> >>>> Al.
> >>>>
> >>>>
> >>>> ----- Original Message -----
> >>>> From: "Jeromy Evans" <je...@blueskyminds.com.au>
> >>>> To: "Struts Developers List" <de...@struts.apache.org>
> >>>> Sent: Thursday, March 20, 2008 7:08 AM
> >>>> Subject: If I had 1000 hours to give...
> >>>>
> >>>>
> >>>>> It's been quiet lately so I thought I'd throw something out there.
> >>>>>
> >>>>> If you could give 1000 hours to the Struts 2 project, what would you
> >> do?
> >>>>> I would like to it become the SOA framework of choice through :
> >>>>> - SEO-friendly URLs become the default and users never have to think
> >>>> about
> >>>>> it again;
> >>>>> - allow action methods to be bound to an http method and allow
> results
> >>>> to
> >>>>> be easily bound to the result code and requested content type (as
> per
> >>>> REST
> >>>>> plugin)
> >>>>> - support content in the request (eg text/xml or text/json
> >>>> content-type),
> >>>>> deserialize and set the model of the action (the reverse of the REST
> >>>>> plugin)
> >>>>> - allow actions to be pojos and delete ActionSupport (without losing
> >>>>> implicit i18n and validation functionality)
> >>>>> - allow hot deployment & run-time management of actions (OSGi??)
> >>>>> - refactor UIBean & XWork component so there's only one model and
> one
> >>>>> template per tag and they're easy to unit test (code-generate the
> >>>>> wrappers/template models/taglibs)
> >>>>> - action scope and component scope become first-class concepts
> >>>> (integrate
> >>>>> the plugins)
> >>>>> - add run-time developer tools; configuration browser becomes
> standard
> >>>> in
> >>>>> developer mode and add a resource bundle browser
> >>>>> - delete all ajax-like tags and funky tags; add standard
> interceptors
> >> &
> >>>>> models to ease integration with the client-side libraries, groovy,
> >>>> grails,
> >>>>> JSF, struts1 (and others?). tags move to plugin.
> >>>>> - I don't have an opinion about portal support but I'm sure it's
> >>>> important
> >>>>> I think I ran out of hours already!
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
James Mitchell
Re: If I had 1000 hours to give...
Posted by Adam Hardy <ah...@cyberspaceroad.com>.
Really??? I don't think jsp:getProperty does conversion and formatting - does it?
James Mitchell on 20/03/08 16:49, wrote:
> Actually, and not trying to be funny here, but ... that's available today...
>
> <jsp:getProperty name="myBean" property="foo"/>
>
> http://java.sun.com/products/jsp/tags/11/tags11.html
>
>
>
> On Thu, Mar 20, 2008 at 11:42 AM, Adam Hardy <
> ahardy.struts@cyberspaceroad.com> wrote:
>
>> +1
>>
>> in fact, i'd write a new taglibrary with just lightweight support for form
>> properties, conversion, and formatting. No HTML, no Ajax, no OGNL, no
>> value stack.
>>
>> Then I'd do a session of performance testing to see what the improvement
>> was
>> (did somebody else suggest that?).
>>
>>
>> Antonio Petrelli on 20/03/08 07:54, wrote:
>>> Just one item:
>>> - allow the use of JSTL, instead of special tags.
>>> If it is already possible, well, forgive me :-)
>>>
>>> Antonio
>>>
>>> 2008/3/20, Al Sutton <al...@alsutton.com>:
>>>> My list;
>>>>
>>>> - Overhaul the AJAX plugins so that we're up to date on dojo and we
>> have a
>>>> framework for adding other AJAX library plug-ins whilst maintaining a
>> core
>>>> tag set.
>>>> - Overhaul message passing so that action errors and action messages
>> could
>>>> be persisted through redirects with no user configuration or validation
>>>> issues.
>>>> - Overhaul zero configuration to allow results to be defined at method
>>>> level
>>>> - Complete the move to Generics.
>>>> - Thrash the framework through a profiler to look for optimization
>>>> opportunities.
>>>> - and with the spare time; build a school in a third work country :).
>>>>
>>>>
>>>> Al.
>>>>
>>>>
>>>> ----- Original Message -----
>>>> From: "Jeromy Evans" <je...@blueskyminds.com.au>
>>>> To: "Struts Developers List" <de...@struts.apache.org>
>>>> Sent: Thursday, March 20, 2008 7:08 AM
>>>> Subject: If I had 1000 hours to give...
>>>>
>>>>
>>>>> It's been quiet lately so I thought I'd throw something out there.
>>>>>
>>>>> If you could give 1000 hours to the Struts 2 project, what would you
>> do?
>>>>> I would like to it become the SOA framework of choice through :
>>>>> - SEO-friendly URLs become the default and users never have to think
>>>> about
>>>>> it again;
>>>>> - allow action methods to be bound to an http method and allow results
>>>> to
>>>>> be easily bound to the result code and requested content type (as per
>>>> REST
>>>>> plugin)
>>>>> - support content in the request (eg text/xml or text/json
>>>> content-type),
>>>>> deserialize and set the model of the action (the reverse of the REST
>>>>> plugin)
>>>>> - allow actions to be pojos and delete ActionSupport (without losing
>>>>> implicit i18n and validation functionality)
>>>>> - allow hot deployment & run-time management of actions (OSGi??)
>>>>> - refactor UIBean & XWork component so there's only one model and one
>>>>> template per tag and they're easy to unit test (code-generate the
>>>>> wrappers/template models/taglibs)
>>>>> - action scope and component scope become first-class concepts
>>>> (integrate
>>>>> the plugins)
>>>>> - add run-time developer tools; configuration browser becomes standard
>>>> in
>>>>> developer mode and add a resource bundle browser
>>>>> - delete all ajax-like tags and funky tags; add standard interceptors
>> &
>>>>> models to ease integration with the client-side libraries, groovy,
>>>> grails,
>>>>> JSF, struts1 (and others?). tags move to plugin.
>>>>> - I don't have an opinion about portal support but I'm sure it's
>>>> important
>>>>> I think I ran out of hours already!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: If I had 1000 hours to give...
Posted by James Mitchell <jm...@gmail.com>.
Actually, and not trying to be funny here, but ... that's available today...
<jsp:getProperty name="myBean" property="foo"/>
http://java.sun.com/products/jsp/tags/11/tags11.html
On Thu, Mar 20, 2008 at 11:42 AM, Adam Hardy <
ahardy.struts@cyberspaceroad.com> wrote:
> +1
>
> in fact, i'd write a new taglibrary with just lightweight support for form
> properties, conversion, and formatting. No HTML, no Ajax, no OGNL, no
> value stack.
>
> Then I'd do a session of performance testing to see what the improvement
> was
> (did somebody else suggest that?).
>
>
> Antonio Petrelli on 20/03/08 07:54, wrote:
> > Just one item:
> > - allow the use of JSTL, instead of special tags.
> > If it is already possible, well, forgive me :-)
> >
> > Antonio
> >
> > 2008/3/20, Al Sutton <al...@alsutton.com>:
> >> My list;
> >>
> >> - Overhaul the AJAX plugins so that we're up to date on dojo and we
> have a
> >> framework for adding other AJAX library plug-ins whilst maintaining a
> core
> >> tag set.
> >> - Overhaul message passing so that action errors and action messages
> could
> >> be persisted through redirects with no user configuration or validation
> >> issues.
> >> - Overhaul zero configuration to allow results to be defined at method
> >> level
> >> - Complete the move to Generics.
> >> - Thrash the framework through a profiler to look for optimization
> >> opportunities.
> >> - and with the spare time; build a school in a third work country :).
> >>
> >>
> >> Al.
> >>
> >>
> >> ----- Original Message -----
> >> From: "Jeromy Evans" <je...@blueskyminds.com.au>
> >> To: "Struts Developers List" <de...@struts.apache.org>
> >> Sent: Thursday, March 20, 2008 7:08 AM
> >> Subject: If I had 1000 hours to give...
> >>
> >>
> >>> It's been quiet lately so I thought I'd throw something out there.
> >>>
> >>> If you could give 1000 hours to the Struts 2 project, what would you
> do?
> >>>
> >>> I would like to it become the SOA framework of choice through :
> >>> - SEO-friendly URLs become the default and users never have to think
> >> about
> >>> it again;
> >>> - allow action methods to be bound to an http method and allow results
> >> to
> >>> be easily bound to the result code and requested content type (as per
> >> REST
> >>> plugin)
> >>> - support content in the request (eg text/xml or text/json
> >> content-type),
> >>> deserialize and set the model of the action (the reverse of the REST
> >>> plugin)
> >>> - allow actions to be pojos and delete ActionSupport (without losing
> >>> implicit i18n and validation functionality)
> >>> - allow hot deployment & run-time management of actions (OSGi??)
> >>> - refactor UIBean & XWork component so there's only one model and one
> >>> template per tag and they're easy to unit test (code-generate the
> >>> wrappers/template models/taglibs)
> >>> - action scope and component scope become first-class concepts
> >> (integrate
> >>> the plugins)
> >>> - add run-time developer tools; configuration browser becomes standard
> >> in
> >>> developer mode and add a resource bundle browser
> >>> - delete all ajax-like tags and funky tags; add standard interceptors
> &
> >>> models to ease integration with the client-side libraries, groovy,
> >> grails,
> >>> JSF, struts1 (and others?). tags move to plugin.
> >>> - I don't have an opinion about portal support but I'm sure it's
> >> important
> >>> I think I ran out of hours already!
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
James Mitchell
Re: If I had 1000 hours to give...
Posted by Adam Hardy <ah...@cyberspaceroad.com>.
+1
in fact, i'd write a new taglibrary with just lightweight support for form
properties, conversion, and formatting. No HTML, no Ajax, no OGNL, no value stack.
Then I'd do a session of performance testing to see what the improvement was
(did somebody else suggest that?).
Antonio Petrelli on 20/03/08 07:54, wrote:
> Just one item:
> - allow the use of JSTL, instead of special tags.
> If it is already possible, well, forgive me :-)
>
> Antonio
>
> 2008/3/20, Al Sutton <al...@alsutton.com>:
>> My list;
>>
>> - Overhaul the AJAX plugins so that we're up to date on dojo and we have a
>> framework for adding other AJAX library plug-ins whilst maintaining a core
>> tag set.
>> - Overhaul message passing so that action errors and action messages could
>> be persisted through redirects with no user configuration or validation
>> issues.
>> - Overhaul zero configuration to allow results to be defined at method
>> level
>> - Complete the move to Generics.
>> - Thrash the framework through a profiler to look for optimization
>> opportunities.
>> - and with the spare time; build a school in a third work country :).
>>
>>
>> Al.
>>
>>
>> ----- Original Message -----
>> From: "Jeromy Evans" <je...@blueskyminds.com.au>
>> To: "Struts Developers List" <de...@struts.apache.org>
>> Sent: Thursday, March 20, 2008 7:08 AM
>> Subject: If I had 1000 hours to give...
>>
>>
>>> It's been quiet lately so I thought I'd throw something out there.
>>>
>>> If you could give 1000 hours to the Struts 2 project, what would you do?
>>>
>>> I would like to it become the SOA framework of choice through :
>>> - SEO-friendly URLs become the default and users never have to think
>> about
>>> it again;
>>> - allow action methods to be bound to an http method and allow results
>> to
>>> be easily bound to the result code and requested content type (as per
>> REST
>>> plugin)
>>> - support content in the request (eg text/xml or text/json
>> content-type),
>>> deserialize and set the model of the action (the reverse of the REST
>>> plugin)
>>> - allow actions to be pojos and delete ActionSupport (without losing
>>> implicit i18n and validation functionality)
>>> - allow hot deployment & run-time management of actions (OSGi??)
>>> - refactor UIBean & XWork component so there's only one model and one
>>> template per tag and they're easy to unit test (code-generate the
>>> wrappers/template models/taglibs)
>>> - action scope and component scope become first-class concepts
>> (integrate
>>> the plugins)
>>> - add run-time developer tools; configuration browser becomes standard
>> in
>>> developer mode and add a resource bundle browser
>>> - delete all ajax-like tags and funky tags; add standard interceptors &
>>> models to ease integration with the client-side libraries, groovy,
>> grails,
>>> JSF, struts1 (and others?). tags move to plugin.
>>> - I don't have an opinion about portal support but I'm sure it's
>> important
>>> I think I ran out of hours already!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: If I had 1000 hours to give...
Posted by Antonio Petrelli <an...@gmail.com>.
Just one item:
- allow the use of JSTL, instead of special tags.
If it is already possible, well, forgive me :-)
Antonio
2008/3/20, Al Sutton <al...@alsutton.com>:
>
> My list;
>
> - Overhaul the AJAX plugins so that we're up to date on dojo and we have a
> framework for adding other AJAX library plug-ins whilst maintaining a core
> tag set.
> - Overhaul message passing so that action errors and action messages could
> be persisted through redirects with no user configuration or validation
> issues.
> - Overhaul zero configuration to allow results to be defined at method
> level
> - Complete the move to Generics.
> - Thrash the framework through a profiler to look for optimization
> opportunities.
> - and with the spare time; build a school in a third work country :).
>
>
> Al.
>
>
> ----- Original Message -----
> From: "Jeromy Evans" <je...@blueskyminds.com.au>
> To: "Struts Developers List" <de...@struts.apache.org>
> Sent: Thursday, March 20, 2008 7:08 AM
> Subject: If I had 1000 hours to give...
>
>
> > It's been quiet lately so I thought I'd throw something out there.
> >
> > If you could give 1000 hours to the Struts 2 project, what would you do?
> >
> > I would like to it become the SOA framework of choice through :
> > - SEO-friendly URLs become the default and users never have to think
> about
> > it again;
> > - allow action methods to be bound to an http method and allow results
> to
> > be easily bound to the result code and requested content type (as per
> REST
> > plugin)
> > - support content in the request (eg text/xml or text/json
> content-type),
> > deserialize and set the model of the action (the reverse of the REST
> > plugin)
> > - allow actions to be pojos and delete ActionSupport (without losing
> > implicit i18n and validation functionality)
> > - allow hot deployment & run-time management of actions (OSGi??)
> > - refactor UIBean & XWork component so there's only one model and one
> > template per tag and they're easy to unit test (code-generate the
> > wrappers/template models/taglibs)
> > - action scope and component scope become first-class concepts
> (integrate
> > the plugins)
> > - add run-time developer tools; configuration browser becomes standard
> in
> > developer mode and add a resource bundle browser
> > - delete all ajax-like tags and funky tags; add standard interceptors &
> > models to ease integration with the client-side libraries, groovy,
> grails,
> > JSF, struts1 (and others?). tags move to plugin.
> > - I don't have an opinion about portal support but I'm sure it's
> important
> >
> > I think I ran out of hours already!
> >
> > cheers,
> > Jeromy Evans
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: If I had 1000 hours to give...
Posted by Brian Pontarelli <br...@pontarelli.com>.
> - Overhaul message passing so that action errors and action messages
> could be persisted through redirects with no user configuration or
> validation issues.
Scopes plugin works pretty well from what I've heard.
> - Overhaul zero configuration to allow results to be defined at method
> level
Convention plugin does this (if I understand correctly).
-bp
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: If I had 1000 hours to give...
Posted by Al Sutton <al...@alsutton.com>.
My list;
- Overhaul the AJAX plugins so that we're up to date on dojo and we have a
framework for adding other AJAX library plug-ins whilst maintaining a core
tag set.
- Overhaul message passing so that action errors and action messages could
be persisted through redirects with no user configuration or validation
issues.
- Overhaul zero configuration to allow results to be defined at method level
- Complete the move to Generics.
- Thrash the framework through a profiler to look for optimization
opportunities.
- and with the spare time; build a school in a third work country :).
Al.
----- Original Message -----
From: "Jeromy Evans" <je...@blueskyminds.com.au>
To: "Struts Developers List" <de...@struts.apache.org>
Sent: Thursday, March 20, 2008 7:08 AM
Subject: If I had 1000 hours to give...
> It's been quiet lately so I thought I'd throw something out there.
>
> If you could give 1000 hours to the Struts 2 project, what would you do?
>
> I would like to it become the SOA framework of choice through :
> - SEO-friendly URLs become the default and users never have to think about
> it again;
> - allow action methods to be bound to an http method and allow results to
> be easily bound to the result code and requested content type (as per REST
> plugin)
> - support content in the request (eg text/xml or text/json content-type),
> deserialize and set the model of the action (the reverse of the REST
> plugin)
> - allow actions to be pojos and delete ActionSupport (without losing
> implicit i18n and validation functionality)
> - allow hot deployment & run-time management of actions (OSGi??)
> - refactor UIBean & XWork component so there's only one model and one
> template per tag and they're easy to unit test (code-generate the
> wrappers/template models/taglibs)
> - action scope and component scope become first-class concepts (integrate
> the plugins)
> - add run-time developer tools; configuration browser becomes standard in
> developer mode and add a resource bundle browser
> - delete all ajax-like tags and funky tags; add standard interceptors &
> models to ease integration with the client-side libraries, groovy, grails,
> JSF, struts1 (and others?). tags move to plugin.
> - I don't have an opinion about portal support but I'm sure it's important
>
> I think I ran out of hours already!
>
> cheers,
> Jeromy Evans
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: If I had 1000 hours to give...
Posted by Nils-Helge Garli Hegvik <ni...@gmail.com>.
> If you could give 1000 hours to the Struts 2 project, what would you do?
I would try to:
- Completely refactor all tags/components (it's really hard to extend
and customize) and extract them to a plugin, making it easier to drop
in a different tag library implementation.
- Simplify and standardize the tag syntax. We'll lose some
flexibility, but I would be willing to give that up if it makes Struts
2 more accessible for the "crowd".
- Simplify configuration, focusing on annotations and convention over
configuration.
- +1 on generics
- Make it possible to override individual interceptors (swap with a
new implementation with the same name) without having to redefine the
complete interceptor stack (which is really an xwork issue)
- AJAX and JSR286 support for the portlet plugin
Nils-H
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: If I had 1000 hours to give...
Posted by Bob Tiernay <bt...@hotmail.com>.
I would like to see:
- provisions for AspectJ as a replacement/alternative for/to interceptors
- +1 for native Guice/Spring support
- More flexible i18n structuring and packaging (multiple resource bundles
via configuration over convention)
- integration support for existing validation frameworks (hibernate
validator and the highly configurable OVal)
- 100% annotation support (anything in struts.xml can be configured via
annotations... including things like <param> et al.)
- Scopes / web beans as first class citizens (a la the scope plugin)
- Faster releases (um, 2.1 still isn't out... Don is your computer fixed
yet?!?!)
- A strong eye on spring MVC and Stripes to see what else we can improve
upon
--------------------------------------------------
From: "Jeromy Evans" <je...@blueskyminds.com.au>
Sent: Thursday, March 20, 2008 3:08 AM
To: "Struts Developers List" <de...@struts.apache.org>
Subject: If I had 1000 hours to give...
> It's been quiet lately so I thought I'd throw something out there.
>
> If you could give 1000 hours to the Struts 2 project, what would you do?
>
> I would like to it become the SOA framework of choice through :
> - SEO-friendly URLs become the default and users never have to think about
> it again;
> - allow action methods to be bound to an http method and allow results to
> be easily bound to the result code and requested content type (as per REST
> plugin)
> - support content in the request (eg text/xml or text/json content-type),
> deserialize and set the model of the action (the reverse of the REST
> plugin)
> - allow actions to be pojos and delete ActionSupport (without losing
> implicit i18n and validation functionality)
> - allow hot deployment & run-time management of actions (OSGi??)
> - refactor UIBean & XWork component so there's only one model and one
> template per tag and they're easy to unit test (code-generate the
> wrappers/template models/taglibs)
> - action scope and component scope become first-class concepts (integrate
> the plugins)
> - add run-time developer tools; configuration browser becomes standard in
> developer mode and add a resource bundle browser
> - delete all ajax-like tags and funky tags; add standard interceptors &
> models to ease integration with the client-side libraries, groovy, grails,
> JSF, struts1 (and others?). tags move to plugin.
> - I don't have an opinion about portal support but I'm sure it's important
>
> I think I ran out of hours already!
>
> cheers,
> Jeromy Evans
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org