Separate deploying the XForms engine.

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Separate deploying the XForms engine.

jfmoreno
This post was updated on .
Hi:
 
Please help me with your suggestions.
    I've looked at the writeup on separate deploying the XForms engine with Java applications (http://www.orbeon.com/ops/doc/reference-xforms-java) , as you recommend, but it seems not being enough to solve my problem ;-). I want to deploy in a OC4J application server, and I have two questions:

 
1. It's possible to do a minimal deployment without a whole orbeon war?, what files, and where are the essentials for work only the XForms engine.
2. We have the following configuration in our application's web.xml (only the filters):
 

 
  <filter>
    <filter-name>FiltroInicialFRACC</filter-name>
    <filter-class>ip2.comun.controlapp.control.FRACCInitialFilter</filter-class>
   
    <init-param>
      <param-name>UsarAppSession</param-name>
      <param-value>true</param-value>
      <description>Parametro del filtro que indica a FRACC que se debe usar la
      sesión de aplicación</description>
    </init-param>
    <init-param>
      <param-name>NombreParametroHTTPSubaplicacion</param-name>
      <param-value>SUBAPP</param-value>
      <description>Parametro del filtro que indica a FRACC cómo se llama el
      parámetro HTTP en el que llegará la subaplicación asociada a cada usuario
      </description>
    </init-param>
  </filter>
 
  <filter>
    <filter-name>orbeon-xforms-filter</filter-name>
    <filter-class>org.orbeon.oxf.servlet.OrbeonXFormsFilter</filter-class>
    <init-param>
      <param-name>oxf.xforms.renderer.context</param-name>
      <param-value>/DOCUNET</param-value>
    </init-param>
  </filter>
 
  <filter-mapping>
    <filter-name>FiltroInicialFRACC</filter-name>
    <url-pattern>/ServletAccion</url-pattern>
  </filter-mapping>
 
  <filter-mapping>
    <filter-name>orbeon-xforms-filter</filter-name>
    <url-pattern>/visordocumentos/VisualizaDocumentoPrincipal.jsp</url-pattern>
    <dispatcher>REQUEST</dispatcher>
    <dispatcher>FORWARD</dispatcher>
  </filter-mapping>
 
.. it's correct?, because don't work. Many errors occur related the first filter (this is a part of our Framework MVC). It's possible to integrate Orbeon Forms XForms filter in this scenario?. How?.
 
Thanks in advance, your assistance is highly appreciated.

In the attached file OC4JTrace.txt can you see the trace.OC4JTrace.txt
Reply | Threaded
Open this post in threaded view
|

Re: Separate deploying the XForms engine.

Erik Bruchez
Administrator
Regarding #1, I don't think we have an official list of optional JAR
files. We should do it at some point.

Regarding #2, it's hard to be super specific without spending a lot of
time, but yes you should be able to chain multiple filters including
OrbeonXFormsFilter.

-Erik

On Wed, Jul 1, 2009 at 4:27 AM, jfmoreno<[hidden email]> wrote:

>
> Hi:
>
> Please help me with your suggestions.
>    I've looked at the writeup on
> http://www.nabble.com/file/p24288189/OC4JTrace.txt OC4JTrace.txt  with Java
> applications (http://www.orbeon.com/ops/doc/reference-xforms-java) , as you
> recommend, but it seems not being enough to solve my problem ;-). I want to
> deploy in a OC4J application server, and I have two questions:
>
>
> 1. It's possible to do a minimal deployment without a whole orbeon war?,
> what files, and where are the essentials for work only the XForms engine.
> 2. We have the following configuration in our application's web.xml (only
> the filters):
>
> <!-- ************************ Parámetros de contexto ***********************
> -->
>  <!-- ******************************* Filtros
> ****************************** -->
>  <filter>
>    <filter-name>FiltroInicialFRACC</filter-name>
>
> <filter-class>ip2.comun.controlapp.control.FRACCInitialFilter</filter-class>
>    <!-- Filtro usado por FRACC para controlar las peticiones HTTP, crear la
>    sesión web y controlar la sesión de aplicación si se indica que se use.
>    Debe ser el primer filtro declarado en web.xml.
>    Este filtro tiene dos parámetros opcionales (obligatorios si se trabaja
> con
>    subaplicaciones):
>      - UsarAppSession:
>      - NombreParametroHTTPSubaplicacion -->
>    <init-param>
>      <param-name>UsarAppSession</param-name>
>      <param-value>true</param-value>
>      <description>Parametro del filtro que indica a FRACC que se debe usar
> la
>      sesión de aplicación</description>
>    </init-param>
>    <init-param>
>      <param-name>NombreParametroHTTPSubaplicacion</param-name>
>      <param-value>SUBAPP</param-value>
>      <description>Parametro del filtro que indica a FRACC cómo se llama el
>      parámetro HTTP en el que llegará la subaplicación asociada a cada
> usuario
>      </description>
>    </init-param>
>  </filter>
>  <!-- Declare and configure the Orbeon Forms XForms filter -->
>  <filter>
>    <filter-name>orbeon-xforms-filter</filter-name>
>    <filter-class>org.orbeon.oxf.servlet.OrbeonXFormsFilter</filter-class>
>    <init-param>
>      <param-name>oxf.xforms.renderer.context</param-name>
>      <param-value>/DOCUNET</param-value>
>    </init-param>
>  </filter>
>  <!-- **************************** Mapeos de Filtros
> *************************** -->
>  <filter-mapping>
>    <filter-name>FiltroInicialFRACC</filter-name>
>    <url-pattern>/ServletAccion</url-pattern>
>  </filter-mapping>
>  <!-- Any web resource under
> /visordocumentos/VisualizaDocumentoPrincipal.jsp
>    is processed by the XForms engine -->
>  <filter-mapping>
>    <filter-name>orbeon-xforms-filter</filter-name>
>
> <url-pattern>/visordocumentos/VisualizaDocumentoPrincipal.jsp</url-pattern>
>    <dispatcher>REQUEST</dispatcher>
>    <dispatcher>FORWARD</dispatcher>
>  </filter-mapping>
>
> .. it's correct?, because don't work. Many errors occur related the first
> filter (this is a part of our Framework MVC). It's possible to integrate
> Orbeon Forms XForms filter in this scenario?. How?.
>
> Thanks in advance, your assistance is highly appreciated.
>
> In the attached file OC4JTrace.txt can you see the trace.
> --
> View this message in context: http://www.nabble.com/Separate-deploying-the-XForms-engine.-tp24288189p24288189.html
> Sent from the ObjectWeb OPS - Users mailing list archive at Nabble.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
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>


--
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
OW2 mailing lists service home page: http://www.ow2.org/wws