I'm interested in specifying config, config-transform and XSLs outside of war/ear 
file, i.e. in ability to have them unpacked in a file system under project root and 
updating of maverick without rebuilding of war/ear file during development.
I think that the best solution to the problem is factoring out all access to file 
resources in a single place and adding check for config parameter specifying www-root 
in a file system when accessing a resource there. This check was done in a piece of 
code I posted to this list earlier. I think that the variable "xslDir" used there 
should be renamed to "fileWwwRoot" or smth and given that semantics.
I've read discussion about reloading of xsl files only when they are changed in early 
letters of this list discussing preload of xsls, but I cannot figure out how can I use 
this feature because when I change xsl I have to rebuild ear/war and redeploy it. It 
results in restarting of whole web app by container and all xsl files are reloaded 
regardless of wheteher they were changed or not. If it is possible to avoid it, could 
you, please, advise me how?

Cheers,
Yura.
----- Original Message ----- 
From: "Schnitzer, Jeff" <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> 
To: <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> 
Sent: Thursday, February 13, 2003 3:19 AM 
Subject: RE: [Mav-user] Specifying external maverick.xml 

> Heh, yeah, that's what I thought :-)
> 
> I'll explicitly check for file:, http:, and ftp:. Should have that
> checked in tonight.
> 
> Jeff
> 
> > -----Original Message-----
> > From: Dan Finkelstein [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, February 12, 2003 4:04 PM
> > To: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
> > Subject: RE: [Mav-user] Specifying external maverick.xml
> > 
> > Thanks for the update, but I couldn't get the new code to work, maybe
> > that's what you meant by not supporting the file stuff yet ! <grin>
> > 
> > I was trying to set enter something like:
> > 
> > getServletContext().setAttribute(Dispatcher.KEY_CONFIG_FILE,
> > "<file:///whatever/maverick.xml>");
> > 
> > I think that if you add a check for the string starting with
> "file://",
> > and
> > then call new URL(filepath) instead of getResource(), it would be
> > fine. Make sense?
> > 
> > Best,
> > Dan
> > 




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
[INVALID FOOTER]

Reply via email to