>
> Could this by any chance have anything to do with the
> infamous "layoutsnull" problem? I somehow recall seeing
> a double (back)slash somewhere...
>
> --
> Gonzalo A. Diethelm
> [EMAIL PROTECTED]
Not likely. The layoutsnull problem is most generally related to using
the "screen" parameter key as opposed to the "template" keyword while
trying to use the template related java modules. You cannot use the
WebMacro*Layout's or Velocity*Layout's without specifying the layout
template to use. This is done automatically by "name association" if
you specify the screen template using the template keyword, if you
specify the java module using the screen keyword, you need to make sure
you set the layout template specifically, if you intend to use templates
for layouts. Though if you are using a template system, I do not see
many reasons to explicitely specify the Screen while also wanting to use
a layout. Generally a direct reference to the Screen would be for cases
like building a binary response stream and the Layout should be set to
null.
It is okay to define the Layout module for a Screen to be null. Then
the results of the Screen are returned.
It is not okay to define the Layout module to be one of the template
Layouts and then to not define a layout template that they can use.
This is the layoutsnull problem.
John McNally
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
