And there is still place for improvement, take a look at the
ComponentTagSupport#doStartTag, each time instance of Container is
taken from Dispatcher, which means each time configuration is checked
if needs to be reloaded - obviously it doesn't make sense to check
that or reload configuration durin
2012/12/12 Philip Luppens :
> I'd say to go for it, but please do explain what the issue was for archival
> reasons, since the original ticket[1] did not receive any update yet.
Ok, you're right. The problem is related to my FileManager
refactorings and introduced FileManagerFactory with default
i
On Wed, Dec 12, 2012 at 6:30 PM, Łukasz Lenart wrote:
> Johannes discovered a huge performance issue which is already solved in
> trunk (2.3.8) so I'm going to prepare a new release ASAP. Is threre any
> other important outstanding issue that should be solved before the release?
>
> (on mobile)
>
Johannes discovered a huge performance issue which is already solved in
trunk (2.3.8) so I'm going to prepare a new release ASAP. Is threre any
other important outstanding issue that should be solved before the release?
(on mobile)
2012/12/12 ChadDavis :
> Just looking through the codebase and I'm curious as to what the "ng" part
> of this package referes to?
>
> org.apache.struts2.dispatcher.ng
As Dave said, Next Generation but with 3.x we're planning to remove
existing FilterDispatcher and move those new filters to
org.apa
