Hi again Lukasz,

Sorry for the inconvenience but recently I worked on an issue [1] which directed me to MAYBE a serious problem. I preferred to inform you as it's maybe important enough to ship with upcoming 2.3.16 version!

Thanks in advance!

[1] https://issues.apache.org/jira/browse/WW-4105?focusedCommentId=13811928&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13811928

On Tue 29 Oct 2013 12:20:18 PM IRST, Lukasz Lenart wrote:
2013/10/28 Yasser Zamani <yasser.zam...@live.com>:
Today, I also resolved [1] bug as an improvement (actually was not a bug).
Please see [2] if it's a good idea to ship this improvement with incoming
2.3.16 release.

Thanks in advance!

[1] https://issues.apache.org/jira/browse/WW-4176
[2]
https://issues.apache.org/jira/browse/WW-4176?focusedCommentId=13806734&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13806734

Thanks, I have noticed that but ParametersInterceptor is a monster now
and adding additional logic to it doesn't help :/ I'll leave it for
now as I must figure out some better solution (some kind of
modularisation for interceptors) - just to allow users steer the
behaviour of each interceptor programatically not only via static
settings.


Regards

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Reply via email to