Web flow is ok, but I would prefer if Enums would be used for it, it instead of strings (they're easily mapped from string and back)
Every enum is a type for it self and as such a handler can be attached to each, unlike the string: where we have only one shot to choose the right (natural) one. I've recently created a small state machine for a complicated processing to break it into managable parts. Defining a state machine using Enums was no more complicated than defining in a some xml, but felt a lot more natural and Java like. (and I could use autocomplete as well :):) ) Davor Hrg On 6/9/07, Massimo Lusetti <[EMAIL PROTECTED]> wrote:
On 6/8/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > That's a good point ... should we just get rid of String response? By my point of view... yes. > I'm not certain; there may be some cases (such as the forthcoming > Spring Web Flow integration) where strings would be more > useful/convienient than Class instances. Actually i don't know about Spring Web Flow (never used) but besides that i don't see any reason why not to remove it now. Class return type is more safe then String. -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
