Separate deployment query

>
> Hi,
>
> I was wondering if someone could advise me on whether 'separate deployment'
> is the right approach for the following scenario:
>
> We have several Orbeon XForms applications (handwritten, not using Form
> Builder)  that currently we deploy in a single context under Tomcat. The
> multiple applications are currently all stored below the "resources/apps"
> folder as per the way the default Orbeon example applications are deployed.
> Each application needs to access separate JNDI data sources and essentially
> be independent of the others from a security point of view. So each time we
> need to define a new application, we add the source files under the apps
> folder, update the web.xml, server.xml and context.xml files.
>
> The problem is is that this is all very time consuming and leads to
> dependencies between the applications. If we want to stop one of the
> applications, we affect all the others. In general it is awkward to maintain
> the applications in isolation.
>
> We were wondering if the separate deployment mechanism can be used to help
> with this? However all the documentation refers to JSP/Jave applications,
> using the Orbeon deployment to handle the Xforms processing etc. It is not
> clear to me if we can use the separate deployment mechanism to effectively
> run separate Orbeon Xforms applications that all make use of their own
> (private) page flow, XPL pipelines etc.
>
> Is this a scenario that separate deployment can help with?
>
> Thanks,
> Neil
> --
> View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Separate-deployment-query-tp2313097p2313097.html
> Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com.
>

>
> Hi,
>
> I was wondering if someone could advise me on whether 'separate deployment'
> is the right approach for the following scenario:
>
> We have several Orbeon XForms applications (handwritten, not using Form
> Builder)  that currently we deploy in a single context under Tomcat. The
> multiple applications are currently all stored below the "resources/apps"
> folder as per the way the default Orbeon example applications are deployed.
> Each application needs to access separate JNDI data sources and essentially
> be independent of the others from a security point of view. So each time we
> need to define a new application, we add the source files under the apps
> folder, update the web.xml, server.xml and context.xml files.
>
> The problem is is that this is all very time consuming and leads to
> dependencies between the applications. If we want to stop one of the
> applications, we affect all the others. In general it is awkward to maintain
> the applications in isolation.
>
> We were wondering if the separate deployment mechanism can be used to help
> with this? However all the documentation refers to JSP/Jave applications,
> using the Orbeon deployment to handle the Xforms processing etc. It is not
> clear to me if we can use the separate deployment mechanism to effectively
> run separate Orbeon Xforms applications that all make use of their own
> (private) page flow, XPL pipelines etc.
>
> Is this a scenario that separate deployment can help with?
>
> Thanks,
> Neil
> --
> View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Separate-deployment-query-tp2313097p2313097.html
> Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com.
>

>
> Hi Alex,
>
> Yes, we are using the SQL processor in XPL and referencing the various data
> sources via JNDI.
>
> What we are hoping to achieve is effectively to run many Orbeon Forms
> applications on the same server, but without having to deploy common
> resources more than once or to have to overlay our application resources
> with the core framework.
>
> Each application needs to access some common data sources, plus some unique
> to itself. We've been able to achieve this on a small scale by manually
> configuring the resources. Each time we need to define a new application, we
> have to update the whole deployment. We are now trying to make this process
> more streamlined and we had thought separate deployment may help us isolate
> each application. However I think I may have misinterpreted the purpose of
> separate deployment.
>
> However I've just come across your tip about referencing resources in a
> separate webapps directory. This may well help us achieve some of the effect
> we would like:
>
> http://orbeon-forms-ops-users.24843.n4.nabble.com/separate-deployment-w-o-Java-td44095.html#a44097
>
> I'm going to try and see if this gets us closer to where we need to be.
>
> Thanks,
> Neil
> --
> View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Separate-deployment-query-tp2313097p2316014.html
> Sent from the Orbeon Forms (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
>
>