----- Original Message ----- From: "Craig R. McClanahan" <[EMAIL PROTECTED]> To: "Struts Developers List" <[EMAIL PROTECTED]> Sent: Monday, October 06, 2003 7:25 PM Subject: Re: Struts-chain Behavior Discussion
> I actually think this is better, because you can customize *just* the B1 > path or *just* the B2 path if you want to, without having to mess with > MAIN at all. I believe people should use them as they see fit. Just like choosing inner classes or regular classes in an application, if you want to take advantage of surrounding environments, inner classes might be more suitable. Regular classes give you independent customization, like what you point out here. But I do not want to say which one is better without specific goals, because sometime people want to centralize logics and keep them in sync, instead of specifying Class4 in three different places. > UI workflows across requests are not what commons-chain is really for -- My message might not be that clear. I did not intend to use commons-chain for UI workflows across requests. I am considering to design UIs to construct chains. UIs' necessary attributes must be identified at first. The result chains will be used in application modules (in Struts). I did an estimation and found many use cases are just to jump to the last command. So I am asking the list if there is a direct "jump" for those simple use cases. > However, it's also feasible to build branches and labels in by subclass > CommandBase and ChainBase appropriately, instead of modify Command and > Chain. That would be the suggested way to prototype something. Yes. I need to look at CommandBase and ChainBase for possible extensions. Jing --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
