You are probably right, some changes are required on the client side. But ModelAction, as refactored in 2.0, is not the right place to do it. In any case, what you had was the current execute() method, unchanged, and an additional execute_1_0 (or something similar) that wasn't being called. If the changes need to be made, they need to be sprinkled case-by-case into StrutsClientConnector, AbstractWebappClientConnector, AbstractClientConnector, etc.
As I said before, a merge isn't likely to help in this case. Need to identify the changes between the released 1.0 (2.0 was branched from there) ModelAction and the latest version in Branch_1_0. Then, make similar changes to the above classes. I doubt ModelAction will change at all for this.
As far as the 2.0 branch, we have ways yet to go. It is premature to make the branch. But it is getting close to the release to warrant not taking risks with the code. Maybe you can get the changes working and tested on your local machine first? If need be, we can temporarily branch clnt-struts for you to do the final collaboration with Santanu, and when everything works we can merge back to HEAD?
Shash
Hi Shash.
About the ModelAction stuff;
According to Santanu, some of that was needed for the svc-fileupload-struts, as well as other misc. bugfixes. Are other equivalent bugfixes and enhancements already in place in Head (I was unable to determine this, and was
hoping that Santanu would take a look when he had a moment)? Or would it be better at this point to split off a 2.0 branch?
With Santanu back from vacation, I am hopeful about a discussion and assitance on any of the necessary enhancements to ModelAction. Should I wait until 2.0 has been branched off?
Regards, Steve
http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
