Re: Merging XWork into Struts Core

2014-05-11 Thread Paul Benedict
On Sun, May 11, 2014 at 6:10 AM, Lukasz Lenart wrote: > Basically we have two "core"s - and what I want to do is to merge them > to be the real core (not divided), thus should also remove some clumsy > code which exists in XWork-Core just to satisfy Struts-Core's needs. > And also reduce some dupl

Re: Less boilerplate in code

2014-05-11 Thread Johannes Geppert
I prefer to switch slf4j instead of an own xwork logging facade. Regards Johannes # web: http://www.jgeppert.com twitter: http://twitter.com/jogep 2014-05-10 9:43 GMT+02:00 Lukasz Lenart : > Hi, > > What do you think about that idea [1]? > > B

Re: Merging XWork into Struts Core

2014-05-11 Thread Paul Benedict
Instead of merging, perhaps what you really need to do is modify the XWork API to make it more extensible. It does seem a bit crazy you need to constantly change both. XWork should be as un-struts as possible, I think. Cheers, Paul On Fri, May 9, 2014 at 1:00 AM, Lukasz Lenart wrote: > Hi, > >

Re: Merging XWork into Struts Core

2014-05-11 Thread Lukasz Lenart
Basically we have two "core"s - and what I want to do is to merge them to be the real core (not divided), thus should also remove some clumsy code which exists in XWork-Core just to satisfy Struts-Core's needs. And also reduce some duplication like ActionContext and ServletActionContext. Having on