Le vendredi 27 juillet 2007 à 14:02 -0700, Nathan Bubna a écrit :
> None that i know of.
> 
> Perhaps you can extend the Include directive to change it's name (to
> #import() or something, then do as Claude suggested and drop the
> orginal from the default directive.properties and add your renamed
> directive as well.

Yes, renaming it is one solution. Or escaping the # (-> \#include).

Using comments cannot work since apache won't see them.


  Claude


> On 7/27/07, White, Tim <[EMAIL PROTECTED]> wrote:
> > Right...I still want to be able to do includes.  I wonder if there is a way 
> > to disable them if they are inside comments?
> >
> > -----Original Message-----
> > From: Claude Brisson [mailto:[EMAIL PROTECTED]
> > Sent: Friday, July 27, 2007 2:50 PM
> > To: Velocity Users List
> > Subject: Re: Ignoring/rewriting SSI commands with VelocityLayoutServlet
> >
> > Maybe by globally disactivating the #include directive? It is declared in 
> > the file org/apache/velocity/runtime/defaults/velocity.properties.
> >
> >
> >   Claude
> >
> > Le vendredi 27 juillet 2007 à 12:31 -0600, White, Tim a écrit :
> > > So, I'm trying out an idea that would let us serve all our existing
> > > .html pages with VelocityLayoutServlet, instead of with with straight
> > > Apache.
> > >
> > > The problem is, a lot of our existing .html pages have Server Side
> > > Includes in them like this:
> > >
> > > <!--#include
> > > virtual="/global/includes/residential/resInGlobalScript.html"-->
> > >
> > > Ideally, I'd like velocity to handle these without changing the .html
> > > files, since there are around 10,000 of them.
> > >
> > > At minimum, I'd at least like Velocity to ignore it, rather than
> > > trying to process it as a velocity #include().
> > >
> > > Any ideas?
> > >
> > > Tim
> > >
> > >
> > > This communication is the property of Qwest and may contain
> > > confidential or privileged information. Unauthorized use of this
> > > communication is strictly prohibited and may be unlawful.  If you have
> > > received this communication in error, please immediately notify the
> > > sender by reply e-mail and destroy all copies of the communication and 
> > > any attachments.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to