Joe Germuska wrote:
I wrote:
Yes... I'm sorry that that discussion has stalled. Although I don't even know if that's an incremental step towards a POJO action -- it's practically all you need, plus a little more smarts in the CreateAction command. I'll go post a ping.
OK, so I actually started looking at using POJOs for Actions, and it's a bit trickier than I'd thought, but I may want to use it on a current project, so if people want to talk about it, there's a chance I'll get it into Struts 1.3 sooner than later...
Sorry for Chiming in on this late.
In our web application which we inherited from another company they used nakedobjects(Google it) to create a generic framework that supposedly isolates the business objects from both the upper and lower tear, which is only one small part of nakedobjects capabilities.
In theory it sounds like a silver bullet, but in our real working system it has been a real headache in maintaining and tracking down bugs (Like data loss under load) since it does allot of work under the covers.
The original developers of the web app I am told contributed heavily to the nakedobjects code base so they should have know how to use the library, assuming it was the right pattern at the right time.
<rant>
The original developers of the web app also rolled their own supposedly MVC framework, workflow system, and XML parser. It is the most tightly coupled/fragile system I have worked with. The saying 'Too smart by half' really applies there.
I really miss Struts.
</rant>
My point is if new approach is taken towards Actions that it should be easily understood by reading code, easy to debug, and easy to maintain for the users of the Framework.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
