The idea fell out of creating high level use cases for my actions. In each
use case I first listed all the conditions that must be true before any
processing could take place, then form validation conditions, then the
expected post processing conditions that must be true in order to forward to
the next logical sequence.

-Action
  - Preprocessing Assertions:
  - User Input Assertions:
  - Processing Assertions:

  - Process:

  - Success:
    - Forward to ....

  - Failure:
    - Preprocessing Assertions:
      - Forward to ...
    - User Input Assertions:
      - Forward to ....
    - Processing Assertions:
      - Forward to

Now with the new exception handling in 1.1b, I can add

  - Exceptions:
    - Forward to ...


I can then reference this when creating the struts-config or when I design
the classes.


robert


> -----Original Message-----
> From: Jennings, Christofer J. [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 06, 2002 11:52 AM
> To: 'Struts Users Mailing List'
> Subject: RE: Assertions
>
>
> Very good reasons! I'd sure like to see this feature supported as you
> describe.
> It might also be nice to have global asserts for things like user
> authentication/authorization.
>
> -----Original Message-----
> From: Robert Taylor [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 06, 2002 8:07 AM
> To: Struts Users Mailing List
> Subject: RE: Assertions
>
>
> Yep, that may be the approach I take although it circumvents the front
> controller. Not necessarily a bad thing. It just disperses business logic,
> configuratin, and, in event that the assertion fails, navigation logic. It
> would be nice to have this all reside within the front controller and
> configurable via one source (the struts-config file).
>
> robert
>
>
>
> > -----Original Message-----
> > From: Jennings, Christofer J. [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, June 06, 2002 10:26 AM
> > To: 'Struts Users Mailing List'
> > Subject: RE: Assertions
> >
> >
> > How about using filters?
>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to