Julien, Thank you. I did get the application to work once, but I am stuck again.
Following the directions of chapter 3.2 of the 2.02 reference, I believe I have set things up as described. Note: the reference describes changing the WebAppResourceManagerFactory to FlatFile... , but goes on to say (p.26) deploy myapp.war . Also, the sample helloworld.xpl line: <p:output name="data" ref="data"/> I changed to <p:output name="data" ref="#data"/> because every other example used the hash for local reference. I loaded the app using the Tomcat manager. On startup, it emits the same log message as the working OXF app. http://128.111.236.18:8080/nees/ -- just the tomcat servlet http://128.111.236.18:8080/oxf/ -- working great Below is my web.xml and the rest of the files are viewable through the app. What could I be doing wrong? --If you have the time, thanks, Hank <web-app> <!-- Initialize a resource manager --> <context-param> <param-name>oxf.resources.factory</param-name> <param-value>org.orbeon.oxf.resources.PriorityResourceManagerFactory</param- value> </context-param> <context-param> <param-name>oxf.resources.flatfile.rootdir</param-name> <param-value>/opt/jwsdp-1.2/webapps/nees</param-value> </context-param> <context-param> <param-name>oxf.resources.priority.1</param-name> <param-value>org.orbeon.oxf.resources.FlatFileResourceManagerFactory</param- value> </context-param> <context-param> <param-name>oxf.resources.priority.2</param-name> <param-value>org.orbeon.oxf.resources.ClassLoaderResourceManagerFactory</par am-value> </context-param> <!-- Set location of properties.xml (read by resource manager) --> <context-param> <param-name>oxf.properties</param-name> <param-value>oxf:/config/properties.xml</param-value> </context-param> <listener> <listener-class>org.orbeon.oxf.servlet.ProcessorServletContextListener</list ener-class> </listener> <servlet> <servlet-name>oxf</servlet-name> <servlet-class>org.orbeon.oxf.servlet.ProcessorServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>oxf</servlet-name> <url-pattern>/</url-pattern> </servlet-mapping> </web-app> ----- Original Message ----- From: "Julien Mercay" <[EMAIL PROTECTED]> To: "OXF Users" <[EMAIL PROTECTED]> Sent: Thursday, August 28, 2003 4:56 PM Subject: Re: First app. file set > Hi Hank, > > This exception typically occurs when the WebApp Controller can't find > the requested page, and no error page is declared. Make sure you > access the right page in your application. Your controller declares a > "/" page, relative to the context path. You should therefore access > this page with a URL similar to the following: > > http://localhost:8080/oxf/ > > assuming "oxf" is the context path. The trailing "/" refers to the > controller entry. > > You can also declare a not-found page in the <view> element of > controller.xml. The following would display the notfound.xml page with > a 404 HTTP error code when you access a wrong URL. > > <view not-found="oxf:/config/notfound.xml"/> > > > Examining your file, I noticed that your view pipeline contains an > error. You instantiate the webapp-controller, but you are trying to > display a simple HTML page. The webapp-controller is a dispatcher > similar to the Struts controller servlet. > > You have multiple ways to achieve what you want: > > 1) Use the identity processor. Change your pipeline to match the > following. The identity processor mirrors its data input to its data > output. > > <p:config xmlns:p="http://www.orbeon.com/oxf/pipeline";> > <p:param type="output" name="data"/> > <p:processor uri="oxf/processor/identity"> > <p:input name="data"> > <html> > <body>Hello, World!</body> > </html> > </p:input> > <p:output name="data" ref="data"/> > </p:processor> > </p:config> > > > 2) Use a plain XML file. The webapp controller supports shortcuts: you > can simply rewrite the above pipeline as an XML file. OXF internally > uses an identity processor like in option 1. The same applies to XSLT > stylesheet. > > <html> > <body>Hello, World!</body> > </html> > > > To answer your last question, there is no default pipeline, init, or > epilogue in OXF. The init and the main pipeline are declared in > properties.xml (referenced from web.xml). The epilogue is declared in > controller.xml, and is optional (like in your example). > > Hope this helps, > Julien > > Hank Ratzesberger wrote: > > > Julien, > > > > Thank you. I would be happy to go the WAR file route > > if that's what you recommend. I was trying the > > "from scratch" just to check that I really understand > > what I am doing. If it's not a lot of your time, everything > > else seems to be right as far as loading the servlet > > and initializing the resources, but I get this exception: > > > > Condition failed for every branch of choose: [(/request/request-path = '/')] > > at > > org.orbeon.oxf.processor.pipeline.ChooseProcessor$ConcreteChooseProcessor.st > > art(ChooseProcessor.java:375 > > > > I have the following files: > > > > /helloworld.xpl > > /config/controller.xml > > /config/licence.xml > > /config/log4j.xml > > /config/properties.xml > > > > as well as the libraries and web.xml (tomcat 4) config file. > > > > So, I think it just boils down to my properties.xml file: > > > > <properties> > > <property type="string" name="oxf.license" > > value="oxf:/config/license.xml"/> > > <property type="string" name="oxf.servlet.log4j" > > value="oxf:/config/log4j.xml"/> > > <property type="integer" name="oxf.cache.size" > > value="200"/> > > <property type="string" name="oxf.xslt.transformer" > > value="interpreter"/> > > <property type="boolean" name="oxf.validation.processor" > > value="true"/> > > <property type="boolean" name="oxf.validation.user" > > value="true"/> > > <property type="boolean" name="oxf.validation.xforms" > > value="true"/> > > <property type="string" name="oxf.servlet.processor" > > value="oxf/processor/webapp-controller"/> > > <property type="string" name="oxf.servlet.input.controller" > > value="oxf:/config/controller.xml"/> > > <property type="string" name="oxf.java.jarpath" > > value="M:/OXF/lib;M:/OXF/lib/cli"/> > > </properties> > > > > > > My controller.xml file: > > > > <config xmlns="http://www.orbeon.com/oxf/controller"; > > xmlns:xu="http://www.xmldb.org/xupdate";> > > <page path-info="/" view="oxf:/helloworld.xpl"/> > > </config> > > > > and the view file: > > > > <p:config xmlns:p="http://www.orbeon.com/oxf/pipeline";> > > <p:param type="output" name="data"/> > > <p:processor uri="oxf/processor/webapp-controller"> > > <p:input name="data"> > > <html> > > <body>Hello, World!</body> > > </html> > > </p:input> > > <p:output name="data" ref="data"/> > > </p:processor> > > </p:config> > > > > I was under the impression that there is a default init, epilogue > > etc., pipelines, unless overridden. > > > > Many thanks, > > Hank > > > > > > ----- Original Message ----- > > From: "Julien Mercay" <[EMAIL PROTECTED]> > > To: "OXF Users" <[EMAIL PROTECTED]> > > Sent: Thursday, August 28, 2003 3:55 PM > > Subject: Re: First app. file set > > > > > > > >>Hi Hank, > >> > >>The easiest way to get up to speed with OXF is to modify the > >>distribution WAR file. If you decide to start over and create your own > >>WAR file, the following directories should be copied in a similar > >>location: > >> > >>WEB-INF/resources/config > >> (contains the OXF startup files, and the epilogue) > >> > >>WEB-INF/resources/oxf-theme > >> (contains the default theme, called from the epilogue. Feel free to > >> modify or replace these files) > >> > >>If you still experience errors, please send me the first exception > >>displayed in the browser, or in the Tomcat console. > >> > >>Regards, > >>Julien > >> > >>Hank Ratzesberger wrote: > >> > >> > >>>I am having a few problems setting up my first application > >>>by copying the files from the oxf.war file. > >>> > >>>The init.xpl, error.xpl, etc., reference "oxf-theme" files. > >>> > >>>I am not sure where my errors end and the errors they trigger > >>>begin. > >>> > >>>In any case, thanks. > >>> > >>>--Hank > >>> > >>>============================================ > >>>Replying to a list? I'll get my copy there! > >>> > >>>Hank Ratzesberger > >>>http://crustal.ucsb.edu/ | http://neesgrid.org/ > >>>Institute for Crustal Studies > >>>University of California, Santa Barbara > >>>============================================ > >>>_______________________________________________ > >>>oxf-users mailing list > >>>[EMAIL PROTECTED] > >>>http://mail.orbeon.com/mailman/listinfo/oxf-users > >> > >> > >>_______________________________________________ > >>oxf-users mailing list > >>[EMAIL PROTECTED] > >>http://mail.orbeon.com/mailman/listinfo/oxf-users > >> > > > > > > _______________________________________________ > > oxf-users mailing list > > [EMAIL PROTECTED] > > http://mail.orbeon.com/mailman/listinfo/oxf-users > > > _______________________________________________ > oxf-users mailing list > [EMAIL PROTECTED] > http://mail.orbeon.com/mailman/listinfo/oxf-users > _______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
