Orbeon Forms community mailing list

Separate exist deployment in Orbeon 3.9

Classic

List

Threaded

8 messages Options

Ethan Gruber

Separate exist deployment in Orbeon 3.9

I've seen a few threads about this, but many are a few years old, and I'm not sure they still apply.

I have a separate exist deployment running in Tomcat, so I'd like to have Orbeon save to that instead of the default exist database that it ships with. I followed older directions and placed the following into properties-local.xml:

<property as="xs:anyURI" name="oxf.xforms.store.application.uri" value="xmldb:exist://localhost:8080/exist/xmlrpc"/>
<property as="xs:string" name="oxf.xforms.store.application.collection" value="/db/orbeon/xforms/cache/"/>

However, this seems to have no result when I restart Tomcat. Am I missing something? I have also used "http://localhost:8080/exist" for "oxf.xforms.store.application.uri" with no effect. Is there a different way to change the default exist in 3.9? Once this is accomplished, will I have to change my action for XForms submissions (my guess is 'no'), e.g., action="/exist/rest/db/eaditor/test.xml"?

Thanks,
Ethan

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

Re: Separate exist deployment in Orbeon 3.9

Administrator

Ethan,

This property is for the XForms engine state store. In 3.9, the XForms
engine no longer uses eXist to store state so these properties will
have no effect.

There are separate properties for Form Runner, but if I understand
well you are not using that.

The way to go ahead then would be to create your own property, and
then, for each submission, to do something like:

<xf:submission action="{xxf:property('my.exist.url')}/exist/…" …/>

where my.exist.url is the name of the property.

-Erik

On Tue, May 17, 2011 at 1:42 PM, Ethan Gruber <[hidden email]> wrote:

> I've seen a few threads about this, but many are a few years old, and I'm
> not sure they still apply.
>
> I have a separate exist deployment running in Tomcat, so I'd like to have
> Orbeon save to that instead of the default exist database that it ships
> with. I followed older directions and placed the following into
> properties-local.xml:
>
> <property as="xs:anyURI" name="oxf.xforms.store.application.uri"
> value="xmldb:exist://localhost:8080/exist/xmlrpc"/>
> <property as="xs:string" name="oxf.xforms.store.application.collection"
> value="/db/orbeon/xforms/cache/"/>
>
> However, this seems to have no result when I restart Tomcat. Am I missing
> something? I have also used "http://localhost:8080/exist" for
> "oxf.xforms.store.application.uri" with no effect. Is there a different way
> to change the default exist in 3.9? Once this is accomplished, will I have
> to change my action for XForms submissions (my guess is 'no'), e.g.,
> action="/exist/rest/db/eaditor/test.xml"?
>
> Thanks,
> Ethan
>
>
> --
> 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

Ralf Jung

Re: Re: Separate exist deployment in Orbeon 3.9

Hi,

> This property is for the XForms engine state store. In 3.9, the XForms
> engine no longer uses eXist to store state so these properties will
> have no effect.
So, can the exist servlet configs and the jar files be removed from Orbeon
without problems, if Form Runner/Builder are not used? Or is there a less
invasive way to disable the Orbeon-internal eXist?

Kind regards,
Ralf

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

Re: Re: Re: Separate exist deployment in Orbeon 3.9

Administrator

Ralf,

Yes they can be removed entirely in Orbeon Forms 3.9. Simply
commenting out/removing the entries in web.xml will do, but feel free
to remove all the eXist JAR files as well.

-Erik

On Wed, May 18, 2011 at 10:57 AM, Ralf Jung <[hidden email]> wrote:

> Hi,
>
>> This property is for the XForms engine state store. In 3.9, the XForms
>> engine no longer uses eXist to store state so these properties will
>> have no effect.
> So, can the exist servlet configs and the jar files be removed from Orbeon
> without problems, if Form Runner/Builder are not used? Or is there a less
> invasive way to disable the Orbeon-internal eXist?
>
> Kind regards,
> Ralf
>
>
> --
> 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
>
>

