You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Eduardo Lobo <el...@inet.co.cr> on 2004/07/30 19:53:54 UTC
Could not find template for component Home/$Border in locale en_US
The Border.jwc is under in the WEB-INF section of the war file. Border.html is in the context-root.
Why Tapestry desn't finds the html template of the component?
The Page's templates are too in the context-root, but this ones have no problem, and component's templates do.
Thanks.
Re: Global vs Engine
Posted by "Julio C. Rivera" <ju...@ya.com>.
See
http://jakarta.apache.org/tapestry/doc/TapestryUsersGuide/intro.engine-service-visit.html
http://jakarta.apache.org/tapestry/doc/TapestryUsersGuide/state.engine.html
http://jakarta.apache.org/tapestry/doc/TapestryUsersGuide/state.global.html
Summary:
Global is a singleton, common to all user sessions. It stores global
application information and implements global application behaviour.
There is an Engine instance for every user session (it is stored in the
HttpSession).
At 13:03 30/07/2004 -0700, you wrote:
>Hello,
> I am not sure when to use the Global class and my Engine class. Can
>someone please tell me what is intended to be implemented in each? They are
>both singletons aren't they?
>
>Joe
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: Component page listeners
Posted by Shawn Church <sh...@boxity.com>.
No, since the problem is not related to rewind. The problem is that if
I have 10 components contained by a page, and each component is
registered as a page listener, the pageBeginRender of each of the 10
components are invoked, even if the component itself is not rendered in
the page (due to a conditional, etc.).
Shawn
Quoting "Filip S. Adamsen" <fi...@stubkjaer-adamsen.dk>:
> Would something like
>
> public void pageBeginRender(PageEvent event) {
> if (!event.getRequestCycle().isRewinding()) {
> // do your thing here
> }
> }
>
> do the trick?
>
> -----Original Message-----
> From: Shawn Church [mailto:shawn@boxity.com]
> Sent: Friday, July 30, 2004 11:41 PM
> To: Tapestry users
> Subject: Component page listeners
>
> [...]
>
> Any ideas? I am really just trying to initialize my component
> properties, but only if the component will actually get rendered.
>
> Thanks,
> Shawn
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: Component page listeners
Posted by "Filip S. Adamsen" <fi...@stubkjaer-adamsen.dk>.
Would something like
public void pageBeginRender(PageEvent event) {
if (!event.getRequestCycle().isRewinding()) {
// do your thing here
}
}
do the trick?
-----Original Message-----
From: Shawn Church [mailto:shawn@boxity.com]
Sent: Friday, July 30, 2004 11:41 PM
To: Tapestry users
Subject: Component page listeners
[...]
Any ideas? I am really just trying to initialize my component
properties, but only if the component will actually get rendered.
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Component page listeners
Posted by Shawn Church <sh...@boxity.com>.
I have a set of components which are contained in a single page, each
of which are conditionally rendered depending on the application
state. Each of these components implements PageRenderListener, and I
have realized that pageBeginRender is invoked in each component on
every page cycle, regardless of whether the component is ultimately
rendered or not (based on the conditions in the containing page).
I'm sure this is happening since each of the components are contained
by a parent page, and they are registered as page listeners. I found
an archived message about this (someone wanting a
componentRenderListener), but I'm not sure how/if it was resolved.
I tried replacing pageRenderListener with prepareForRender, but the
page is locked by this point so I'm not able to change any of the page
properties (or properties of my components which are contained by the
page).
Any ideas? I am really just trying to initialize my component
properties, but only if the component will actually get rendered.
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Global vs Engine
Posted by Jamie Orchard-Hays <ja...@dang.com>.
Unless you need a custom engine (probably not), you'll never touch it.
Global is the object where you put items you want accessable to all pages in
your application.
----- Original Message -----
From: "Joe Andolina" <jo...@andomation.com>
To: "'Tapestry users'" <ta...@jakarta.apache.org>
Sent: Friday, July 30, 2004 4:03 PM
Subject: Global vs Engine
> Hello,
> I am not sure when to use the Global class and my Engine class. Can
> someone please tell me what is intended to be implemented in each? They
are
> both singletons aren't they?
>
> Joe
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Global vs Engine
Posted by Joe Andolina <jo...@andomation.com>.
Hello,
I am not sure when to use the Global class and my Engine class. Can
someone please tell me what is intended to be implemented in each? They are
both singletons aren't they?
Joe
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Could not find template for component Home/$Border in locale en_US
Posted by stephen smithstone <sk...@lchost.co.uk>.
i find that the component templates have to be in the WEB-INF as well
not sure if you can set it in the .application file thou
On 30 Jul 2004, at 19:47, Mikaël Cluseau wrote:
> Eduardo Lobo wrote:
>> The Border.jwc is under in the WEB-INF section of the war file.
>> Border.html is in the context-root. Why Tapestry desn't finds the
>> html template of the component?
>> The Page's templates are too in the context-root, but this ones have
>> no problem, and component's templates do.
>> Thanks.
>
> It is specified to be like that. But you can redefine template
> locations using the $template asset in each component...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Could not find template for component Home/$Border in locale
en_US
Posted by Mikaël Cluseau <nw...@nwrk.dyndns.org>.
Eduardo Lobo wrote:
> The Border.jwc is under in the WEB-INF section of the war file. Border.html is in the context-root.
>
> Why Tapestry desn't finds the html template of the component?
>
> The Page's templates are too in the context-root, but this ones have no problem, and component's templates do.
>
>
> Thanks.
It is specified to be like that. But you can redefine template locations
using the $template asset in each component...
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org