>
>
> - Also it looks like wicket  requires code changes when more pages are
> added
> and each page needs to have separate handler and it can not be done in
> configuration file. This may become an issue when number of pages increase
> in future.



what do you mean with this? You want to have the flow between pages in a xml
file?
Please explain to me how you want to do that exactly, i am always very
curious why
the web frameworks all really want this.

How do you see that you can just drop in a new page. And then configure an
xml file
and that page is suddenly the response page of 5 other pages (actions) ?
But what state does that new page get? Are all the pages that you show
completely stateless
they can construct themself from something and know what they must show and
what there context is?

So how do all the previous pages know exactly what context to set somewhere
that the new page wants?

Please if anybody could tell me how they can build an application with flow
where all the pages
don't really know anything of the next page of even what the next page
really is.

Is there 1 person on this list that made a struts or webflow application
like this that they can randomly
define flow and add pages without touching the existing code base?

johan

Reply via email to