Jing Zhou wrote:
I am wondering how I could implement a jump behavior in the main
chain. The use case for a jump behavior is that the main chain should
continue with several commands skipped over. For example, I would like
to jump to the last command in the main chain after the current command.
- Original Message -
From: Craig R. McClanahan [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Sent: Wednesday, October 01, 2003 11:24 AM
Subject: Re: [struts-chain] Writing a command to process a Tiles Definition
There's a conditional behavior use case in the existing
Jing Zhou wrote:
- Original Message -
From: Craig R. McClanahan [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Sent: Wednesday, October 01, 2003 11:24 AM
Subject: Re: [struts-chain] Writing a command to process a Tiles Definition
There's a conditional behavior use
snip
Didn't your O-O programming classes explain to you the evils of the
goto statement? :-)
/snip
Of course everyone knows gotos are naughty.
Thats why programming languages nowdays market them under the much
friendlier sounding terms break and continue. ;-
-Original Message-
From:
Greg Reddin wrote:
I'm trying to write a Command or set of Commands that will process a
Tiles definition to help complete the 1.x-compatible chained request
processor. I've got something working, but I would like some
community input before I submit it.
First, I created another subclass of
There's a conditional behavior use case in the existing code as well;
when validation fails, we want to redisplay the input form. Originally,
I modelled this command as a Chain that conditionally executed its child
commands, but that seemed a little hokey. Now, this command definition
says:
Greg Reddin wrote:
There's a conditional behavior use case in the existing code as
well; when validation fails, we want to redisplay the input form.
Originally, I modelled this command as a Chain that conditionally
executed its child commands, but that seemed a little hokey. Now,
this
I've found that experimenting has worked a lot better once I started
doing it in the open :-).
Point taken :-) Here's what I have so far, most definitely to be
changed sometime soon.
Greg
/*
* $Header:
