velocity-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Gaspar" <paulo.gas...@krankikom.de>
Subject RE: They used Velocity (www.onjava.com)
Date Thu, 02 May 2002 11:47:09 GMT
> How are you restricting access to the ClassLoader?  We've been
> worrying about $ref.getClass().getClassLoader() ...
> 
> I'm unsure how to draft a policy file which only applies to Velocity.

Well, that is not a problem at my company.

But you probably could use the new custom introspection to take care
of that. 

(Right Geir???)

Hmmm, that thing is even more useful than I thought!
=:o)


Have fun,
Paulo Gaspar


> -----Original Message-----
> From: dlr@despot.finemaltcoding.com
> [mailto:dlr@despot.finemaltcoding.com]On Behalf Of Daniel Rall
> Sent: Thursday, May 02, 2002 11:25 AM
> To: Velocity Developers List
> Cc: paulo.gaspar@krankikom.de
> Subject: Re: They used Velocity (www.onjava.com)
> 
> 
> "Paulo Gaspar" <paulo.gaspar@krankikom.de> writes:
> 
> > They were wise.
> >
> > At my company Velocity was the only templating mechanism that the
> > designers really enjoyed and used with no problems and almost with
> > no help... and we tried several.
> >
> > (BTW: I think XSLT was the most hated.)
> >
> >
> > We to are planning to give customer control to some templates on
> > some sites. Can you guess what is the obvious template engine
> > choice?
> 
> How are you restricting access to the ClassLoader?  We've been
> worrying about $ref.getClass().getClassLoader() ...
> 
> I'm unsure how to draft a policy file which only applies to Velocity.
> 

--
To unsubscribe, e-mail:   <mailto:velocity-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:velocity-dev-help@jakarta.apache.org>


Mime
View raw message