Ralf Jung

Re: Re: Re: Re: Separate exist deployment in Orbeon 3.9

Hi Erik,

thanks a lot, it's indeed working :)

Kind regards,
Ralf

Am Donnerstag 19 Mai 2011, um 08:01:17 schrieb Erik Bruchez:

> Ralf,
>
> Yes they can be removed entirely in Orbeon Forms 3.9. Simply
> commenting out/removing the entries in web.xml will do, but feel free
> to remove all the eXist JAR files as well.
>
> -Erik
>
> On Wed, May 18, 2011 at 10:57 AM, Ralf Jung <[hidden email]> wrote:
> > Hi,
> >
> >> This property is for the XForms engine state store. In 3.9, the XForms
> >> engine no longer uses eXist to store state so these properties will
> >> have no effect.
> >
> > So, can the exist servlet configs and the jar files be removed from
> > Orbeon without problems, if Form Runner/Builder are not used? Or is
> > there a less invasive way to disable the Orbeon-internal eXist?
> >
> > Kind regards,
> > Ralf
> >
> >
> > --
> > 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

Ethan Gruber

Re: Re: Re: Re: Re: Separate exist deployment in Orbeon 3.9

Thanks for your help. This is exactly what I was looking for: disabling Orbeon's internal exist and switching to a separate instance.

Ethan

On Thu, May 19, 2011 at 5:19 AM, Ralf Jung <[hidden email]> wrote:

Hi Erik,

thanks a lot, it's indeed working :)

Kind regards,
Ralf

Am Donnerstag 19 Mai 2011, um 08:01:17 schrieb Erik Bruchez:

> Ralf,
>
> Yes they can be removed entirely in Orbeon Forms 3.9. Simply
> commenting out/removing the entries in web.xml will do, but feel free
> to remove all the eXist JAR files as well.
>
> -Erik
>
> On Wed, May 18, 2011 at 10:57 AM, Ralf Jung <[hidden email]> wrote:
> > Hi,
> >
> >> This property is for the XForms engine state store. In 3.9, the XForms
> >> engine no longer uses eXist to store state so these properties will
> >> have no effect.
> >
> > So, can the exist servlet configs and the jar files be removed from
> > Orbeon without problems, if Form Runner/Builder are not used? Or is
> > there a less invasive way to disable the Orbeon-internal eXist?
> >
> > Kind regards,
> > Ralf
> >
> >
> > --
> > 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

lacco

Re: Re: Re: Re: Re: Separate exist deployment in Orbeon 3.9

I have an orbeon setup that uses form runner/ builder with its own REST backend (specified via oxf.fr.persistence.app.uri.*.*.*). Is it also possible for me to remove the complete exist backend? If yes, how do I achieve this exactly (what are the relevant lines in web.xml)? Thx!

Ralf Jung

Re: Re: Re: Re: Re: Re: Separate exist deployment in Orbeon 3.9

Hi lacco,

yes, that's easily possible, I did it for my deployment. You can remove all
the jar files in the libs folder that start with "exist".
For the web.xml, I do not know exactly what I changed, but I attached my
version of that file for reference. It could be that I commented out too much
for your need (e.g. I don't use Form Runner at all), but it should give you an
idea.

Kind regards,
Ralf

Am Montag 25 Juli 2011, um 17:35:23 schrieb lacco:

> I have an orbeon setup that uses form runner/ builder with its own REST
> backend (specified via oxf.fr.persistence.app.uri.*.*.*). Is it also
> possible for me to remove the complete exist backend? If yes, how do I
> achieve this exactly (what are the relevant lines in web.xml)? Thx!
>
> --
> View this message in context:
> http://orbeon-forms-ops-users.24843.n4.nabble.com/Separate-exist-deploymen
> t-in-Orbeon-3-9-tp3530691p3693128.html Sent from the Orbeon Forms
> (ops-users) mailing list archive at Nabble.com.

web.xml (15K) Download Attachment