On the contrary the Web Application Controller is best used when you do not use Struts or JSF. It is designed to integrate smoothly with XForms. There is detailed information here:
http://www.orbeon.com/oxf/doc/processors-controller
I paste the first paragraphs of that page below:
"The OXF Web Application Controller is the heart of OXF-based Web applications. It maps incoming user requests to individual pages and defines how each page is built out of a model and a view, following the model-view-controller (MVC) architecture.
The Web Application Controller features an easy to use yet powerful workflow engine that allows developers to declare the entire site navigation logic. With a central place where the navigation logic is defined, pages can be developed completely independently from each other."
In addition to the WAC, you typically write, for each page, a model and / or a view. Those can be static XML files, XSLT stylesheets, or full-fledged XML pipelines.
Definitely, if you do not plan to use Struts or JSF, the WAC is the way to go.
-Erik
Hank Ratzesberger wrote: > seem to be over my first hurdle, and sorry to > make it such a burden to the list. This I hope > is a more useful discussion. > > Earlier, it was mentioned that the webapp-controller > processor is designed for integration with struts, etc., > but it seems to me that OXF is preferable to struts. > > On the other hand, the webapp-controller allows > you to configure what files are delivered directly and > easily map urls to pages. Also, if you are using xforms, > is there a sample that uses the pipeline processor? > > I am going to attempt to avoid JSP and JSF as far > as possible, should I use the webapp-controller anyway, > or does it matter? > > Thanks, > Hank
_______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
