> Quick comments, not directly related to MySQL:
>
> 1. The embedded eXist is used for two purposes:
>
> 1.1. Storage of XForms state when memory overflows
> 1.2. Document storage for the demos
>
> Regarding #1.1, we could use something else, it's just that we had
> eXist on hand. Currently the XForms engine natively uses eXist for
> that purpose, but it's an implementation detail I would say.
>
> Regarding #1.2, you probably shouldn't use the embedded eXist for
> production. Rather, use a separate eXist deployment.
>
> Form Runner allows you currently to use eXist, Oracle XML, and
> hopefully soon MySQL as a backend (if somebody sponsors it ;).
>
> 2. You can choose what eXist instance to use using the configuration properties.

>
> -Erik
>
> On Thu, Jan 28, 2010 at 3:18 PM, Jeremiah Jahn <[hidden email]> wrote:
>> I'd also suggest that you  use client states in place of exists. The one
>> change will make things a lot easier. I also remember reading someplace that
>> you might be able to se oracle, but that's costly, and I'm not sure where I
>> saw that. My one problem with exists, is that you can't really choose where
>> it is located, which is a an issue with exists, and not orbeon.
>> You may also want to check out a combination of JAXB, and hibernate. Don't
>> know if that will work, otherwise you have to WAY abstract, and treat
>> everything at a node level, and do some serious java reflection. You'l also
>> run into a large number or normalization issues. You should probably
>> consider just determining the metadata you need from he form, and using the
>> DB as a place to store that, plus the intact XML as text.  I really depends
>> alot on what you are trying to do with the data.
>>
>> Sorry for the explosion of comments,
>> -jj-
>> On Jan 28, 2010, at 2:35 PM, Hank Ratzesberger wrote:
>>
>> Tom,
>> Would it be simpler to get the data out of eXist and update Mysql with
>> "shredded" data and/or
>> the XML as text document?
>> This adds a layer to the form designer that would break with every new
>> feature or control.  On the
>> other hand, a process that, say, uses XSLT to create SQL statements would
>> move this task
>> out of the FR persistence layer.  I'm presuming it doesn't need to be
>> real-time...
>> --Hank
>> On Jan 28, 2010, at 12:09 PM, Thomas Lynk wrote:
>>
>> Hey,
>>
>> We are looking for your support on an proposed upgrade to Orbeon.
>>
>> We want to hire the team at Orbeon to replace the eXists with Mysql.  That
>> means when you create a form it will create a mysql database to store the
>> form data.  The issue is that it is a lot of work and expensive. I am
>> looking for a group of users to cost share the project.
>>
>> If you’re interested please contact me and we can discuss the details.
>>
>> Tom
>>
>> [hidden email]
>> (519) 962-9974
>>
>>
>>
>> --
>> 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
>>
>> Hank Ratzesberger
>> NEES@UCSB
>> Institute for Crustal Studies,
>> University of California, Santa Barbara
>> 805-893-8042
>>
>>
>>
>>
>>
>> --
>> 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
>>
>>
>
> --
> 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