> > Oh please no... please no abstract methods with > magic implementations. What happens when you go to > debug the class? > > The debugger would step from your action into the > result. You rave > about Hibernate and AOP; how do you debug those? >
It's one of the biggest problems with them. Well, not so much Hibernate 'cause I don't find myself in stack traces with Hibernate proxies in the middle, but AOP interceptor / proxies are in there all the time and it's a pain. At least there they are wrapping my implementation, so I can see where my code was and get to it. The AOP interceptor code can also be stepped into. In this case you'd have magically runtime-created classes with implementations that aren't backed by any source code. > If you get an exception in your result, the action > that led to it will > be in the stack trace; that's more than you can say > about the current > state of affairs. How often do you get an exception in the result that isn't some obscure FM template issue? Seems like a non-issue to me. > > Some people want a simpler, more or less flexible > approach in addition > to the current one, and there's nothing wrong with > that; I was just > responding with some brainstorming. Feel free to > throw out better > ideas. > > Bob > Let's just not take away from what we have to chase some "agile" manifesto that hasn't proven itself in production. Rails is nifty and all, but the stuff I've seen built with it isn't exactly rocket science. --------------------------------------------------------------------- Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=38338&messageID=75939#75939 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
