Hi, I've got myself into a tight little knot trying to work out how to "short-circuit" them templating mechanism. What I have is an application developed with Velocity and Turbine. During the execution of one of my VelocityActions (a type of ActionEvent) I want to divert the output mechanism so that it runs some code that will set the response type to something other than text/html and generate that output (in effect, supersede the templating mechanism from within Turbine). So, for example, I might have an ActionEvent that usually runs the normal templating mechanism but in special circumstances it should instead cause the verbatim contents of a file residing in the server's filesystem to be output via the HTTP response. I have had trouble trying to work out how to fit within the org.apache.turbine.modules.Page/org.apache.ecs.Document and Screens/Service structure that Turbine uses. I thought I might be able to subclass Page and Document to achieve what I want, but got confused in the process of trying to work out how to approach this. An alternative option is to HTTP redirect the user to a different servlet that does what I want. However, then what am I supposed to do about the Turbine ACLs (other than reimplement...)? So...has anyone thought about this sort of thing before and if so, what are the best strategies? (If my description has not been sufficient I will repost something better if I can think of how to express it.) Thank you. PS. If there is an FAQ I couldn't find it at jakarta.apache.org:8080/jyve... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
