On 7/26/06, Jason Carreira <[EMAIL PROTECTED]> wrote:
I understand that there are different ways to skin the cat, but what if I want to reuse my actions in different contexts? What if I want to call my action from a JBPM workflow? Do I need to subclass it to override the result that's returned?
It's my understanding that the current approach wouldn't go away. I'd prefer to stick to one approach, but if one approach can't meet everyone's needs... Then again, any new approach would have to provide a lot of value over the current approach. People keep talking about modeling results using annotations, but I've yet to see an approach I like. I'm perfectly aware that my "abstract result method" suggestion is a bad idea, but it's the only decent annotation-based approach I can come up with, and I'm trying to get the conversation started and think outside the box. I don't understand this huge backlash against XML in the Java community. XML
has its place. XML is really good at representing hierarchical structured data. Building up that hierarchy in Java code isn't nearly as intuitive or understandable (to me). There's definitely ways to over-do it, but I think it's shifted too far back the other way.
I agree with this, but Spring still puts too much information in XML (and moving the configuration into Java in the way they've done is not the solution). XML is better than Java for declaration, but we should resist embedding too much logic. XML is a lot harder to debug and refactor than Java. :) Bob
