Is there anything special about antlr-2_7_4_orbeon.jar that it can't be upgraded to antlr-2.7.6.jar (which comes with the new eXist)? -- -- 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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Fwiw, I got startup stack traces using antlr-2_7_4_orbeon.jar (specifically antlr related) with the new eXist jars: from WEB-INF/lib, I moved out the old exist jars mv *exist* /tmp/oldexist/ installed eXist to my home dir using the downloaded newcore jar, and copied over new jars based on http://eric.van-der-vlist.com/blog/1416?t=item cd ~/eXist cp -a exist-modules.jar exist-optional.jar exist.jar lib/core/jgroups-all.jar lib/core/xmldb.jar lib/core/xmlrpc-1.2-patched.jar $CATALINA_HOME/webapps/ROOT/WEB-INF/lib/ startup stack traces went away when I upgraded to antlr-2.7.6.jar. On Fri, Jan 26, 2007 at 06:01:22PM -0800, Mike Leary wrote: > > Is there anything special about antlr-2_7_4_orbeon.jar that it can't be > upgraded to antlr-2.7.6.jar (which comes with the new eXist)? -- -- 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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
The simplest case I could come up with would not PUT doc to eXist. Upgraded ops in the same way and tested the gov't forms: importing docs showed no result, but they were in eXist. I could make a new form and save it, but it also would not show up in the list. -- -- 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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Administrator
|
In reply to this post by Mike Leary
Mike,
I upgraded locally to eXist 1.1.1 without too many problems. I now have these JARs (and removed the old ones): antlr-2.7.6-exist_1_1_1.jar exist-1_1_1.jar jgroups-all-exist_1_1_1.jar xmlrpc-1.2-patched-exist_1_1_1.jar exist-modules-1_1_1.jar jug-lgpl-2_0_0-exist_1_1_1.jar exist-optional-1_1_1.jar xmldb-exist_1_1_1.jar I also had to use the new exist-conf.xml (which may be called conf.xml in the eXist distribution) and I removed the XML catalogs configuration in that file. FWIW, the current antlr-2_7_4_orbeon.jar is "rerooted", i.e. it is put in another package to prevent conflict with some application servers' incompatible antlr. Similarly, the eXist JAR was modified to refer to this new re-rooted antler. We haven't done this work for 1.1.1 yet, which is why we haven't committed that to CVS yet. (May the author of antlr be cursed, by the way, for not putting his classes in a decent Java package. ;-) -Erik Mike Leary wrote: > Fwiw, I got startup stack traces using antlr-2_7_4_orbeon.jar > (specifically antlr related) with the new eXist jars: > > from WEB-INF/lib, I moved out the old exist jars > mv *exist* /tmp/oldexist/ > > installed eXist to my home dir using the downloaded newcore jar, and > copied over new jars based on > http://eric.van-der-vlist.com/blog/1416?t=item > > cd ~/eXist > cp -a exist-modules.jar exist-optional.jar exist.jar lib/core/jgroups-all.jar lib/core/xmldb.jar lib/core/xmlrpc-1.2-patched.jar $CATALINA_HOME/webapps/ROOT/WEB-INF/lib/ > > startup stack traces went away when I upgraded to antlr-2.7.6.jar. > > > On Fri, Jan 26, 2007 at 06:01:22PM -0800, Mike Leary wrote: >> Is there anything special about antlr-2_7_4_orbeon.jar that it can't be >> upgraded to antlr-2.7.6.jar (which comes with the new eXist)? -- 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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
The more I look at this the better an external install of eXist looks. :) I'm happy to test anything, but I'll have to leave it to folks familiar with OXF's lib usage to make this happen. Here's a breakdown of eXist's libs that might help in upgrading OXF's eXist. * = probably should be upgraded/included x = conflict - = probably not needed Top level: * exist-modules.jar * exist-optional.jar * exist.jar Endorsed: * serializer-2.7.0.jar -- not in oxf * xalan-2.7.0.jar -- 2_5_1_orbeon in oxf x xercesImpl.jar -- xml-apis-xerces_2_6_2_orbeon.jar in oxf x xml-apis.jar -- xml-apis-xerces_2_6_2_orbeon.jar in oxf I had copied those four into $CATALINA_HOME/common/endorsed. Is xml-apis-xerces_2_6_2_orbeon then superfluous, conflicting, customized? See other possible xerces conflict below. Core: * antlr-2.7.6.jar * jgroups-all.jar * xmldb.jar * xmlrpc-1.2-patched.jar * sunxacml.jar -- open source implementation of the OASIS XACML standard (eXtensible Access Control Markup -- seems worth including :) I didn't try adding this. X resolver.jar -- (xml-commons resolver lib) resolver-xerces_2_6_2_orbeon in oxf - commons-pool-1.2.jar -- 1.3 is in oxf - excalibur-cli-1.0.jar -- a lightweight, embeddable Inversion of Control container named Fortress that is written in java - javax.servlet.jar -- tomcat has servlet-api.jar - jEdit-syntax.jar -- a syntax highlighting JavaBean (could be worth a look?) - jline-0_9_5.jar -- library for handling console input - log4j-1.2.14.jar -- log4j-1.3alpha0 is in oxf ( alpha-8 of log4j is available ) Optional: * jug-lgpl-2.0.0.jar -- seems odd that it's optional... formatted for fixed-width: _eXist_ _OXF_ axis.jar axis_1_2_1-axis.jar in oxf axis-ant.jar axis-schema.jar commons-discovery-0.2.jar commons-discovery-0_2.jar commons-fileupload-1.1.1.jar commons-fileupload-1.0.jar commons-httpclient-3.0.jar commons-httpclient-3_0_1.jar commons-io-1.1.jar commons-logging-1.0.4.jar jaxrpc.jar axis_1_2_1-jaxrpc.jar nekohtml-0.9.5.jar saaj.jar axis_1_2_1-saaj.jar wsdl4j-1.5.1.jar axis_1_2_1-wsdl4j-1.5.1.jar -- -- 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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Administrator
|
On 1/27/07, Mike Leary <[hidden email]> wrote:
> The more I look at this the better an external install of eXist looks. :) Hi Mike, Yes: In the Orbeon Forms example, we are re-rooting antlr because if we don't, Orbeon Forms won't work out of the box on some application servers. This has the downside that upgrading to a new version of eXist required antlr to be re-rerooted. Yes, this makes upgrading eXist harder, but getting Orbeon Forms to work out of the box is a priority. So by all mean, if you need a version of eXist which is more recent than the one shipped with Orbeon Forms, the easiest thing at this point is to deploy the eXist WAR file separately, along Orbeon Forms. Alex -- 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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Almost but not quite...
I have an (oxf) app separate from the ops webapp dir (in ROOT). According to the exist deployment guide: "Important It is currently not possible to run more than one instance of the eXist database in one servlet container." Is it not really? I don't know, but that's enough to keep me away from it. I'll try turning off exist in the nightly ops build; else I think I'll deploy the nightly ops (for documentation) into jetty, and then run my app and exist in tomcat. :p On Wed, Jan 31, 2007 at 07:24:46PM -0800, Alessandro Vernet wrote: > So by all mean, if you need a version of eXist which is more recent > than the one shipped with Orbeon Forms, the easiest thing at this > point is to deploy the eXist WAR file separately, along Orbeon Forms. -- -- 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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Administrator
|
Mike,
That's a surprising note! We can't confirm this because we haven't tried running multiple instances of eXist in the same servlet container. Can you try posting to the exist-open mailing-list to ask what the deal is? BTW as I said earlier, I have locally eXist 1.1.1 running fine within the Orbeon WAR under Tomcat. -Erik Mike Leary wrote: > Almost but not quite... > > I have an (oxf) app separate from the ops webapp dir (in ROOT). > > According to the exist deployment guide: > > "Important > > It is currently not possible to run more than one instance of the eXist > database in one servlet container." > > Is it not really? I don't know, but that's enough to keep me away from > it. I'll try turning off exist in the nightly ops build; else I think > I'll deploy the nightly ops (for documentation) into jetty, and then run > my app and exist in tomcat. :p > > > > > On Wed, Jan 31, 2007 at 07:24:46PM -0800, Alessandro Vernet wrote: >> So by all mean, if you need a version of eXist which is more recent >> than the one shipped with Orbeon Forms, the easiest thing at this >> point is to deploy the eXist WAR file separately, along Orbeon Forms. > -- 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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Administrator
|
In reply to this post by Mike Leary
Hi Mike,
On 2/1/07, Mike Leary <[hidden email]> wrote: > "Important > > It is currently not possible to run more than one instance of the eXist > database in one servlet container." I am also surprised by this comment. But note that if you are deploying eXist in a separate WAR file, you can disable the eXist that comes with Orbeon Forms. Doing so is a simple matter of removing the 2 eXist servlets declared in the Orbeon Forms web.xml (one for the REST API and the other one for WebDAV). Then only the jars will be left, and as they will be loaded by a different class loader, I doubt they can cause any problem. Alex -- 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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
Free forum by Nabble | Edit this page |