Sorry, I forgot
Tapestry version: 5.1.0.5
Browser: Firefox
Valentin Yerastov wrote:
>
> Hello users and developers!
>
> I have template:
>
> ${value}
> UPDATE
>
> And page class:
>
> @Persist
> private int value;
>
> @InjectComponent("output")
> private Zone output;
>
> @Inject
>
Hello users and developers!
I have template:
${value}
UPDATE
And page class:
@Persist
private int value;
@InjectComponent("output")
private Zone output;
@Inject
private Request request;
public Object onActionFromUpdate() {
value++;
if (request.isXHR()) {
Tapestry 5.1 is really good about tracking what it was doing when one
of these exceptions occur. Check the console, as Sven pointed out.
On Thu, May 14, 2009 at 4:20 AM, Sven Homburg wrote:
> have a look at your console output.
> may be there ist another exception in front of the shown exception
Ben Gidley has done a detailed analysis of Tapestry 5 performance He
used some quite reasonable assumptions, including running tests for
over an hour to gauge memory use over time. His conclusion is that
Tapestry performance is excellent, which is a relief if not a surprise.
What I'm really pleased
Thanks for the great work; I think these were pretty great results.
On Thu, May 14, 2009 at 10:41 AM, Ben Gidley wrote:
> Hi,
> As I posted a few weeks back I have been running a series of load tests and
> have come to the following key conslusions
>
> - *Tapestry is fast* - the response times
Em Thu, 14 May 2009 15:32:20 -0300, Borut Bolčina
escreveu:
My intention was that page selects its own layout, not which block gets
rendered. I am using the block and delegate for other purposes. If the
layouts don't differ much then one can use parameters for the layout and
then conditionall
My intention was that page selects its own layout, not which block gets
rendered. I am using the block and delegate for other purposes. If the
layouts don't differ much then one can use parameters for the layout and
then conditionally renders parts of the layout so it looks different. I
wanted to h
Hi,
As I posted a few weeks back I have been running a series of load tests and
have come to the following key conslusions
- *Tapestry is fast* - the response times even under load are low. It
isn't alway's fastest solution but it is sufficiently fast for me to focus
my tuning attention e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Geoffrey,
The documentation for Tapestry 5.1 is at
http://tapestry.apache.org/tapestry5.1, not
http://tapestry.apache.org/tapestry5.
I believe this is what you're looking for:
http://tapestry.apache.org/tapestry5.1/guide/propexp.html
/Filip
On 2
I seem to recall hearing somewhere that T5.1 has support for easily binding
parameter values to a List in a component. I can't find anything about it
in the release notes or documentation, so I'm starting to think I imagined
it. Is this ringing a bell for anyone?
- Geoffrey
--
Geoffrey Wisema
On Thu, May 14, 2009 at 7:12 AM, Borut Bolčina wrote:
> You probably mean that I would have one layout component, but with
> conditional blocks and not several layouts chosen dynamically?
Not exactly. You can define one block per layout and use delegate to
render one of them. The choosing logic s
> Again Yuri you have not posted the relevant code, but at a guess
it is the most relevant i have except the JS part :)
> this is likely where you are going wrong:
>>where "info" constructs server url from request
for Ajax i think i must give full url and not the one with only
context path (without
have a look at your console output.
may be there ist another exception in front of the shown exception
with regards
Sven Homburg
Founder of the Chenille Kit Project
http://www.chenillekit.org
2009/5/13 Christine
> After upgrading to 5.1, I get the error below. Apparently, there's an
> error
Again Yuri you have not posted the relevant code, but at a guess this is likely
where you are going wrong:
>where "info" constructs server url from request
Your link object should probably be constructing the relevant context for your
link, and not from the request:
Link el = componentResource
Something like that, yeah.
Am 14.05.2009 12:12 schrieb Borut Bolčina:
You probably mean that I would have one layout component, but with
conditional blocks and not several layouts chosen dynamically?
-Borut
2009/5/14 Ulrich Stärk
Maybe a Delegate can help you here.
Uli
Am 14.05.2009 10:45
thank you for the great tip :)
> This is possible, isn't it?
>
> @InjectComponent
> private Zone myZone;
> public String getCurrentZoneId() {
> return "somethingUnique";
> }
> myZone will be treated like a normal component id by tapestry, and makes it
> possible to inject the zone in the clas
ok.
The component has:
@SuppressWarnings("unchecked")
public StreamResponse onGetChildren(Long watcherId, Long domId) {
...}
as component event. Hence, 2 context params
links are created like that:
Link el = componentResources.createEventLink("getchildren");
renderSupport
You probably mean that I would have one layout component, but with
conditional blocks and not several layouts chosen dynamically?
-Borut
2009/5/14 Ulrich Stärk
> Maybe a Delegate can help you here.
>
> Uli
>
> Am 14.05.2009 10:45 schrieb Borut Bolčina:
>
> Hi,
>>
>> I am trying to set the layo
Thanks to all! It`s work!
Inge Solvoll wrote:
>
> This is possible, isn't it?
>
>
>
> @InjectComponent
> private Zone myZone;
>
> public String getCurrentZoneId() {
> return "somethingUnique";
> }
>
> myZone will be treated like a normal component id by tapestry, and makes
> it
> possibl
Maybe a Delegate can help you here.
Uli
Am 14.05.2009 10:45 schrieb Borut Bolčina:
Hi,
I am trying to set the layout dynamically, but I guess this can not be done.
The t:type="${layout}" does not get expanded to whatever I set in
Index.java.
PageWithLayout.tml
===
http://tapestry.
Hi,
I am trying to set the layout dynamically, but I guess this can not be done.
The t:type="${layout}" does not get expanded to whatever I set in
Index.java.
PageWithLayout.tml
===
http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";>
page with ${layout}
PageWithLayout.java
=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You should use an EventLink instead - that's what they're for. :)
/Filip
Yury Luneff skrev:
> Hello, users.
>
> Is there a way to separate activation contexts for page and its
> components?
>
> I wrote a component that uses AJAX to interact from cl
This is possible, isn't it?
@InjectComponent
private Zone myZone;
public String getCurrentZoneId() {
return "somethingUnique";
}
myZone will be treated like a normal component id by tapestry, and makes it
possible to inject the zone in the class.
On Thu, May 14, 2009 at 9:08 AM, Yury Luneff
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
The documentation has been updated to reflect most, if not all, of the
changes. Template inheritance etc. is described here, at the bottom:
http://tapestry.apache.org/tapestry5.1/guide/templates.html
/Filip
On 2009-05-14 08:04, Peter Stavrinide
well, as for template -- it should work (not so much time need for
checking). as for zones injection in the page... well, i guess you
need to find a way of not injecting zones, there are different
possibilities that might work for you.
> How can I generate dynamic ID for zone?
> Can I use somethin
Hi Yury,
Please post some code, it will be easier to guide you.
Peter
- Original Message -
From: "Yury Luneff"
To: users@tapestry.apache.org
Sent: Wednesday, 13 May, 2009 18:59:20 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: page & components activation contexts
Hello, user
26 matches
Mail list logo
