separate deployment w/o Java

Howdy,

Using Orbeon forms has made implementing my application so simple, I do
not have any "code" at all.   All I have are a bunch of xhtml/xml/xpl
files that call external programs written by someone else.  The
integration demo worked fine so now I need to work on deployment.    
Originally I was planning on deploying orbeon.war and then dropping my
files on top of orbeon but the CM guys would prefer that I deliver a
separate WAR file from orbeon.war which makes sense but I can't find an
example of what should go into my war file.

I've looked at the writeup on deploying the XForms engine with Java
applications (http://www.orbeon.com/ops/doc/reference-xforms-java) but
as I don't have any Java code myself, I'm at a loss as to what goes into
my web.xml file in addition to the filter definitions.  I assume I need
to reference a servlet but what?  Do I need to copy more than just
orbeon-xforms-filter.jar into my WEB-INF/lib directory?  I'm using
tomcat 6 so I created a META-INF/context.xml file with the following:

<Context crossContext="true"/>

I've tried looking through the docs but can't find anything that covers
this.   Should I search for something other than deployment?

I am using Orbeon Forms dev-3.7.1.200905272119 on Linux.

I have also seen references to a rewrite issue with regard to separate
deployment so I am wondering if I'll get hit by this.  Will I need to
change my references to orbeon?

TIA,
claude




--
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

And just to be clear, I am making use of page-flow with individual xpl
pipelines where I pass one or more arguments - such as the path to the
data file I want processed by the external program.   I'm also using
replace="instance" in my submits, no replace="all".

So with that in mind, does it make sense to do a separate deployment?  
Is there a clean way for me to deploy my orbeon "applets" separate from
the orbeon.war file?  I'd like to be able to make use of orbeon updates
w/o having to "redeploy" my application each time.


claude felizardo wrote:

--
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

The initial idea of separate deployment is that a given web app (WAR)  
produces XForms documents which are processed by the Orbeon Forms WAR.  
Is that anywhere close from your scenario?

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

Erik Bruchez wrote: Nope.   My project is adapting an existing web/database application and
enhancing it with some new functionality.  Most of it is pretty much
HTML and CGI's written in C.   With the exception of me calling some
external programs via XPL, my stuff is completely generated and
processed by Orbeon Forms.   They didn't even have Tomcat installed
until I needed it for Orbeon Forms so no other Java code anywhere.   The
new applications are pretty much independent so we just need to provide
links to each other in a navbar.

It sounds like separate deployment doesn't make sense for me.  If that's
the case, what will be the best way for me to deploy my app?

What about creating my own WAR file that is expanded on top of orbeon
that replaces the original apps-list.xml and page-flow.xml files in the
WEB-INF/resources directory, adds my properties-local.xml and
theme-local.xml in the config diretory and then copies my application
files in the apps directory?  That would allow us to CM orbeon.war the
same way we handle Apache and Tomcat and then my stuff could go into the
same area as the rest of our application source files.  During the build
process we'd create a new WAR and installation would consist of creating
a new directory inside of Tomcat, expand the latest stable orbeon.war
and then my WAR in the same place.

claude




--
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

Claude,

cfeliz wrote

It sounds like separate deployment doesn't make sense for me.  If that's
the case, what will be the best way for me to deploy my app?

Right, in this case you can't use separate deployment. If I understand you correctly, your application consists of resources that you deploy in WEB-INF/resources. If your goal is to deploy an unchanged orbeon.war, you can setup the resource manager to get the resources from a location other than WEB-INF/resources. The resource manager is setup in web.xml with context parameters:

    <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/resources</param-value>
    </context-param>
    <context-param>
        <param-name>oxf.resources.priority.2</param-name>
        <param-value>org.orbeon.oxf.resources.ClassLoaderResourceManagerFactory</param-value>
    </context-param>

This tells the resource manager to first look for resources in the war file, under /WEB-INF/resources, and then, if not found there, through the class loader (in the jar files). You could replace the WebAppResourceManagerFactory with the FilesystemResourceManagerFactory to get the files from some location on disk:

    <context-param>
        <param-name>oxf.resources.priority.1</param-name>
        <param-value>org.orbeon.oxf.resources.FilesystemResourceManagerFactory</param-value>
    </context-param>
    <context-param>
        <param-name>oxf.resources.priority.1.oxf.resources.filesystem.sandbox-directory</param-name>
        <param-value>/home/me/my-resources</param-value>
    </context-param>

And if you don't want to change the web.xml (so you really keep the orbeon.war completely unchanged), you can set this in the server.xml with two <Parameter> (the first one would be: <Parameter name="oxf.resources.priority.1" value="org.orbeon.oxf.resources.FilesystemResourceManagerFactory"/>) inside the <Context>. Those <Parameter> should override the context parameters in the server.xml. I haven't tried this, so you'll let me know if this works for you ;).

Alex