struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nestel, Frank" <>
Subject AW: Struts limitation?
Date Wed, 14 Jun 2000 15:07:58 GMT

sounds fairly similar to what i wanted to suggest in my last,
probably to long posting. I'm not sure whether you could keep
that hierarchical structure since true web applications are more
like a graph than like a hierarchy (this might be different with
certain very special cases like surveys or multiple choice stuff).
To illustrate that on the most elementary example:
		-> signon
		-> logon
		-> explanations_signon
		-> login (for those how suddenly remember their pwd)
		-> welcome (this is kind of a back button)
		-> signon
		-> explanations_login
		-> signon (in case you are not signed on yet)
		-> authenticator
		-> user_page
		-> login (retry)

This cannot easily be flattened in the structure you suggested below
(maybe it was only meant as a simplified sample).

But the idea would be to augment every node (=page) not only with
actions and beans, but also with a named list of destination nodes,
where to go next. In fact Craig already started that with his
registration example, but I'd rather like it in a system. I'd also
like to have a special tag so I can jump to such a named destination
from within the corresponding JSP, so that I can replace pages, by
simply editing the action.xml

stop, to long again


> -----Urspr√ľngliche Nachricht-----
> Von: Rick Goeltz []
> Gesendet am: Mittwoch, 14. Juni 2000 16:29
> An:
> Betreff: RE: Struts limitation?
> "Lisa Woodring (EUS)" <> wrote:
> >One idea we had was to create an XML representation of the pages
> >         (it would define the page names and which 
> parameters are on each
> >         page,
> This is exactly what I am working on:
> survey
>    page1
>      question1
>         answer1
>         answer2
>      question2
> Thought I would use JDOM to handle the xml document.  Just 
> getting started; 
> suggestions welcome.
> Rick

View raw message