[s2] Goal - no experimental code in core for 2.1
With the latest refactorings in XWork that allow plugins to provide code that load Packages, I'd like to suggest that we make it a key design feature of Struts 2.1 that Core includes no code labeled "experimental". Here is what I imagine it would entail: 1. Move the zero conf code (annotations and code from ClasspathConfigurationProvider) into the codebehind plugin. 2. Move restful mapper into its own plugin There are two main general advantages of this from a user perspective: 1. Code from core can be fully trusted to be deemed of GA quality 2. Using zero conf and restful features become easier While the first one is pretty self-explanatory, the second makes sense when you think about how plugins work. Currently, to use the zero conf or restful code, you have to have the right jars, config settings, and follow poorly documented rules. If, for example, the restful code was its own plugin, you could drop the restful jar in and it would configure your application with the appropriate settings automatically - disable .action extension, enable slashes in action names, set the restful mapper, etc. Right now, it takes some voodoo magic to get restful and zero conf working right (especially together), even for me and I wrote most of it :( By moving the zero conf code into the codebehind plugin, we also make it easier to maintain, document, and use for developers. Also, it makes it easier for other plugins, like SmartURL, to provide an alternate zero conf implementation. A different, but related discussion, is how best to provide zero conf in Struts 2, and honestly, I don't see a clear solution yet. What is in core now is ok, SmartURL improves things, but other parts I don't like as much, so by putting them all on the same playing field, I'd hope we encourage innovation. Anyways, back to the main topic, I'd like to get all experimental code out of core. Any objections? Don - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [s2] Goal - no experimental code in core for 2.1
+1 for anything that makes configuration easier Don Brown wrote: With the latest refactorings in XWork that allow plugins to provide code that load Packages, I'd like to suggest that we make it a key design feature of Struts 2.1 that Core includes no code labeled "experimental". Here is what I imagine it would entail: 1. Move the zero conf code (annotations and code from ClasspathConfigurationProvider) into the codebehind plugin. 2. Move restful mapper into its own plugin There are two main general advantages of this from a user perspective: 1. Code from core can be fully trusted to be deemed of GA quality 2. Using zero conf and restful features become easier While the first one is pretty self-explanatory, the second makes sense when you think about how plugins work. Currently, to use the zero conf or restful code, you have to have the right jars, config settings, and follow poorly documented rules. If, for example, the restful code was its own plugin, you could drop the restful jar in and it would configure your application with the appropriate settings automatically - disable .action extension, enable slashes in action names, set the restful mapper, etc. Right now, it takes some voodoo magic to get restful and zero conf working right (especially together), even for me and I wrote most of it :( By moving the zero conf code into the codebehind plugin, we also make it easier to maintain, document, and use for developers. Also, it makes it easier for other plugins, like SmartURL, to provide an alternate zero conf implementation. A different, but related discussion, is how best to provide zero conf in Struts 2, and honestly, I don't see a clear solution yet. What is in core now is ok, SmartURL improves things, but other parts I don't like as much, so by putting them all on the same playing field, I'd hope we encourage innovation. Anyways, back to the main topic, I'd like to get all experimental code out of core. Any objections? Don - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wiki access
You should be all set now. Apologies for the long delay. -- Martin Cooper On 9/26/07, Martin Gilday <[EMAIL PROTECTED]> wrote: > > Thanks, I've faxed in a CLA. > > > - Original message - > From: "Martin Cooper" <[EMAIL PROTECTED]> > To: "Struts Developers List" > Date: Tue, 25 Sep 2007 07:40:14 -0700 > Subject: Re: Wiki access > > On 9/25/07, Martin Gilday <[EMAIL PROTECTED]> wrote: > > > > Hi, > > Could I please have write access to the struts2 wiki? > > > Please read and follow the instructions here: > > http://struts.apache.org/helping.html#documentation > > -- > Martin Cooper > > > I'd like to > > update this page > > > > > http://struts.apache.org/2.0.9/docs/how-do-we-get-access-to-the-session.html > > as it refers to "servlet-config" when in struts-default it is > > "servletConfig". My account email is [EMAIL PROTECTED] > > > > Thanks, > > Martin. > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Wiki access
Thanks Martin, looks to be working fine. - Original message - From: "Martin Cooper" <[EMAIL PROTECTED]> To: "Struts Developers List" Date: Sun, 7 Oct 2007 10:23:37 -0700 Subject: Re: Wiki access You should be all set now. Apologies for the long delay. -- Martin Cooper On 9/26/07, Martin Gilday <[EMAIL PROTECTED]> wrote: > > Thanks, I've faxed in a CLA. > > > - Original message - > From: "Martin Cooper" <[EMAIL PROTECTED]> > To: "Struts Developers List" > Date: Tue, 25 Sep 2007 07:40:14 -0700 > Subject: Re: Wiki access > > On 9/25/07, Martin Gilday <[EMAIL PROTECTED]> wrote: > > > > Hi, > > Could I please have write access to the struts2 wiki? > > > Please read and follow the instructions here: > > http://struts.apache.org/helping.html#documentation > > -- > Martin Cooper > > > I'd like to > > update this page > > > > > http://struts.apache.org/2.0.9/docs/how-do-we-get-access-to-the-session.html > > as it refers to "servlet-config" when in struts-default it is > > "servletConfig". My account email is [EMAIL PROTECTED] > > > > Thanks, > > Martin. > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Source and test maven artifacts for struts2
Is there anyplace where the source and test jars are deployed as part of a release? Looking in the central maven repository and on http://people.apache.org/repo/m2-ibiblio-rsync-repository, I only see the bin artifact. I ran into an issue with needing the test artifact because I extend a JUnit test to test some custom tags I wrote. Deploying the test artifact I could see skipping, however, it seems like having the source artifacts available via maven would be a useful thing. (In fact, it is recommended in the Maven artifact upload guide) Tom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Help me to understand this cord
I m tring to understand a struts code i have found this http://www.nabble.com/How-to-access-static-property-in-jsp-page-using-struts-tf3877595.html#a13090604 Sent from the Struts - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
