I think that's a Velocity thing and not a Maverick thing. Try this in
your template:
$response.setContentType('text/plain')
-dk
On Sunday, August 24, 2003, at 03:49 PM, Dan Finkelstein wrote:
Hi --
I know this is a really dumb question, esp considering that I've been
using and relying on
Hmmm. I have the following in my web.xml and it works just fine:
welcome-file-list
welcome-fileindex.vm/welcome-file
/welcome-file-list
*.vm is mapped to the VelocityLayoutServlet in my webapp's web.xml.
I would expect a specification of 'index.m' to work as well, since it's
just running the
AFAICS, Tomcat (at least 4.1.18) has its own commons-beanutils.jar in
its server/lib. It could conflict with the one you added to Tomcat
classpath.
The jars in Tomcat's server/lib directory are not visible from webapps.
However, the jars in common/lib and shared/lib are.
The problem may not be directly with the BeanUtils class, but rather a
class it imports. For all of our installations, we have the following
commons jars in every webapp's WEB-INF/lib directory:
commons-beanutils
commons-collections
commons-lang
commons-logging
Actually, that's a bit of a
Hmmm...I don't want to rain on any parades, but I'm just wondering why
you didn't want to use Velocity, as it accomplishes the same thing and
it's already written and well-supported?
--doug
---
This SF.Net email is sponsored by BEA Weblogic
Indeed, the solution presented below is best, because then the browser
will just cache the entire .js file.
However, I've had problems using the XML shortcut for empty tags in
this particular case, so always do script src=.../script
Cheers,
doug
On Sep 1, 2004, at 4:49 PM, jim moore wrote:
Why