Greetings.

My first pass at merging clnt-struts & keel-core 1.0 -> Head is complete.

HOWEVER, there are two objects where developer teams diverged remarkably and 
incompatably;
ModelAction (execute method) from clnt-struts,
NestedException from keel-core.

If Mike Nash, Shash, Santanu, and Philip Brown would be so kind as to have a look and 
come up with the actual solution, it would be appreciated.

I checked in a modified version of ModelAction.  BOTH versions of the execute method 
are present, with the 1.0 version called execute1_0.

With NestedException, the handle it was keeping to the exception that caused the 
current exception was removed due to serialization issues.  This removal breaks some 
code in the HEAD version of ModelAction.execute.

About NestedException.  I would like to vote on removing this class (or at least 
deprecating it).
Starting with JDK 1.4, Throwables all implement Serializable (this may have been 
present before 1.4, not sure) and now have a Cause property, which is the Throwable 
which caused the current Exception.  As a result, the bulk of the methods provided by 
this class are now already provided by Throwable, perhaps making this class redundant.

Looking forward to seeing this merge completed.

Regards,
Steve

PS: I ran "ant tests" before I checked in, and everything passed.

PPS: Eclipse has a number of Wizards to merge code from HEAD to a given branch.  Would 
it be possible that once this merge was done, for all developers to develop on HEAD, 
and merge to 1.x as needed?  The Eclipse Merge Wizard should make this a snap.



--
Java/J2EE Developer/Integrator
Currently "On the Road"
214-724-7741


http://keelframework.org/documentation
Keelgroup mailing list
[EMAIL PROTECTED]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com

Reply via email to