DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12489>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12489 Setting JSP as template engine still uses velocity components ------- Additional Comments From [EMAIL PROTECTED] 2002-09-10 17:23 ------- I assume that you set services.TemplateService.default.extension=jsp in tr.props. That has some side-effects right now but the portal should still work for the most part. There's an outstanding task of bringing JSP templates in par with Velocity. This is no small task. This hasn't been a priority probably because there was no real "cry" for better JSP support until recently (I may be wrong about that though). Why do you want to completely disable Velocity? If you want to be able to publish JSP content as portlets you can still achieve that while keeping Velocity as default template engine. You just have to always reference your templates with .jsp extension. Can you be more specific about your reasons to shut off Velocity? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
