Thanks - setupRender() did it. I wasn't aware of the order of calling,
but it makes sense now that you mention it (I understand the rendering
is totally from page activation). Thanks for the clarification :)
Howard Lewis Ship wrote:
onActivate() (i.e., the "activate" event) is not part of rend
onActivate() (i.e., the "activate" event) is not part of rendering, it comes
very early in the request handling process.
I think you want to do something more like beginRender() or even
setupRender().
On 9/30/07, Chris Lewis <[EMAIL PROTECTED]> wrote:
>
> FYI I just upgraded to 5.0.6-SNAPSHOT wit
FYI I just upgraded to 5.0.6-SNAPSHOT with the same results.
Howard Lewis Ship wrote:
Could we see your Start page?
On 9/28/07, Chris Lewis <[EMAIL PROTECTED]> wrote:
I'm creating something like DocumentScriptBuilder for inserting
stylesheets, much like DocumentScriptBuilderImpl does for j
My Start.java follows - note that *themes.default* is a symbol
contributed in my app module. It is valid as I am able to inject and
access it via a getter.
package com.propertypix.www.pages;
import org.apache.tapestry.Asset;
import org.apache.tapestry.annotations.Environmental;
import org.apac
Could we see your Start page?
On 9/28/07, Chris Lewis <[EMAIL PROTECTED]> wrote:
>
> I'm creating something like DocumentScriptBuilder for inserting
> stylesheets, much like DocumentScriptBuilderImpl does for javascripts. I
> have this method in my app module, inspired by the method in
> Tapestry
I'm creating something like DocumentScriptBuilder for inserting
stylesheets, much like DocumentScriptBuilderImpl does for javascripts. I
have this method in my app module, inspired by the method in TapestryModule:
public void
contributePageRenderInitializer(OrderedConfiguration
configurati
