I've been using Spring MVC for about a year with JSP/JSTL (unfortunately; decision out of my hands). There are many great things about it, but despite all its flexibility and features, it occasionally suffers from do-too-much-for-you problems that make it hard to do things different than prescribed.
All that said, I have not as yet used their Velocity integration, so i don't know the best way to get the VelocityEngine their view class is using. I'm guessing you've seen that you can get the VelocityEngine in a subclass of VelocityView http://www.springframework.org/docs/api/org/springframework/web/servlet/view/velocity/VelocityView.html but i don't know that that will get it for you at the point you need it during a request. if not, my initial reaction is to just encourage to configure your own VelocityEngine using the same properties/config as the one Spring does, if possible. Using the same properties/config should keep things rendering the same. does that help? On 8/21/06, Bill Rishel <[EMAIL PROTECTED]> wrote:
Within Struts I've been using a velocity engine from within a subclass of VelocityViewServlet with which I am able to call evaluate(Context context, java.io.Writer out, java.lang.String logTag, java.lang.String instring) to render the vtl in the 'instring'. Because I am doing my own preprocessing before that call and possibly after I need that kind of fine grained control of the vtl rendering. I am moving now to Spring, which gives me some important features, but haven't been able to figure out how to do the "hand rendering" of the vtl within a Spring controller. Any suggestions on how to do that? Bill Rishel --------------------------------------------------------------------- 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]
