Em Wed, 15 Oct 2008 12:48:13 -0300, Jecki <[EMAIL PROTECTED]> escreveu:
OMG, 2 days of efforts (or even more) for this trivial thing. shame on
us :( and the credit goes to Thiago.
That's why mailing list and forums exist: you help a little, you get
helped a little. :)
--
Thiago H. de Paula
OMG, 2 days of efforts (or even more) for this trivial thing. shame on
us :( and the credit goes to Thiago.
On Wed, Oct 15, 2008 at 11:31 PM, moritzgilsdorf
<[EMAIL PROTECTED]> wrote:
>
> THANKS!! That was it!
>
> I knew it must be something trivial.
>
Em Wed, 15 Oct 2008 12:31:15 -0300, moritzgilsdorf
<[EMAIL PROTECTED]> escreveu:
THANKS!! That was it!
You're welcome! :)
I knew it must be something trivial.
That should maybe be a Tapestry #1 rule: You must use t:id to give an id
to a component, not id (without the t: prefix). By the
THANKS!! That was it!
I knew it must be something trivial.
Thiago H. de Paula Figueiredo wrote:
>
> Em Wed, 15 Oct 2008 12:16:13 -0300, moritzgilsdorf
> <[EMAIL PROTECTED]> escreveu:
>
>> Thanks for the reply.
>>
>> I tried several types of namings, including your proposal. The method i
Em Wed, 15 Oct 2008 12:16:13 -0300, moritzgilsdorf
<[EMAIL PROTECTED]> escreveu:
Thanks for the reply.
I tried several types of namings, including your proposal. The method is
only started when I change it for example to onAction().
A little desperate guess: try t:id="reset" instead of id=
Thanks for the reply.
I tried several types of namings, including your proposal. The method is
only started when I change it for example to onAction().
Jecki wrote:
>
> You might want to try using the method naming convention instead of
> annotation.
>
> @OnEvent(value = "reset")
>p
You might want to try using the method naming convention instead of annotation.
@OnEvent(value = "reset")
public Object reset(){
tableParsed = false;
saveSucceed = false;
return null;
}
change to:
public Object onActionFromReset(){
tableParsed = false;
Just to bring this up. I tried several things to solve the Problem but to no
avail. I still have no clue on what is going wrong here.
I've put everything from the component into a page, nothing changed. I
testet it on several other computers, nothing. I tried it using tomcat,
nothing.
I have Act
The event handler method is in a class called CellHTSUpload.java and the
actionlink in the corresponding CellHTSUpload.tml.
CellHTSUpload.java looks like this:
public class CellHTSUpload {
private UploadedFile descript;
private UploadedFile topTable;
@Persist
private Experiment
maybe you can try to be more specific in this way:
${index}
@OnEvent(value = "action", component = "select")
void valueChosen(int value)
{
this.value = value;
}
Here you can find more explanation:
http://tapestry.apache.org/tapestry5/tapestry-core/guide/event.html
moritzgilsdorf-
Where is your event handler method? If the is inside
component Foo's template (Foo.tml), then the method goes inside
Foo.java.
On Mon, Oct 13, 2008 at 9:22 AM, moritzgilsdorf
<[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I'm feeling like posting a very trivial problem but unfortunately I can't
> find m
Yes, they are both persisted. tableParsed is set to true after a file was
uploaded and parsed success
fully. This variable is then used to show the next step of this process
which requires the table to be parsed.
The whole thing works well except that after the process is finished I have
to resta
Em Mon, 13 Oct 2008 14:22:36 -0200, moritzgilsdorf
<[EMAIL PROTECTED]> escreveu:
@OnEvent(component = "reset")
public Object reset(){
tableParsed = false;
saveSucceed = false;
return null;
}
Are tableParsed and saveSucceed @Persist'ed?
--
Thiago H. de Pau
13 matches
Mail list logo
