CVS Update: Barracuda
[email protected] Mon, 28 Oct 2002 1:05:02 ()
| Newsgroups | gmane.comp.java.enhydra.barracuda.cvs |
|---|---|
| Message-ID | <[email protected]> |
CVSROOT: /u/cvs Module name: Barracuda Repository: Projects/EnhydraOrg/toolsTech/Barracuda/src/org/enhydra/barracuda/core/util/dom/ Changes by: JacobK@frogger. 02/10/28 01:05:02 Modified files: Projects/EnhydraOrg/toolsTech/Barracuda/WEB-INF/jars/: barracuda-ant.jar Projects/EnhydraOrg/toolsTech/Barracuda/WEB-INF/lib-ext/: barracuda-core.jar barracuda-examples.jar barracuda-testbed.jar barracuda-tutorials.jar plankton.jar Projects/EnhydraOrg/toolsTech/Barracuda/WEB-INF/lib/: barracuda-admin.jar barracuda-config.jar barracuda.jar Projects/EnhydraOrg/toolsTech/Barracuda/src/: build.xml sample.version.properties Projects/EnhydraOrg/toolsTech/Barracuda/src/org/enhydra/barracuda/core/util/dom/: DefaultDOMFactory.java Added files: Projects/EnhydraOrg/toolsTech/Barracuda/WEB-INF/lib-ext/: plankton-webapp.jar Log message: Had to add a necessary change based on the new Log4jCRS repository selector. Actually, it isn't so much a problem with the repository selector than a problem with Log4jInit. Log4jInit, as it is currently coded, is required to exist within the local webapp classloader so that it dies along with the webapp. This probably could be fixed, but the easy solution is to create a plankton-webapp.jar which *always* goes in the WEB-INF/lib of ones webapp. plankton.jar can then either move to wherever log4j exists which can be either in the webapp classloader or in a parent classloader such as $CATALINA_HOME/shared/lib. Actually, you should put log4j in $CATALINA_HOME/common/lib in order not to mess up Tomcat's own logging system. This will work just as well for our purposes while keeping commons-logging happy. I'm also working on some weird classloading issues with XMLCStdFactory.java. I made a change in DefaultDOMFactory.java which should really be done, but it doesn't look like it affects the problem at hand. The change I made is to call XMLCStdFactory like this: new XMLCStdFactory(cl.getClassLoader(), null); instead of this: new XMLCStdFactory(this.getClass().getClassLoader(), new StreamXMLCLogger()); XMLCStdFactory creates its own StreamXMLCLogger() if we pass it null, so no need to specificaly pass that and we shouldn't assume that DefaultDOMFactory will be created by the same classloader as the class needing loading by XMLCStdFactory so get the classloader from the class instead of 'this', or DefaultDOMFactory. Again, it really didn't affect anything. The classloading issue is happening where barracuda-core.jar and plankton.jar exist in shared/lib alongside xmlc-2.1.jar. Things are fine on the first install and run of the application, but fail after removal and another install. Upon attempting loading of the XMLC page I get errors like this: Caused by: java.lang.ClassNotFoundException: org.enhydra.barracuda.contrib.dbroggisch.examples.view.xmlc.PrefixMappingHTMLImpl Anyway, I'm investigating. May also be a Tomcat bug. You never know. Jake =================================================================== File: no file barracuda-ant.jar Status: Unknown Working revision: No entry for barracuda-ant.jar Repository revision: No revision control file =================================================================== File: no file barracuda-core.jar Status: Unknown Working revision: No entry for barracuda-core.jar Repository revision: No revision control file =================================================================== File: no file barracuda-examples.jar Status: Unknown Working revision: No entry for barracuda-examples.jar Repository revision: No revision control file =================================================================== File: no file barracuda-testbed.jar Status: Unknown Working revision: No entry for barracuda-testbed.jar Repository revision: No revision control file =================================================================== File: no file barracuda-tutorials.jar Status: Unknown Working revision: No entry for barracuda-tutorials.jar Repository revision: No revision control file =================================================================== File: no file plankton.jar Status: Unknown Working revision: No entry for plankton.jar Repository revision: No revision control file =================================================================== File: no file barracuda-admin.jar Status: Unknown Working revision: No entry for barracuda-admin.jar Repository revision: No revision control file =================================================================== File: no file barracuda-config.jar Status: Unknown Working revision: No entry for barracuda-config.jar Repository revision: No revision control file =================================================================== File: no file barracuda.jar Status: Unknown Working revision: No entry for barracuda.jar Repository revision: No revision control file =================================================================== File: no file build.xml Status: Unknown Working revision: No entry for build.xml Repository revision: No revision control file =================================================================== File: no file sample.version.properties Status: Unknown Working revision: No entry for sample.version.properties Repository revision: No revision control file =================================================================== File: no file DefaultDOMFactory.java Status: Needs Checkout Working revision: 1.4 Mon Oct 28 09:05:02 2002 Repository revision: 1.4 /u/cvs/Projects/EnhydraOrg/toolsTech/Barracuda/src/org/enhydra/barracuda/core/util/dom/DefaultDOMFactory.java,v Existing Tags: Barracuda_1_1_1 (revision: 1.3) Barracuda_1_1_0 (revision: 1.3) BARRACUDA_1_0_FINAL (revision: 1.3) =================================================================== File: no file plankton-webapp.jar Status: Unknown Working revision: No entry for plankton-webapp.jar Repository revision: No revision control file