> I switched to using the > VelocityScreen/VelocityOnlyLayout and it works correctly.
I was wrong, this does not work correctly. All content that is generated by $jetspeed.getPane() is rendered above the all of the layout's markup when using VelocityOnlyLayout. I am wondering if this means that the ConcreteElement returned by $jetspeed.getPane(), is being directly added to the output stream, but this is only a guess. Is there a work-around or fix for this rendering issue? Scott > -----Original Message----- > From: Weaver, Scott [mailto:[EMAIL PROTECTED]] > Sent: Monday, July 01, 2002 9:04 AM > To: 'Jetspeed Users List' > Subject: VelocityDirectLayout does not allow recognize RunData.setLayoutTe > mplate() > > This is probably more of a Turbine issue then a Jetspeed. > > > > Has anyone noticed that RunData.setLayoutTemplate() does not work when > using > (the default in 1.3a3) settings VelocityDirectLayout and > VelocityDirectScreen in TR.props. I switched to using the > VelocityScreen/VelocityOnlyLayout and it works correctly. I looked at the > doc for the VelocityDirect* classes and there is no mention of this being > a > restriction. Anybody have any idea on this one. > > > > Thanks, > > Scott
