I hate to say it but I also ran into a similar problem and it made me rethink how my pages were laid out to begin with.
If you need to include parts of code routinely, look at making a navigation with the code segments, and then using the layout to organise these navigations. You should try to limit the screen class to one per page to help keep the logical connection to your java screen classes. Navigations can access all the same information held in the session that the screen class has access to, so you aren't loosing out on the functionality of a screen class by moving some of your logic out to navigations. just a thought. Jeff Painter On Thu, 17 Jun 2004, Ilan Azbel wrote: > I have checked that the file I try to include renders correctly when I call > it on its own. But I get one of those useless Velocity error message that > doesn't provide any info when I use #parse. > > I get the same error when I use #include > > Any ideas? > > > > > > > -----Original Message----- > > From: David Demner [mailto:[EMAIL PROTECTED] > > Sent: 17 June 2004 04:20 > > To: 'Turbine Users List' > > Subject: RE: processing a .vm file within another .vm file > > > > > > Hi Ilan, > > > > You can use the #parse("other.vm") velocity directive. > > > > See http://jakarta.apache.org/velocity/user-guide.html#Parse for more > > information. > > > > Good luck, > > > > David > > > > -----Original Message----- > > From: Ilan Azbel [mailto:[EMAIL PROTECTED] > > Sent: Thursday June 17, 2004 7:17 AM > > To: Turbine Users List > > Subject: processing a .vm file within another .vm file > > > > > > Hello, > > > > I am using turbine with velocity. > > > > I have certain pieces of velocity code that are used throughout my > > application. I have put these common pieces of code into many > > different .vm > > files. > > > > I now have a need to "include" these .vm files inside other .vm files. How > > can I do this? I am not sure which turbine object to use. > > > > Ilan > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
