Integratin Orbeon Forms Into JSF Application
Locked
 
|
Hi folks,
I'm trying to get the example application "bookcast" to run in my existing JSF application. What I have done so far is: * I copied all JARs from Orbeon Forms' WEB-INF/lib folder to the same folder of my JSF application. * I copied the 'config' folder from Orbeon Forms' WEB-INF/resources folder to my JSF application's WEB-INF/config folder. * I copied the sample application "bookcast" to the root folder of my JSF application. * I added the following entries to my JSF application's 'web.xml' file: <filter> <filter-name>ops-main-filter</filter-name> <filter-class>org.orbeon.oxf.servlet.OPSServletFilter</filter-class> <init-param> <param-name>oxf.main-processor.name</param-name> <param-value>{http://www.orbeon.com/oxf/processors}pipeline</param-value> </init-param> <init-param> <param-name>oxf.main-processor.input.config</param-name> <param-value>oxf:/config/filter.xpl</param-value> </init-param> <init-param> <param-name>oxf.error-processor.name</param-name> <param-value>{http://www.orbeon.com/oxf/processors}pipeline</param-value> </init-param> <init-param> <param-name>oxf.error-processor.input.config</param-name> <param-value>oxf:/config/error.xpl</param-value> </init-param> </filter> <filter-mapping> <filter-name>ops-main-filter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> This is more or less how it is described at http://www.orbeon.com/ops/doc/integration-xforms-jsp. When I then started Tomcat, the error log said: 2007-04-03 16:03:36 StandardContext[/myapp]Exception starting filter ops-main-filter javax.servlet.ServletException: Declaration of resource factory missing: no value declared for property 'oxf.resources.factory' at org.orbeon.oxf.servlet.OPSServletFilter.init(OPSServletFilter.java:54) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:225) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:79) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4349) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) at org.apache.catalina.core.StandardHost.start(StandardHost.java:789) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) at org.apache.catalina.core.StandardService.start(StandardService.java:480) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) at org.apache.catalina.startup.Catalina.start(Catalina.java:556) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) ----- Root Cause ----- javax.servlet.ServletException: Declaration of resource factory missing: no value declared for property 'oxf.resources.factory' at org.orbeon.oxf.servlet.OPSServletFilterDelegate.init(OPSServletFilterDelegate.java:83) at org.orbeon.oxf.servlet.OPSServletFilter.init(OPSServletFilter.java:49) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:225) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:79) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4349) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) at org.apache.catalina.core.StandardHost.start(StandardHost.java:789) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) at org.apache.catalina.core.StandardService.start(StandardService.java:480) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) at org.apache.catalina.startup.Catalina.start(Catalina.java:556) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) So the first thing to notice is, the documentation seems to be insufficient, respectively too imprecise. Well, so I also copied the following entries to my JSF application's 'web.xml' file: <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.priority.1</param-name> <param-value>org.orbeon.oxf.resources.WebAppResourceManagerFactory</param-value> </context-param> <context-param> <param-name>oxf.resources.priority.1.oxf.resources.webapp.rootdir</param-name> <param-value>/WEB-INF</param-value> </context-param> <context-param> <param-name>oxf.classloader.enable</param-name> <param-value>false</param-value> </context-param> <context-param> <param-name>oxf.classloader.ignore-packages</param-name> <param-value>java. javax. org.apache.log4j. org.xml. org.w3c.</param-value> </context-param> <context-param> <param-name>oxf.properties</param-name> <param-value>oxf:/config/properties.xml</param-value> </context-param> <context-param> <param-name>oxf.initialize-logging</param-name> <param-value>true</param-value> </context-param> Trying to start Tomcat afterwards, causes the following error log: Initializing Resource Manager with: {org.orbeon.oxf.resources.WebAppResourceManagerImplServletContext=org.apache.catalina.core.ApplicationContextFacade@1c6bbd3, oxf.resources.priority.2=org.orbeon.oxf.resources.ClassLoaderResourceManagerFactory, oxf.resources.factory=org.orbeon.oxf.resources.PriorityResourceManagerFactory, oxf.resources.priority.1.oxf.resources.webapp.rootdir=/WEB-INF/resources, oxf.resources.priority.1=org.orbeon.oxf.resources.WebAppResourceManagerFactory} log4j:ERROR exception setting timeout, shutting down server socket. java.net.BindException: Address already in use: JVM_Bind at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331) at java.net.ServerSocket.bind(ServerSocket.java:318) at java.net.ServerSocket.<init>(ServerSocket.java:185) at java.net.ServerSocket.<init>(ServerSocket.java:97) at org.apache.log4j.net.SocketHubAppender$ServerMonitor.run(SocketHubAppender.java:348) at java.lang.Thread.run(Thread.java:534) So I turned logging off, by setting 'oxf.initialize-logging' to false. And now when I try to start Tomcat, I still get the following error log, and Tomcat does not start up successfully: 2007-04-03 16:44:53 StandardContext[/myapp] Exception starting filter ops-main-filter javax.servlet.ServletException: Cannot load "/org/orbeon/oxf/xml/schemas/processor-registry.rng" with webapp loader at org.orbeon.oxf.servlet.OPSServletFilter.init(OPSServletFilter.java:54) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:225) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:79) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4349) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) at org.apache.catalina.core.StandardHost.start(StandardHost.java:789) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) at org.apache.catalina.core.StandardService.start(StandardService.java:480) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) at org.apache.catalina.startup.Catalina.start(Catalina.java:556) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) ----- Root Cause ----- javax.servlet.ServletException: Cannot load "/org/orbeon/oxf/xml/schemas/processor-registry.rng" with webapp loader at org.orbeon.oxf.servlet.OPSServletFilterDelegate.init(OPSServletFilterDelegate.java:83) at org.orbeon.oxf.servlet.OPSServletFilter.init(OPSServletFilter.java:49) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:225) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:79) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4349) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) at org.apache.catalina.core.StandardHost.start(StandardHost.java:789) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) at org.apache.catalina.core.StandardService.start(StandardService.java:480) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) at org.apache.catalina.startup.Catalina.start(Catalina.java:556) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) So this seems as if the Orbeon Forms servlet filter is not able to load the 'processor-registry.rng' from the 'ops.jar', although it is available in the WEB-INF/lib folder of my application. But I do not know why and hope that I can get some help here to solve that problem. By the way, I tried this all with Tomcat 5.0.28 and Orbeon Forms 3.5. Cheers, bitbyter -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
|
|
Hi there,
is there maybe anyone who could help me, integrating Orbeon Forms into my JSF application? I really would appreciate any help. I tried all that came into my mind to get the things running. I even downloaded the source tarball and debugged the stuff. But as the source seems to be out of sync with the source in the jars, I wasn't really successfull. All I was able to find out is that the method call "WebAppContext.instance(servletContext)" in the init method of the class OPSServletFilterDelegate throws an exception. All I want to do, is get Orbeon Forms to generate (x)html/ajax stuff out of XForms elements, so that there is no need to install any plugins or extension on the client/browser. Not more, not less. :) Is there maybe somebody that is using Orbeon Froms already in his JSF application? The way as described in http://www.orbeon.com/ops/doc/integration-xforms-jsp unfortunately does not work for me. :( Anyone who might help? Cheers, bitbyter Tuesday, April 3, 2007, 5:02:30 PM, you wrote: > Hi folks, > I'm trying to get the example application "bookcast" to run in my existing > JSF application. What I have done so far is: > * I copied all JARs from Orbeon Forms' WEB-INF/lib folder to the same folder > of my JSF application. > * I copied the 'config' folder from Orbeon Forms' WEB-INF/resources folder > to my JSF application's WEB-INF/config folder. > * I copied the sample application "bookcast" to the root folder of my JSF > application. > * I added the following entries to my JSF application's 'web.xml' file: > <filter> > <filter-name>ops-main-filter</filter-name> > <filter-class>org.orbeon.oxf.servlet.OPSServletFilter</filter-class> > <init-param> > <param-name>oxf.main-processor.name</param-name> > > <param-value>{http://www.orbeon.com/oxf/processors}pipeline</param-value> > </init-param> > <init-param> > <param-name>oxf.main-processor.input.config</param-name> > <param-value>oxf:/config/filter.xpl</param-value> > </init-param> > <init-param> > <param-name>oxf.error-processor.name</param-name> > > <param-value>{http://www.orbeon.com/oxf/processors}pipeline</param-value> > </init-param> > <init-param> > <param-name>oxf.error-processor.input.config</param-name> > <param-value>oxf:/config/error.xpl</param-value> > </init-param> > </filter> > <filter-mapping> > <filter-name>ops-main-filter</filter-name> > <url-pattern>/*</url-pattern> > </filter-mapping> > This is more or less how it is described at > http://www.orbeon.com/ops/doc/integration-xforms-jsp. > When I then started Tomcat, the error log said: > 2007-04-03 16:03:36 StandardContext[/myapp]Exception starting filter ops-main-filter > javax.servlet.ServletException: Declaration of resource factory missing: > no value declared for property 'oxf.resources.factory' > at > org.orbeon.oxf.servlet.OPSServletFilter.init(OPSServletFilter.java:54) > at > org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:225) > at > org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) > at > org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:79) > at > org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4349) > at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) > at > org.apache.catalina.core.StandardHost.start(StandardHost.java:789) > at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) > at > org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) > at > org.apache.catalina.core.StandardService.start(StandardService.java:480) > at > org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) > at org.apache.catalina.startup.Catalina.start(Catalina.java:556) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287) > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) > ----- Root Cause ----- > javax.servlet.ServletException: Declaration of resource factory missing: > no value declared for property 'oxf.resources.factory' > at > org.orbeon.oxf.servlet.OPSServletFilterDelegate.init(OPSServletFilterDelegate.java:83) > at > org.orbeon.oxf.servlet.OPSServletFilter.init(OPSServletFilter.java:49) > at > org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:225) > at > org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) > at > org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:79) > at > org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4349) > at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) > at > org.apache.catalina.core.StandardHost.start(StandardHost.java:789) > at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) > at > org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) > at > org.apache.catalina.core.StandardService.start(StandardService.java:480) > at > org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) > at org.apache.catalina.startup.Catalina.start(Catalina.java:556) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287) > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) > So the first thing to notice is, the documentation seems to be insufficient, > respectively too imprecise. Well, so I also copied the following entries to my JSF application's > 'web.xml' file: > <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.priority.1</param-name> > > <param-value>org.orbeon.oxf.resources.WebAppResourceManagerFactory</param-value> > </context-param> > <context-param> > > <param-name>oxf.resources.priority.1.oxf.resources.webapp.rootdir</param-name> > <param-value>/WEB-INF</param-value> > </context-param> > <context-param> > <param-name>oxf.classloader.enable</param-name> > <param-value>false</param-value> > </context-param> > <context-param> > <param-name>oxf.classloader.ignore-packages</param-name> > <param-value>java. javax. org.apache.log4j. org.xml. org.w3c.</param-value> > </context-param> > <context-param> > <param-name>oxf.properties</param-name> > <param-value>oxf:/config/properties.xml</param-value> > </context-param> > <context-param> > <param-name>oxf.initialize-logging</param-name> > <param-value>true</param-value> > </context-param> > Trying to start Tomcat afterwards, causes the following error log: > Initializing Resource Manager with: > {org.orbeon.oxf.resources.WebAppResourceManagerImplServletContext=org.apache.catalina.core.ApplicationContextFacade@1c6bbd3, > oxf.resources.priority.2=org.orbeon.oxf.resources.ClassLoaderResourceManagerFactory, > oxf.resources.factory=org.orbeon.oxf.resources.PriorityResourceManagerFactory, > oxf.resources.priority.1.oxf.resources.webapp.rootdir=/WEB-INF/resources, > oxf.resources.priority.1=org.orbeon.oxf.resources.WebAppResourceManagerFactory} > log4j:ERROR exception setting timeout, shutting down server socket. > java.net.BindException: Address already in use: JVM_Bind > at java.net.PlainSocketImpl.socketBind(Native Method) > at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331) > at java.net.ServerSocket.bind(ServerSocket.java:318) > at java.net.ServerSocket.<init>(ServerSocket.java:185) > at java.net.ServerSocket.<init>(ServerSocket.java:97) > at > org.apache.log4j.net.SocketHubAppender$ServerMonitor.run(SocketHubAppender.java:348) > at java.lang.Thread.run(Thread.java:534) > So I turned logging off, by setting 'oxf.initialize-logging' to false. And > now when I try to start Tomcat, I still get the following error log, and > Tomcat does not start up successfully: > 2007-04-03 16:44:53 StandardContext[/myapp] Exception starting filter ops-main-filter > javax.servlet.ServletException: Cannot load > "/org/orbeon/oxf/xml/schemas/processor-registry.rng" with webapp loader > at > org.orbeon.oxf.servlet.OPSServletFilter.init(OPSServletFilter.java:54) > at > org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:225) > at > org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) > at > org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:79) > at > org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4349) > at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) > at > org.apache.catalina.core.StandardHost.start(StandardHost.java:789) > at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) > at > org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) > at > org.apache.catalina.core.StandardService.start(StandardService.java:480) > at > org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) > at org.apache.catalina.startup.Catalina.start(Catalina.java:556) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287) > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) > ----- Root Cause ----- > javax.servlet.ServletException: Cannot load > "/org/orbeon/oxf/xml/schemas/processor-registry.rng" with webapp loader > at > org.orbeon.oxf.servlet.OPSServletFilterDelegate.init(OPSServletFilterDelegate.java:83) > at > org.orbeon.oxf.servlet.OPSServletFilter.init(OPSServletFilter.java:49) > at > org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:225) > at > org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) > at > org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:79) > at > org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4349) > at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) > at > org.apache.catalina.core.StandardHost.start(StandardHost.java:789) > at > org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) > at > org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) > at > org.apache.catalina.core.StandardService.start(StandardService.java:480) > at > org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) > at org.apache.catalina.startup.Catalina.start(Catalina.java:556) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287) > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) > So this seems as if the Orbeon Forms servlet filter is not able to load the > 'processor-registry.rng' from the 'ops.jar', although it is available in the > WEB-INF/lib folder of my application. But I do not know why and hope that I > can get some help here to solve that problem. By the way, I tried this all > with Tomcat 5.0.28 and Orbeon Forms 3.5. > Cheers, > bitbyter -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Re: Integratin Orbeon Forms Into JSF Application
|
Administrator
|
Bitbyter,
We have new code committed which provides a much better way of deploying Orbeon Forms with Java applications. The new documentation about this is here: http://www.orbeon.com/ops/doc/reference-xforms-java For this to work, you will need a nightly build: http://forge.objectweb.org/nightlybuilds/ops/ops/ The intent of this is smooth deployment, no JAR conflicts, easier upgrades, and certainly no debugging of Orbeon Forms needed! Please let us know if this helps you! -Erik BitByter wrote: > Hi there, > > is there maybe anyone who could help me, integrating Orbeon Forms into my > JSF application? I really would appreciate any help. > > I tried all that came into my mind to get the things running. I even > downloaded the source tarball and debugged the stuff. But as the source > seems to be out of sync with the source in the jars, I wasn't really > successfull. All I was able to find out is that the method call > "WebAppContext.instance(servletContext)" in the init method of the class > OPSServletFilterDelegate throws an exception. > > All I want to do, is get Orbeon Forms to generate (x)html/ajax stuff out of > XForms elements, so that there is no need to install any plugins or > extension on the client/browser. Not more, not less. :) > > Is there maybe somebody that is using Orbeon Froms already in his JSF > application? The way as described in > http://www.orbeon.com/ops/doc/integration-xforms-jsp unfortunately does not > work for me. :( > > Anyone who might help? > > Cheers, > bitbyter > > > > Tuesday, April 3, 2007, 5:02:30 PM, you wrote: > >> Hi folks, > >> I'm trying to get the example application "bookcast" to run in my existing >> JSF application. What I have done so far is: > >> * I copied all JARs from Orbeon Forms' WEB-INF/lib folder to the same folder >> of my JSF application. > >> * I copied the 'config' folder from Orbeon Forms' WEB-INF/resources folder >> to my JSF application's WEB-INF/config folder. > >> * I copied the sample application "bookcast" to the root folder of my JSF >> application. > >> * I added the following entries to my JSF application's 'web.xml' file: > >> <filter> >> <filter-name>ops-main-filter</filter-name> >> <filter-class>org.orbeon.oxf.servlet.OPSServletFilter</filter-class> >> <init-param> >> <param-name>oxf.main-processor.name</param-name> >> >> <param-value>{http://www.orbeon.com/oxf/processors}pipeline</param-value> >> </init-param> >> <init-param> >> <param-name>oxf.main-processor.input.config</param-name> >> <param-value>oxf:/config/filter.xpl</param-value> >> </init-param> >> <init-param> >> <param-name>oxf.error-processor.name</param-name> >> >> <param-value>{http://www.orbeon.com/oxf/processors}pipeline</param-value> >> </init-param> >> <init-param> >> <param-name>oxf.error-processor.input.config</param-name> >> <param-value>oxf:/config/error.xpl</param-value> >> </init-param> >> </filter> >> <filter-mapping> >> <filter-name>ops-main-filter</filter-name> >> <url-pattern>/*</url-pattern> >> </filter-mapping> > > >> This is more or less how it is described at >> http://www.orbeon.com/ops/doc/integration-xforms-jsp. > >> When I then started Tomcat, the error log said: > >> 2007-04-03 16:03:36 StandardContext[/myapp]Exception starting filter ops-main-filter >> javax.servlet.ServletException: Declaration of resource factory missing: >> no value declared for property 'oxf.resources.factory' >> at >> org.orbeon.oxf.servlet.OPSServletFilter.init(OPSServletFilter.java:54) >> at >> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:225) >> at >> org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) >> at >> org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:79) >> at >> org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698) >> at >> org.apache.catalina.core.StandardContext.start(StandardContext.java:4349) >> at >> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) >> at >> org.apache.catalina.core.StandardHost.start(StandardHost.java:789) >> at >> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) >> at >> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) >> at >> org.apache.catalina.core.StandardService.start(StandardService.java:480) >> at >> org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) >> at org.apache.catalina.startup.Catalina.start(Catalina.java:556) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:324) >> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287) >> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) >> ----- Root Cause ----- >> javax.servlet.ServletException: Declaration of resource factory missing: >> no value declared for property 'oxf.resources.factory' >> at >> org.orbeon.oxf.servlet.OPSServletFilterDelegate.init(OPSServletFilterDelegate.java:83) >> at >> org.orbeon.oxf.servlet.OPSServletFilter.init(OPSServletFilter.java:49) >> at >> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:225) >> at >> org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) >> at >> org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:79) >> at >> org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698) >> at >> org.apache.catalina.core.StandardContext.start(StandardContext.java:4349) >> at >> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) >> at >> org.apache.catalina.core.StandardHost.start(StandardHost.java:789) >> at >> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) >> at >> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) >> at >> org.apache.catalina.core.StandardService.start(StandardService.java:480) >> at >> org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) >> at org.apache.catalina.startup.Catalina.start(Catalina.java:556) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:324) >> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287) >> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) > > > >> So the first thing to notice is, the documentation seems to be insufficient, >> respectively too imprecise. Well, so I also copied the following entries to my JSF application's >> 'web.xml' file: > >> <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.priority.1</param-name> >> >> <param-value>org.orbeon.oxf.resources.WebAppResourceManagerFactory</param-value> >> </context-param> >> <context-param> >> >> <param-name>oxf.resources.priority.1.oxf.resources.webapp.rootdir</param-name> >> <param-value>/WEB-INF</param-value> >> </context-param> >> <context-param> >> <param-name>oxf.classloader.enable</param-name> >> <param-value>false</param-value> >> </context-param> >> <context-param> >> <param-name>oxf.classloader.ignore-packages</param-name> >> <param-value>java. javax. org.apache.log4j. org.xml. org.w3c.</param-value> >> </context-param> >> <context-param> >> <param-name>oxf.properties</param-name> >> <param-value>oxf:/config/properties.xml</param-value> >> </context-param> >> <context-param> >> <param-name>oxf.initialize-logging</param-name> >> <param-value>true</param-value> >> </context-param> > > >> Trying to start Tomcat afterwards, causes the following error log: > >> Initializing Resource Manager with: >> {org.orbeon.oxf.resources.WebAppResourceManagerImplServletContext=org.apache.catalina.core.ApplicationContextFacade@1c6bbd3, >> oxf.resources.priority.2=org.orbeon.oxf.resources.ClassLoaderResourceManagerFactory, >> oxf.resources.factory=org.orbeon.oxf.resources.PriorityResourceManagerFactory, >> oxf.resources.priority.1.oxf.resources.webapp.rootdir=/WEB-INF/resources, >> oxf.resources.priority.1=org.orbeon.oxf.resources.WebAppResourceManagerFactory} >> log4j:ERROR exception setting timeout, shutting down server socket. >> java.net.BindException: Address already in use: JVM_Bind >> at java.net.PlainSocketImpl.socketBind(Native Method) >> at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331) >> at java.net.ServerSocket.bind(ServerSocket.java:318) >> at java.net.ServerSocket.<init>(ServerSocket.java:185) >> at java.net.ServerSocket.<init>(ServerSocket.java:97) >> at >> org.apache.log4j.net.SocketHubAppender$ServerMonitor.run(SocketHubAppender.java:348) >> at java.lang.Thread.run(Thread.java:534) > > >> So I turned logging off, by setting 'oxf.initialize-logging' to false. And >> now when I try to start Tomcat, I still get the following error log, and >> Tomcat does not start up successfully: > >> 2007-04-03 16:44:53 StandardContext[/myapp] Exception starting filter ops-main-filter >> javax.servlet.ServletException: Cannot load >> "/org/orbeon/oxf/xml/schemas/processor-registry.rng" with webapp loader >> at >> org.orbeon.oxf.servlet.OPSServletFilter.init(OPSServletFilter.java:54) >> at >> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:225) >> at >> org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) >> at >> org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:79) >> at >> org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698) >> at >> org.apache.catalina.core.StandardContext.start(StandardContext.java:4349) >> at >> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) >> at >> org.apache.catalina.core.StandardHost.start(StandardHost.java:789) >> at >> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) >> at >> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) >> at >> org.apache.catalina.core.StandardService.start(StandardService.java:480) >> at >> org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) >> at org.apache.catalina.startup.Catalina.start(Catalina.java:556) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:324) >> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287) >> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) >> ----- Root Cause ----- >> javax.servlet.ServletException: Cannot load >> "/org/orbeon/oxf/xml/schemas/processor-registry.rng" with webapp loader >> at >> org.orbeon.oxf.servlet.OPSServletFilterDelegate.init(OPSServletFilterDelegate.java:83) >> at >> org.orbeon.oxf.servlet.OPSServletFilter.init(OPSServletFilter.java:49) >> at >> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:225) >> at >> org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) >> at >> org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:79) >> at >> org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698) >> at >> org.apache.catalina.core.StandardContext.start(StandardContext.java:4349) >> at >> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) >> at >> org.apache.catalina.core.StandardHost.start(StandardHost.java:789) >> at >> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) >> at >> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) >> at >> org.apache.catalina.core.StandardService.start(StandardService.java:480) >> at >> org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) >> at org.apache.catalina.startup.Catalina.start(Catalina.java:556) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:324) >> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287) >> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) > > >> So this seems as if the Orbeon Forms servlet filter is not able to load the >> 'processor-registry.rng' from the 'ops.jar', although it is available in the >> WEB-INF/lib folder of my application. But I do not know why and hope that I >> can get some help here to solve that problem. By the way, I tried this all >> with Tomcat 5.0.28 and Orbeon Forms 3.5. > >> Cheers, >> bitbyter > > > > > > > -- Orbeon Forms - Web Forms for the Enterprise Done the Right Way http://www.orbeon.com/ -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
|
|
Hi Erik,
I've just read the mentioned documentation. My prefereable way of integrating OF is "integrated deployment". Unfortunately it only describes how to create a new web application with XForms using the ops.war as starting point. But for web applications that already have grown over time, like mine, this is not applicable. Anyway, I'll try to get it running with the new filter by copying the OF stuff into my web app. Ever thought about releasing two different versions of OF? One, the current Orbeon Forms, which probably is an web application framework. And a second version, only capble of XForms processing that could be used within other web frameworks. The last probably would be very interesting for people already using other web frameworks like Struts, JSF, Tapestry, etc. - bitbyter Thursday, April 5, 2007, 10:08:21 PM, you wrote: > Bitbyter, > We have new code committed which provides a much better way of deploying > Orbeon Forms with Java applications. The new documentation about this is > here: > http://www.orbeon.com/ops/doc/reference-xforms-java > For this to work, you will need a nightly build: > http://forge.objectweb.org/nightlybuilds/ops/ops/ > The intent of this is smooth deployment, no JAR conflicts, easier > upgrades, and certainly no debugging of Orbeon Forms needed! > Please let us know if this helps you! > -Erik > BitByter wrote: >> Hi there, >> >> is there maybe anyone who could help me, integrating Orbeon Forms into my >> JSF application? I really would appreciate any help. >> >> I tried all that came into my mind to get the things running. I even >> downloaded the source tarball and debugged the stuff. But as the source >> seems to be out of sync with the source in the jars, I wasn't really >> successfull. All I was able to find out is that the method call >> "WebAppContext.instance(servletContext)" in the init method of the class >> OPSServletFilterDelegate throws an exception. >> >> All I want to do, is get Orbeon Forms to generate (x)html/ajax stuff out of >> XForms elements, so that there is no need to install any plugins or >> extension on the client/browser. Not more, not less. :) >> >> Is there maybe somebody that is using Orbeon Froms already in his JSF >> application? The way as described in >> http://www.orbeon.com/ops/doc/integration-xforms-jsp unfortunately does not >> work for me. :( >> >> Anyone who might help? >> >> Cheers, >> bitbyter >> >> >> >> Tuesday, April 3, 2007, 5:02:30 PM, you wrote: >> >>> Hi folks, >> >>> I'm trying to get the example application "bookcast" to run in my existing >>> JSF application. What I have done so far is: >> >>> * I copied all JARs from Orbeon Forms' WEB-INF/lib folder to the same folder >>> of my JSF application. >> >>> * I copied the 'config' folder from Orbeon Forms' WEB-INF/resources folder >>> to my JSF application's WEB-INF/config folder. >> >>> * I copied the sample application "bookcast" to the root folder of my JSF >>> application. >> >>> * I added the following entries to my JSF application's 'web.xml' file: >> >>> <filter> >>> <filter-name>ops-main-filter</filter-name> >>> <filter-class>org.orbeon.oxf.servlet.OPSServletFilter</filter-class> >>> <init-param> >>> <param-name>oxf.main-processor.name</param-name> >>> >>> <param-value>{http://www.orbeon.com/oxf/processors}pipeline</param-value> >>> </init-param> >>> <init-param> >>> <param-name>oxf.main-processor.input.config</param-name> >>> <param-value>oxf:/config/filter.xpl</param-value> >>> </init-param> >>> <init-param> >>> <param-name>oxf.error-processor.name</param-name> >>> >>> <param-value>{http://www.orbeon.com/oxf/processors}pipeline</param-value> >>> </init-param> >>> <init-param> >>> <param-name>oxf.error-processor.input.config</param-name> >>> <param-value>oxf:/config/error.xpl</param-value> >>> </init-param> >>> </filter> >>> <filter-mapping> >>> <filter-name>ops-main-filter</filter-name> >>> <url-pattern>/*</url-pattern> >>> </filter-mapping> >> >> >>> This is more or less how it is described at >>> http://www.orbeon.com/ops/doc/integration-xforms-jsp. >> >>> When I then started Tomcat, the error log said: >> >>> 2007-04-03 16:03:36 StandardContext[/myapp]Exception starting filter ops-main-filter >>> javax.servlet.ServletException: Declaration of resource factory missing: >>> no value declared for property 'oxf.resources.factory' >>> at >>> org.orbeon.oxf.servlet.OPSServletFilter.init(OPSServletFilter.java:54) >>> at >>> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:225) >>> at >>> org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) >>> at >>> org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:79) >>> at >>> org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698) >>> at >>> org.apache.catalina.core.StandardContext.start(StandardContext.java:4349) >>> at >>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) >>> at >>> org.apache.catalina.core.StandardHost.start(StandardHost.java:789) >>> at >>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) >>> at >>> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) >>> at >>> org.apache.catalina.core.StandardService.start(StandardService.java:480) >>> at >>> org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) >>> at org.apache.catalina.startup.Catalina.start(Catalina.java:556) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>> at java.lang.reflect.Method.invoke(Method.java:324) >>> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287) >>> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) >>> ----- Root Cause ----- >>> javax.servlet.ServletException: Declaration of resource factory missing: >>> no value declared for property 'oxf.resources.factory' >>> at >>> org.orbeon.oxf.servlet.OPSServletFilterDelegate.init(OPSServletFilterDelegate.java:83) >>> at >>> org.orbeon.oxf.servlet.OPSServletFilter.init(OPSServletFilter.java:49) >>> at >>> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:225) >>> at >>> org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) >>> at >>> org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:79) >>> at >>> org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698) >>> at >>> org.apache.catalina.core.StandardContext.start(StandardContext.java:4349) >>> at >>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) >>> at >>> org.apache.catalina.core.StandardHost.start(StandardHost.java:789) >>> at >>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) >>> at >>> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) >>> at >>> org.apache.catalina.core.StandardService.start(StandardService.java:480) >>> at >>> org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) >>> at org.apache.catalina.startup.Catalina.start(Catalina.java:556) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>> at java.lang.reflect.Method.invoke(Method.java:324) >>> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287) >>> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) >> >> >> >>> So the first thing to notice is, the documentation seems to be insufficient, >>> respectively too imprecise. Well, so I also copied the following entries to my JSF application's >>> 'web.xml' file: >> >>> <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.priority.1</param-name> >>> >>> <param-value>org.orbeon.oxf.resources.WebAppResourceManagerFactory</param-value> >>> </context-param> >>> <context-param> >>> >>> <param-name>oxf.resources.priority.1.oxf.resources.webapp.rootdir</param-name> >>> <param-value>/WEB-INF</param-value> >>> </context-param> >>> <context-param> >>> <param-name>oxf.classloader.enable</param-name> >>> <param-value>false</param-value> >>> </context-param> >>> <context-param> >>> <param-name>oxf.classloader.ignore-packages</param-name> >>> <param-value>java. javax. org.apache.log4j. org.xml. org.w3c.</param-value> >>> </context-param> >>> <context-param> >>> <param-name>oxf.properties</param-name> >>> <param-value>oxf:/config/properties.xml</param-value> >>> </context-param> >>> <context-param> >>> <param-name>oxf.initialize-logging</param-name> >>> <param-value>true</param-value> >>> </context-param> >> >> >>> Trying to start Tomcat afterwards, causes the following error log: >> >>> Initializing Resource Manager with: >>> {org.orbeon.oxf.resources.WebAppResourceManagerImplServletContext=org.apache.catalina.core.ApplicationContextFacade@1c6bbd3, >>> oxf.resources.priority.2=org.orbeon.oxf.resources.ClassLoaderResourceManagerFactory, >>> oxf.resources.factory=org.orbeon.oxf.resources.PriorityResourceManagerFactory, >>> oxf.resources.priority.1.oxf.resources.webapp.rootdir=/WEB-INF/resources, >>> oxf.resources.priority.1=org.orbeon.oxf.resources.WebAppResourceManagerFactory} >>> log4j:ERROR exception setting timeout, shutting down server socket. >>> java.net.BindException: Address already in use: JVM_Bind >>> at java.net.PlainSocketImpl.socketBind(Native Method) >>> at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331) >>> at java.net.ServerSocket.bind(ServerSocket.java:318) >>> at java.net.ServerSocket.<init>(ServerSocket.java:185) >>> at java.net.ServerSocket.<init>(ServerSocket.java:97) >>> at >>> org.apache.log4j.net.SocketHubAppender$ServerMonitor.run(SocketHubAppender.java:348) >>> at java.lang.Thread.run(Thread.java:534) >> >> >>> So I turned logging off, by setting 'oxf.initialize-logging' to false. And >>> now when I try to start Tomcat, I still get the following error log, and >>> Tomcat does not start up successfully: >> >>> 2007-04-03 16:44:53 StandardContext[/myapp] Exception starting filter ops-main-filter >>> javax.servlet.ServletException: Cannot load >>> "/org/orbeon/oxf/xml/schemas/processor-registry.rng" with webapp loader >>> at >>> org.orbeon.oxf.servlet.OPSServletFilter.init(OPSServletFilter.java:54) >>> at >>> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:225) >>> at >>> org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) >>> at >>> org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:79) >>> at >>> org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698) >>> at >>> org.apache.catalina.core.StandardContext.start(StandardContext.java:4349) >>> at >>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) >>> at >>> org.apache.catalina.core.StandardHost.start(StandardHost.java:789) >>> at >>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) >>> at >>> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) >>> at >>> org.apache.catalina.core.StandardService.start(StandardService.java:480) >>> at >>> org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) >>> at org.apache.catalina.startup.Catalina.start(Catalina.java:556) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>> at java.lang.reflect.Method.invoke(Method.java:324) >>> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287) >>> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) >>> ----- Root Cause ----- >>> javax.servlet.ServletException: Cannot load >>> "/org/orbeon/oxf/xml/schemas/processor-registry.rng" with webapp loader >>> at >>> org.orbeon.oxf.servlet.OPSServletFilterDelegate.init(OPSServletFilterDelegate.java:83) >>> at >>> org.orbeon.oxf.servlet.OPSServletFilter.init(OPSServletFilter.java:49) >>> at >>> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:225) >>> at >>> org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) >>> at >>> org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:79) >>> at >>> org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698) >>> at >>> org.apache.catalina.core.StandardContext.start(StandardContext.java:4349) >>> at >>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) >>> at >>> org.apache.catalina.core.StandardHost.start(StandardHost.java:789) >>> at >>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) >>> at >>> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) >>> at >>> org.apache.catalina.core.StandardService.start(StandardService.java:480) >>> at >>> org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) >>> at org.apache.catalina.startup.Catalina.start(Catalina.java:556) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>> at java.lang.reflect.Method.invoke(Method.java:324) >>> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287) >>> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) >> >> >>> So this seems as if the Orbeon Forms servlet filter is not able to load the >>> 'processor-registry.rng' from the 'ops.jar', although it is available in the >>> WEB-INF/lib folder of my application. But I do not know why and hope that I >>> can get some help here to solve that problem. By the way, I tried this all >>> with Tomcat 5.0.28 and Orbeon Forms 3.5. >> >>> Cheers, >>> bitbyter >> >> -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Re: Integratin Orbeon Forms Into JSF Application
|
Administrator
|
BitByter,
> I've just read the mentioned documentation. My prefereable way of > integrating OF is "integrated deployment". Unfortunately it only describes > how to create a new web application with XForms using the ops.war as > starting point. But for web applications that already have grown over time, > like mine, this is not applicable. Anyway, I'll try to get it running with > the new filter by copying the OF stuff into my web app. > > Ever thought about releasing two different versions of OF? One, the current > Orbeon Forms, which probably is an web application framework. And a second > version, only capble of XForms processing that could be used within other > web frameworks. The last probably would be very interesting for people > already using other web frameworks like Struts, JSF, Tapestry, etc. version of Orbeon Forms. But we try avoid the "Microsoft Vista syndrome" and to minimize the number of different versions we have, that is, we would prefer to have just one. For example, having two versions means that you have two releases to test instead of one. Could you precise the reason why your preferred deployment option is the "integrated" one? The "separate" deployment option was designed explicitly as a solution to allow deployment of Orbeon Forms for "people already using other web frameworks like Struts, JSF, Tapestry, etc.". -Erik -- Orbeon Forms - Web Forms for the Enterprise Done the Right Way http://www.orbeon.com/ -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
|
|
Hello Erik,
Tuesday, April 10, 2007, 11:30:31 AM, you wrote: > That would be technically possible - we could call this the "minimal" > version of Orbeon Forms. But we try avoid the "Microsoft Vista syndrome" > and to minimize the number of different versions we have, that is, we > would prefer to have just one. For example, having two versions means > that you have two releases to test instead of one. Yes, I agree that this would be some more work to be done. :) > Could you precise the reason why your preferred deployment option is the > "integrated" one? The "separate" deployment option was designed > explicitly as a solution to allow deployment of Orbeon Forms for "people > already using other web frameworks like Struts, JSF, Tapestry, etc.". Well, I'm not familiar with cross context applications, but I assume that there are certain things like security/authentication or session handling that might get complicated. So for exmaple my XForm pages should only be available after previous user authentication/login. But I'd guess the XForm pages would be also accessible without prior login, if they are depolyed in a second, the ops.war application. Furthermore I'm also not sure if all web containers support cross context applications. My app for exmaple has to run on Weblogic 8, although I'm using Tomcat during the development. And as you already mentioned, having only one web app to maintain means less work, especially when updating an application in a clustered environment. :) - bitbyter -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Re: Integratin Orbeon Forms Into JSF Application
|
Administrator
|
BitByter,
Good remarks, and some things to add to the documentation. My comments below. >> Could you precise the reason why your preferred deployment option >> is the "integrated" one? The "separate" deployment option was >> designed explicitly as a solution to allow deployment of Orbeon >> Forms for "people already using other web frameworks like Struts, >> JSF, Tapestry, etc.". > > Well, I'm not familiar with cross context applications, but I assume > that there are certain things like security/authentication or > session handling that might get complicated. We set things up to make sure that the session is shared: all URLs access your application directly. > So for exmaple my XForm pages should only be available after > previous user authentication/login. But I'd guess the XForm pages > would be also accessible without prior login, if they are depolyed > in a second, the ops.war application. No, access is controlled through your own application's web.xml. All URLs that generate XForms pages are 100% controlled by your own web application. You can access URLs of Orbeon Forms directly if you don't protect them, but they won't show your own XForms pages: your application decides what XForms content goes to Orbeon Forms, not the other way around. > Furthermore I'm also not sure if all web containers support cross context > applications. My app for exmaple has to run on Weblogic 8, although I'm > using Tomcat during the development. Good point, WebLogic may or may not support this. I would assume it does, but I may be wrong - something to check in the WL doc. > And as you already mentioned, having only one web app to maintain means less > work, especially when updating an application in a clustered environment. :) But more potential trouble with JAR files and upgrading from one version of Orbeon Forms to another. As you see, it's a trade-off ;-) -Erik -- Orbeon Forms - Web Forms for the Enterprise Done the Right Way http://www.orbeon.com/ -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
|
|
Erik,
the "integrated" version currently does not work. For some reason Tomcat logs an 404 error in its access log, although the JSP page is available. The "seperate" version seems to basically work. Thus I've got some questions about it: - How do I access resources from the JSP/JSF app, like images, CSS, taglibs, etc.? Do I need to duplicate those resource to ops.war and keep them in sync? - What would be the easiest way to protect the XForms URLs from being accessed directly and not through my app? Does this need to be done programmatically? - Does this also work if ops.war is deployed on a different Tomcat instance? - Does this also work if my JSP/JSF page that contains XForms that need to be processed does not generate a complete XHTML page? What if the XForms are simply included from within a template JSP page? Anyway, it would be great if you could give me some further advise how to get the "integrated" version to work within an already existing (!) web app. Which configuration files do I need to copy to my web app? Which entries are required in my web.xml? etc. My two cents about two seperate Orbeon XForms applications: having a "minimal" and "framework" app seems to be a cleaner solution to me. Expecting "minimal" to be part of "framework" I'd assume that the effort (for testing etc) would not double. It just would move. - bitbyter Tuesday, April 10, 2007, 2:42:59 PM, you wrote: > BitByter, > Good remarks, and some things to add to the documentation. My comments > below. >>> Could you precise the reason why your preferred deployment option >>> is the "integrated" one? The "separate" deployment option was >>> designed explicitly as a solution to allow deployment of Orbeon >>> Forms for "people already using other web frameworks like Struts, >>> JSF, Tapestry, etc.". >> >> Well, I'm not familiar with cross context applications, but I assume >> that there are certain things like security/authentication or >> session handling that might get complicated. > We set things up to make sure that the session is shared: all URLs > access your application directly. >> So for exmaple my XForm pages should only be available after >> previous user authentication/login. But I'd guess the XForm pages >> would be also accessible without prior login, if they are depolyed >> in a second, the ops.war application. > No, access is controlled through your own application's web.xml. All > URLs that generate XForms pages are 100% controlled by your own web > application. > You can access URLs of Orbeon Forms directly if you don't protect > them, but they won't show your own XForms pages: your application > decides what XForms content goes to Orbeon Forms, not the other way > around. >> Furthermore I'm also not sure if all web containers support cross context >> applications. My app for exmaple has to run on Weblogic 8, although I'm >> using Tomcat during the development. > Good point, WebLogic may or may not support this. I would assume it > does, but I may be wrong - something to check in the WL doc. >> And as you already mentioned, having only one web app to maintain > means less >> work, especially when updating an application in a clustered > environment. :) > But more potential trouble with JAR files and upgrading from one > version of Orbeon Forms to another. As you see, it's a trade-off ;-) > -Erik -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Re: Integratin Orbeon Forms Into JSF Application
|
Administrator
|
Bitbyter,
> the "integrated" version currently does not work. For some reason > Tomcat logs an 404 error in its access log, although the JSP page is > available. Mmm... Not sure why this happens. Did you try the built-in examples: /ops/xforms-jsp/flickr-search/ /ops/xforms-jsp/guess-the-number/ > The "seperate" version seems to basically work. Thus I've got some questions > about it: > > - How do I access resources from the JSP/JSF app, like images, CSS, taglibs, > etc.? Do I need to duplicate those resource to ops.war and keep them in > sync? No, you don't touch the Orbeon Forms WAR at all. That's the point of the deployment as a separate WAR. You access your resources as you would from a regular JSP page. You use your taglibs as you would without XForms. > - What would be the easiest way to protect the XForms URLs from > being accessed directly and not through my app? Does this need to be > done programmatically? Well, let's make it clearer what an "XForms URL" is: the way this works is that you determine in your web.xml what URLs trigger the Orbeon Forms XForms filter. You can do this by extension, or by path. The default is to trigger the filter on URLs that start with /xforms-jsp/. So for example, say your app is deployed in context /my-app, then /my-app/xforms-jsp/hello.jsp will trigger the filter and thus the XForms engine. This URL is in your web application. It cannot be accessed more "directly" than that. Internally, the filter will forward content to a URL called /ops/xforms-renderer (/ops being the context in which Orbeon Forms is deployed). If you have an Apache front-end, you can hide from the outside world all URLs starting with /ops. > - Does this also work if ops.war is deployed on a different Tomcat > instance? No, it has to be in the same Tomcat instance. > - Does this also work if my JSP/JSF page that contains XForms that > need to be processed does not generate a complete XHTML page? What > if the XForms are simply included from within a template JSP page? Currently, it has to be a complete XHTML page. This means it also has to be well-formed XML. I don't know if JSF supports outputting well-formed XHTML. > Anyway, it would be great if you could give me some further advise > how to get the "integrated" version to work within an already > existing (!) web app. Which configuration files do I need to copy > to my web app? Which entries are required in my web.xml? etc. Doing this thoroughly would require some more work from our part, but for a start you will need the content of WEB-INF/resources. You can later remove the apps under WEB-INF/resources/apps. From web.xml, you will need the resource manager configuration, ops-xforms-filter, ops-main-servlet, ops-xforms-server-servlet, ops-renderer-servlet, and the associated mappings. Unless you use eXist, you can skip the eXist servlets. You can also skip the chart servlet. > My two cents about two seperate Orbeon XForms applications: having a > "minimal" and "framework" app seems to be a cleaner solution to me. > Expecting "minimal" to be part of "framework" I'd assume that the > effort (for testing etc) would not double. It just would move. "Cleaner" is all relative. I think it remains a trade-off ;-) -Erik -- Orbeon Forms - Web Forms for the Enterprise Done the Right Way http://www.orbeon.com/ -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
|
|
Tuesday, April 10, 2007, 5:20:20 PM, you wrote: > No, you don't touch the Orbeon Forms WAR at all. That's the point of > the deployment as a separate WAR. You access your resources as you > would from a regular JSP page. You use your taglibs as you would > without XForms. I'm not sure if I understood this correctly. Where do I have to place my JSP pages that generate the XForms output that I want to be processed by OF? Within the WAR of my app, or within the WAR of Orbeon XForms? > Well, let's make it clearer what an "XForms URL" is: the way this > works is that you determine in your web.xml what URLs trigger the > Orbeon Forms XForms filter. You can do this by extension, or by > path. The default is to trigger the filter on URLs that start with > /xforms-jsp/. So for example, say your app is deployed in context > /my-app, then /my-app/xforms-jsp/hello.jsp will trigger the filter and > thus the XForms engine. This URL is in your web application. It cannot > be accessed more "directly" than that. I got that point. But currently I placed my test xform page into the folder /xforms-jsp/myxforms of the ops.war. So it basically is possible to "directly" access my xform with the URL /ops/xforms-jsp/myxforms/test.jsp. And that is quite bad. > Internally, the filter will forward content to a URL called > /ops/xforms-renderer (/ops being the context in which Orbeon Forms is > deployed). Ah ok, probably this is also the reason for the 404 error with the "integrated" version. I did not define all those Orbeon XForms servlets. > "Cleaner" is all relative. I think it remains a trade-off ;-) Yes, just the question who got to pay... ;) - bitbyter -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Re: Integratin Orbeon Forms Into JSF Application
|
Administrator
|
Bitbyter,
>> No, you don't touch the Orbeon Forms WAR at all. That's the point >> of the deployment as a separate WAR. You access your resources as >> you would from a regular JSP page. You use your taglibs as you >> would without XForms. > > I'm not sure if I understood this correctly. Where do I have to > place my JSP pages that generate the XForms output that I want to be > processed by OF? Within the WAR of my app, or within the WAR of > Orbeon XForms? In separate mode, within the WAR of *your* application. > I got that point. But currently I placed my test xform page into the > folder /xforms-jsp/myxforms of the ops.war. So it basically is > possible to "directly" access my xform with the URL > /ops/xforms-jsp/myxforms/test.jsp. And that is quite bad. How do yo solve this problem with JSP in general? -Erik -- Orbeon Forms - Web Forms for the Enterprise Done the Right Way http://www.orbeon.com/ -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
«
Return to Orbeon Forms community mailing list
|
1 view|%1 views
| Free forum by Nabble | Edit this page |