On Sat, Aug 27, 2011 at 8:30 PM, Steven Benitez <steven.beni...@gmail.com> wrote: > The fact that log4j is an Apache project shouldn't be a deciding > factor, IMO. slf4j is widely adopted and would allow you to easily > route the log messages to your favorite log framework -- be it log4j, > logback, etc.
Some are really emotional on their AL 2.0 license - me included. For me (and some others) it is a very important factor > > On Sat, Aug 27, 2011 at 2:15 PM, Maurizio Cucchiara > <mcucchi...@apache.org> wrote: >> Hi guys, >>> * Struts doesn't use Spring for DI. It actually uses an early version of >>> Guice. >> Yep, IIRC the original author of Guice wrote the DI module which is >> still in use. >> >>> * There were two annotation-based plugins. One is deprecated, the other is >>> not. Take a look at the convention plugin. There has been some debate over >>> XML vs annotations for action mapping and many of us (including myself) >>> would like to keep the XML. >> That's correct too, many of the S2 user prefer the XML approach >> (myself included), since allows to do stuff like hot reload in >> devMode, automated documentation, etc. >> >> Regarding log4j 2.0, IIRC the latest release should adopt the same >> approach of slf4j (with the plus that log4j is an Apache software). >> >> Personally, I would opposed to the name "Struts 3", it was already >> argument of debate, it would puzzle the final user (the two different >> major version correspond to different software). I think the original >> mistake was to call WebWork Struts 2. >> >> When Christian has talked about WebWork, I assumed he was referring to >> the opensymphony stuff (like packaging, etc). Again, there has been >> some debate over as well. >> Anyway, I think that what Christian suggested, is a good starting point. >> >> Maurizio Cucchiara >> >> >> On 27 August 2011 17:41, Steven Benitez <steven.beni...@gmail.com> wrote: >>> >>> >>> * It would make a lot more sense to adopt slf4j than log4j. This allows >>> developers to plug-in any logging framework they want. This has been >>> discussed, but I don't remember what was decided. >>> >>> * I think you mean XWork, since Struts2 _is_ WebWork. >>> >>> On Sat, Aug 27, 2011 at 8:04 AM, Frans Thamura <fr...@meruvian.org> wrote: >>> >>>> From me >>>> >>>> Total rest developer >>>> On Aug 27, 2011 6:10 PM, "Christian Grobmeier" <grobme...@gmail.com> >>>> wrote: >>>> > Hello guys, >>>> > >>>> > are there already plans for a Struts 3? >>>> > >>>> > I have several features I would love to see. The good user I am, I >>>> > share it with you :-) >>>> > >>>> > * JSR-330 >>>> > Currently Struts uses Spring as DI provider. But there is now a >>>> > standard. Should't it be used? Reference implementation is available >>>> > with Google Juice. Spring could be optional only. My guess is that >>>> > many features of Spring are unused for a normal webapp and using plain >>>> > Java is always nice, if it is not java.util.logging (kidding) >>>> > http://www.jcp.org/en/jsr/detail?id=330 >>>> > >>>> > * Annotation-driven Actionmapping >>>> > There was / is a Plugin doing that, but it was deprecated recently. >>>> > Why not break up Struts and check if Annotations aren't possible from >>>> > the core? XML is out - Annotations are in. These Annotations was one >>>> > of the "coolest" features when somebody has explained me why the Play >>>> > Framework is so cool >>>> > >>>> > * Log4j 2.0 >>>> > Currently there is some effort with Log4j 2.0. It is far from >>>> > proudction ready at the moment, but Struts 3 could take a while. >>>> > Besides, version used by struts is 1.2.9. But the current is 1.2.16. >>>> > Time for an upgrade in current development? >>>> > >>>> > * Complete assimilation of WebWork >>>> > As a user I always had some trouble with WebWork separated from >>>> > Struts. I remember the discussion when WebWork was merged - it was all >>>> > about easy migration for WebWork users and such. Now, with changing >>>> > the Actionmapping to Annotations and use of JSR-330 it might be a good >>>> > time to merge WebWork fully into Struts and change the package names. >>>> > I am not sure if I am aware on all complications, but my users heart >>>> > desires easy to understand modules :-) >>>> > >>>> > * OGNL 4.0 >>>> > OGNL is a Commons project now. It may take a while until the next >>>> > release, probably it is ready for a Struts 3, maybe even earlier. >>>> > Latest with Struts 3, OGNL 4.0 should be there. >>>> > >>>> > >>>> > >>>> > So, I am not sure if there is enough interest or enough manpower to do >>>> > the changes. Maybe there are some other roadmaps around. I couldn't >>>> > find them. In any case, I am interested in your thoughts of the future >>>> > Struts development, be it S2 or S3. >>>> > >>>> > Cheers >>>> > Christian >>>> > >>>> > --------------------------------------------------------------------- >>>> > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >>>> > For additional commands, e-mail: dev-h...@struts.apache.org >>>> > >>>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >> For additional commands, e-mail: dev-h...@struts.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > -- http://www.grobmeier.de --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
