You can specify a url to the maverick config file as an init param to the Dispatcher servlet (see http://mav.sourceforge.net/maverick-manual.html#N100CB). This url gets passed to ServletContext.getResource().
I'm really not entirely certain what you can get away with - try putting file://path/to/wherever.xml in there. If that doesn't work, perhaps we should add code to fallback to Class.getResource() if ServletContext.getResource() fails? Dan, if you want to test this out, Dispatcher.loadConfigDocument() is trivial to modify. If you find something that works, I will be happy to commit a patch. Jeff Schnitzer [EMAIL PROTECTED] > -----Original Message----- > From: Dan Finkelstein [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 23, 2003 7:33 PM > To: [EMAIL PROTECTED] > Subject: [Mav-user] Specifying external maverick.xml > > Hi -- > > I'm interested in being able to specify a maverick.xml file that is > located > outside the war file. Right now, it is pulled from within the war and I > want to specify a different one "on-the-fly" so to speak. For example, is > there a call that I could make, like > Maverick.iniitalize(maverick_xml_file)? Or another way to do this? > > Thanks in advance, > Dan > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > [INVALID FOOTER] ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com [INVALID FOOTER]
