From: Vladimir G. <vla...@du...> - 2010-02-12 14:57:30
|
On Feb 12, 2010, at 3:02 AM, Rutger Vos wrote: > This hasn't been fixed yet: mesquite can't be found, the > mesquite.folder_dir property is set to "null/foo" at runtime. I assume > this is due to the new JNDI configuration system, so the path needs to > be set either in web.xml or treebase-web.xml. Vladimir, can you please > explain how this is supposed to work and put it on the wiki? Jon said he fixed the problem, on treebase-dev:80, Thu afternoon; file uploads work for me as of Fri morning. Details are on the wiki at https://sourceforge.net/apps/mediawiki/treebase/index.php?title=Deployment_by_a_sysadmin . If your local or 6666 deployment relies on the WAR-supplied context.xml, you'd need to update it according to the updated treebase-web/src/main/webapp/META-INF/context.xml.example. As you are into the mesquite matters at the moment, I'd like to re- raise the suggestion to drop Mesquite code from SVN (see the forward below). --VG Begin forwarded message: > From: Vladimir Gapeyev <vla...@du...> > Date: February 7, 2010 4:41:35 PM EST > To: TreeBASE Developers <Tre...@li...> > Subject: [Treebase-devel] Get rid of treebase--core/lib ? > > After the re-configuration of server-side access to Mesquite, is there > any remaining need for the Mesquite unpacked under treebase-core/ > lib? My builds appear to be fine both under 'mvn package' and under > Eclipse. > > I'd then suggest removing this Mesquite code from SVN. And, as we are > up for that, would it make sense to clear the whole lib directory? > I.e., is there anything important there? DB2 drivers in lib/ibm are > useless now. What about lib/jars? > > --Vladimir |