Great! Happy that I know these now! Are we, volunteers, allowed to help/contribute with such structural changes? I hope yes. If so, I have passion in `support for actors/asynchronous request handling`. Could you please register an issue with a few directive details? then we can pick and start work on that :) same ones for `less static util classes and coupled code` step by step. (`make JSON plugin more configurable` is simple to pick, while already has issues; `improve the framework's security` is also clear enough to being considered by us).
Ton of thanks for your time and writing for us! On 7/18/2017 10:37 AM, Lukasz Lenart wrote: > 2017-07-17 10:49 GMT+02:00 Yasser Zamani <yasser.zam...@live.com>: >> Absolutely, I did not mean you yourself should do or did something :) I >> just asked these to know if me/we, contributors, should just wait for >> user's demands in jira. or no, it's needed to analysis, study and discus >> competitors here, for new applicable (not all) features or improvements >> in Struts (e.g. you informed me that JSON and Angular are reasons so I >> can study them if any applicable feature could be added to S2). > > No, we should definitely not sit and wait :) Rather figure out what > should be improved and what new features would be nice to have - and > then code and implement them :) > > My two new features on the radar: > - make JSON plugin more configurable, there are few issues related to it [1] > - add support for actors/asynchronous request handling > > Besides these, my main goal is to improve the framework's security and > flexibility (less static util classes and coupled code). > > [1] > https://issues.apache.org/jira/issues/?jql=component%20%3D%20%22Plugin%20-%20JSON%22%20AND%20project%20%3D%20WW%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC > > > Regards >
