Hi Kalle,
The key to it is this snippet: "if the stuff you are setting up is not
needed for component event requests, consider putting it elsewhere".
If I understand your example correctly, the object you are creating IS
needed for a component event request so DO put it in onActivate(...).
Hi Kalle,
It looks like you need to use onActivate() in your case. Could you
give us a sample code, so we can understand you better?
Regards, Sergey.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional
On Tue, Sep 1, 2009 at 9:50 PM, Geoff
Callender wrote:
> Good question. Yes, it does still seem to me to be best practice and no, I
> don't see it breaking the back button. Can you give an example?
Assuming you use something else than session or client persistence and
you initialize (create) an ob
That looks very reasonable. I think I will adopt this approach. Thanks
Geoff.
Benny
On Wed, Sep 2, 2009 at 1:02 AM, Geoff Callender <
geoff.callender.jumpst...@gmail.com> wrote:
> Yes, let's hope the doco is updated soon!
>
>https://issues.apache.org/jira/browse/TAP5-812
>
> As for your
Yes, let's hope the doco is updated soon!
https://issues.apache.org/jira/browse/TAP5-812
As for your conundrum, is there a reason you're not happy to do the
following? It's only a few lines and its intention seems very clear.
@Component(id = "searchForm")
private Form
Hi Kalle,
Good question. Yes, it does still seem to me to be best practice and
no, I don't see it breaking the back button. Can you give an example?
Regards,
Geoff
On 01/09/2009, at 8:37 AM, Kalle Korhonen wrote:
Hey Geoff,
I recall reading at some point that you had recommended not usin
Thanks for alerting me, Geoff. But even the input validation example in the
User Guide shows recording error in onSuccess()! I must say I'm a bit
alarmed by these "quirks". I hope I don't find too many more surprises when
I get deeper into Tapestry 5.1. I am working on a critical application under
Beware, there's a long-standing problem with recording errors in
onSuccess().
https://issues.apache.org/jira/browse/TAPESTRY-1972
Geoff
On 02/09/2009, at 7:59 AM, Benny Law wrote:
Thanks Sebastian. I agree that only business logic related
validation should
go into onSuccess, and I
In a nutshell, the way I did it was to implement IAsset for each
dynamic chart which then gets fetched by component id in the
IEngineService and asked to render itself to the given WebResponse.
Or put another way...
I have 2 dynamic chart images In my Foo.html page definition:
image="ognl:c
Generally, it is necessary to include some kind of id in the URL (as
context) that you can get back when handling the request. Using a
persistent page property is insufficient, since it will be "left" in
the value of the final rendering of the tag, which is kind of
what you are seeing.
This is m
Thanks Sebastian. I agree that only business logic related validation should
go into onSuccess, and I would leave basic field validations to validators
as much as possible. My problem with onValidateForm is still the amount of
code I need to write to check for existing errors before I can do cross
Hi,
I am trying "excercise" my t5 components library with testify. I
created a simple page which will contain the component to test. For
now, it contains only plain html. I am getting this error when running
mvn test
Caused by: java.lang.RuntimeException: Base class
com.formos.tapestry.testify.te
Hello,
the intended validation method for cross field validation is
onValidateForm
The onSuccess is probable the latest point to do validation. I would
only place business logic related validation in there
You may do field validation in the onValidateForm as well but it is
normally simpler, f
Hi Geoffrey (and others),
Did you ever figure out a workaround for this issue? I have:
...
Enter E-mail Address
And when I record e-mail address problems in the form, the t:errors
never renders (unless I reload the page as you said). At this point,
I'll eith
"Mark W. Shead" wrote on 28/08/2009 21:36:55:
> Hm it appears to give me a copy of the registry, but not the same
> instance that was used for testing the pages.
I'm not too sure what you mean by "not the same instance that was used for
testing the pages" but I'm going to guess that you are ru
Thanks Guys,
Works very well!
Newton
Thiago H. de Paula Figueiredo wrote:
>
> Em Tue, 01 Sep 2009 11:43:45 -0300, newtonik
> escreveu:
>
>> Hey,
>
> Hi!
>
>> Has anyone been able to figure out a way to use the FCKEditor in a ajax
>> form submission. It seems like the data in the editor d
Em Tue, 01 Sep 2009 11:43:45 -0300, newtonik escreveu:
Hey,
Hi!
Has anyone been able to figure out a way to use the FCKEditor in a ajax
form submission. It seems like the data in the editor doesn't get
assigned during a ajax submit. This prevents me using formzone when I
have fckeditor
newtonik schrieb:
Hey,
Has anyone been able to figure out a way to use the FCKEditor in a ajax form
submission. It seems like the data in the editor doesn't get assigned during
a ajax submit. This prevents me using formzone when I have fckeditors
textarea. Has anyone worked around this issue? T
Hey,
Has anyone been able to figure out a way to use the FCKEditor in a ajax form
submission. It seems like the data in the editor doesn't get assigned during
a ajax submit. This prevents me using formzone when I have fckeditors
textarea. Has anyone worked around this issue? Thanks.
Newton
--
bdumeny a écrit :
Read the Grid component documentation:
http://tapestry.apache.org/tapestry5.1/tapestry-core/ref/org/apache/tapestry5/corelib/components/Grid.html
Take a look at the index and the row parameters.
Thx,
but indexRow isn't the arrayList index... How to link them?
I have
Read the Grid component documentation:
http://tapestry.apache.org/tapestry5.1/tapestry-core/ref/org/apache/tapestry5/corelib/components/Grid.html
Take a look at the index and the row parameters.
Thx,
but indexRow isn't the arrayList index... How to link them?
check the urls to the images... is it possible they're all the same?
On Tue, Sep 1, 2009 at 2:28 PM, chitraa wrote:
>
> Tapestry 4.
>
> Thank you.
>
>
>
> Howard Lewis Ship wrote:
>>
>> Tapestry 4 or Tapestry 5?
>>
>> On Sun, Aug 30, 2009 at 6:59 PM, chitraa wrote:
>>>
>>> Hi,
>>>
>>> Did you mana
Tapestry 4.
Thank you.
Howard Lewis Ship wrote:
>
> Tapestry 4 or Tapestry 5?
>
> On Sun, Aug 30, 2009 at 6:59 PM, chitraa wrote:
>>
>> Hi,
>>
>> Did you manage to find a solution to this? I am also trying to render
>> multiple chart images into the same page. However, the service renders
>>
Szemere Szemere wrote on 27/08/2009
16:14:16:
> Excuse my ignorance, does Testify work with Tapestry 5.0.18? The current
> version of Testify seems to require Tapestry 5.1.05. Is there a version
> that works with 5.0.18>
Sorry - Testify uses some features of the Tapestry 5.1 IOC container to
d
https://issues.apache.org/jira/browse/TAP5-711
On 01.09.2009 09:27 schrieb Oliver Bauer:
Sorry for the missing subject
Hello,
i have some problems with the submit component and the parameter t:image.
The following works fine with T5.1.0.5
and as expected the following methods are cal
Sorry for the missing subject
> Hello,
>
> i have some problems with the submit component and the parameter t:image.
> The following works fine with T5.1.0.5
>
>
>
>
>
> and as expected the following methods are called
>
> @OnEvent(component="viewselection", value = EventConstants.SELECT
Hello,
i have some problems with the submit component and the parameter t:image.
The following works fine with T5.1.0.5
and as expected the following methods are called
@OnEvent(component="viewselection", value = EventConstants.SELECTED)
void someMethodName() {
logger.debug("With EventC
27 matches
Mail list logo
