From reading the docs I thought it was possible to intercept
JavaScript objects (and functions being called on those objects),
from what I'm reading here it sounds like that isn't the case.
I'll investigate this further and post back any questions I have.
-warner
On May 12, 2008, at 1:08 AM
Hi Warner
I'm not quite sure whether I understand you setup completely.
Nevertheless two hints:
- the "targets" attribute must refer to tapestry components. If you want to
refer to a client-side object use "elements".
- The element you want to intercept indeed *must* be a DOM-node. You could
cal
Here's a solution that's still a bit ugly but at least a little less drastic
than commenting out parts of Dojo... Override dojo.dom.isNode in your code
as follows:
dojo.dom.isNode=function(wh){
if(typeof Element=="function"){
try{
//return wh instanceof Element;
return Object.isEl
I just run into the same exact thing, using Tap 4.1.5, dojo that comes with
it, propertyselection and an eventlistener as well as prototype. Anybody
know if this is fixed in a newer snapshot, if there is a bug open on this or
any (better) workaround?
Kalle
On Sat, Oct 27, 2007 at 9:41 AM, lt <[EM
Hi, a don't see "typeChanged" element in your code, and javascript code
("tapestry.cleanConnect("yypeChanged", "onchange", "formEvent2604279"); ")
has error, don't see yypeChanged element. Put all your code and use Target
instead of Element, and put, if you have, a response when you use a Target
i
correction:
i replaced targets with elements.I am getting 'Error: bad srcObj for
srcFunc: onchange' when calling method: [nsIDOMEventListener::handleEvent]"
error .My ajax response has this
dojo.widget.byId("MyDialog").show();
tapestry.cleanConnect("yypeChanged", "onchange",
No,still not working
Andy Pahne-3 wrote:
>
>
> Try
>
>
>
> instead of
>
>
>
>
>
> Because you use the parameter "targets" in your @EventListener, you have
> to use a component id.
>
>
> Andy
>
>
>
>
>
> abhilash schrieb:
>> Hi all,
>> i am using tapestry4.1.5
>> My even
Try
instead of
Because you use the parameter "targets" in your @EventListener, you have
to use a component id.
Andy
abhilash schrieb:
Hi all,
i am using tapestry4.1.5
My eventListener is not getting called.This is my code.
delegate="ognl:validationDele
Hmm... can't probably help much, but i've seen quite a few fixes regarding
EventListener in the latest 4.1.6-SNAPSHOT
Can you give it a try?
http://people.apache.org/maven-snapshot-repository/org/apache/tapestry/tapestry-framework/4.1.6-SNAPSHOT/
On Thu, Apr 17, 2008 at 9:12 AM, abhilash <[EMAI
Yes,i have a "[EMAIL PROTECTED]" inside my Dialog.This is an ajax Form.My
@EventListener is
@EventListener(elements = "typeChanged", events = "onchange", submitForm =
"ListForm",async=true)
public void watchText(IRequestCycle cycle) {
---
-
-
cycl
Have you read the Dialog gotchas at
http://tapestry.apache.org/tapestry4.1/components/dojo/dialog.html ?
Does your Dialog completely contain a form?
On Thu, Apr 17, 2008 at 8:25 AM, abhilash <[EMAIL PROTECTED]> wrote:
>
> Hi ,
> I am using tapestry 4.1.5
> I have a property selection model in a
Kavya,
The id should be part of the jwcid expression:
the component will create the id attribute for you.
Kavya K wrote:
Hi..
My html code is..
and java code is
@EventListener(elements = "supplimentalId", events = "onclick")
public void watchText(IRequestCycle cycle)
{
// d
I think you have not set the update component, you need to put some code into
watchText() like this:
cycle.getResponseBuilder().updateComponent("DialogContentSupplimental");
I have also had more success implementing my dialogs like this
Then all you do is set showDlg to true in watchText(), but
I still use this workaround.
To have it work with T4.1.3, I think you just need to set the event on a
form component (I use the submit button).
dojo.byId('submit').ajaxEvent=function(json) {};
then :
@EventListener(targets = "submit", events = "ajaxEvent")
public void onAjaxEvent(IRequestCycle c
Is anyone using this workaround on Tapestry 4.1.3? I'm getting some dojo
JavaScript error ("o[i] has no properties"), but it seems to work on Tap.
4.1.2.
Christian Dutaret-3 wrote:
>
> I found a nice solution using dojo's ability to listen to an arbitrary
> javascript function as if it were a
Ok after looking into this. It appears to be a conflict with DOJO and
Prototypte. the isNode method in dojo check to see if Element is of type
function and then compare it to the object. I am not willing to give up
prototype for this, so i just commented out this section of the code in
/dojo-0.4
try 4.1.3-snapshot? There was more work done in that function
recently with the new javascript @EventListener function parameters
being able to be passed in to listeners via special methods in the
BrowserEvent object.
On 8/11/07, Frank <[EMAIL PROTECTED]> wrote:
> Hi,
>
> When I make a simple Eve
Sweet - that works - I thought I had tried that variation, but
obviously not.
I filed it anyway, under https://issues.apache.org/jira/browse/
TAPESTRY-1524
Thanks,
J
On 29-May-07, at 2:48 PM, Jesse Kuhnert wrote:
Sounds like a bug, if you would file it that would help me.
To get past yo
Sounds like a bug, if you would file it that would help me.
To get past your problem though, you may want to try changing your html
element to be:
Name ...
and listener :
@EventListener(targets = "nameHeader", events = "onclick")
public void doSomething(){}
I'm assuming the bug has to do w
Yeah it sounds like a bug of some sort to me.
On 5/28/07, Eric BIANCHI <[EMAIL PROTECTED]> wrote:
Hello list,
On Friday the 18th of May, I wrote :
--- CUT HERE ---
I've been happily using the EventListener Annotation in Tapestry
4.1.1 and everything works fine.
Using the latest snapshot (4.1
It behaves exactly the same way as a normal listener method - the only
difference being what causes it be invoked. So, in your example I'm not
sure what would happen but probably an error of some kind.
If you want to update a component you can use ResponseBuilder (grabbed via
IRequestCycle or h
I'm not sure what you mean, the asynchronous portion should happen
automatically.
It should also behave exactly the same way as your listener method would if
it were say a @Submit component listener or @DirectLink listener. The major
difference is that it automatically submits your form if you h
I've submitted a bug report for this issue:
https://issues.apache.org/jira/browse/TAPESTRY-1495
Thanks,
J
On 18-May-07, at 5:21 PM, Julian Wood wrote:
Hi Jesse, yes, it is a timesheets, billing, invoicing and reporting
system. Quite fun actually.
Your suggestion about not updating the com
Hi Jesse, yes, it is a timesheets, billing, invoicing and reporting
system. Quite fun actually.
Your suggestion about not updating the components unless necessary
was dead on. That took care of a lot of little problems which were
compounding on each other.
I have one last issue though. I
Your code looks like mine a couple of years ago only minus any ajax
support. (sounds hospital / billing ish related )
I agree about the server side validation being annoying and am in the
process of fixing it as it has just now annoyed me.
The not updating your form async triggers I'm not as su
Ah that explains it. Thanks...
On 5/14/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Oh, that's probably not a very good idea with asynchronous requests. I
added some extremely limited support for this mostly just to let people see
that something is happening but overall it's not something that
Oh, that's probably not a very good idea with asynchronous requests. I
added some extremely limited support for this mostly just to let people see
that something is happening but overall it's not something that is really
supported by the protocol and I'd generally suggest not trying it.
You can
I guess is the question I have is, is it not possible to have an
eventlistener submit a form that returns an IPage ?
~chris
On 5/14/07, Chris Chiappone <[EMAIL PROTECTED]> wrote:
Okay so I'm still having a issue trying to use the Eventlistener. The
form is getting submitted correctly but I end
Okay so I'm still having a issue trying to use the Eventlistener. The
form is getting submitted correctly but I end up getting 404 Error
page saying that the requested resource is not available. I had this
submitting with a normal submit and it works fine so I know this page
is available. Any t
Jesse - thanks for the fix!
On 5/14/07, Daniel Jue <[EMAIL PROTECTED]> wrote:
Are you sure the event name is correct? I use "onchange". I've never
used "selectOption" before.
Daniel
On 5/14/07, Chris Chiappone <[EMAIL PROTECTED]> wrote:
> Well this is the code i have, unfortuntately the even
Are you sure the event name is correct? I use "onchange". I've never
used "selectOption" before.
Daniel
On 5/14/07, Chris Chiappone <[EMAIL PROTECTED]> wrote:
Well this is the code i have, unfortuntately the eventlister does not
seem to get triggered:
HTML page:
Java Class:
Yes I guess that page does need to be updated - the correct function to
listen for is now "onValueChanged".
http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/tapestry-examples/TimeTracker/src/java/org/apache/tapestry/timetracker/page/TaskEntryPage.java?view=markup
On 5/14/07, Chris Chiappone
Well this is the code i have, unfortuntately the eventlister does not
seem to get triggered:
HTML page:
Java Class:
@Component(id="projectSelection", bindings = {"model=clientModel",
"value=clientName",
"displayName=message:choose.project", "filterOnChange=true
Here is another example you can use:
http://www.phy6.net/wiki/tiki-index.php?page=Tapestry+4.1.1+Simple+Selection+Model+Update+using+AJAX
I also remember having trouble using that example.
The html should have:
On 5/14/07, Chris Chiappone <[EMAIL PROTECTED]> wrote:
I'm also having trouble g
I'm also having trouble getting the eventlistener triggered when
somthing is selected.
On 5/14/07, Chris Chiappone <[EMAIL PROTECTED]> wrote:
I believe the eventlistener documentation contains some bugs. I
copied the following code:
The relevant html:
Select a pro
Oh - that is easy to fix. Drop the "prop" binding and use ognl. You won't
need that library anymore anyways..
On 5/7/07, RobertSchreiber <[EMAIL PROTECTED]> wrote:
Hi Jessek,
Thanks for your ultra fast response. The latest snapshot works.
Since I get always lost with downloading Tapestry via
Hi Jessek,
Thanks for your ultra fast response. The latest snapshot works.
Since I get always lost with downloading Tapestry via Maven,
I downloaded the latest Workbench WAR file and copied the libs.
JFYI:
I caught another error which I could fix.
Obviously JavaAssist 3.4 cannot handle array in
I'm not completely sure but I think your problem is that the component you
are updating does not refer to the entire select "block" but just to the
label. As the eventlistener/ajaxdojoresponse basically rely client side on
the innerHTML (or similar) javascript function to replace inner html we had
Try updating your tapestry version to 4.1.2. This works fine for me there.
On 5/6/07, RobertSchreiber <[EMAIL PROTECTED]> wrote:
Dear Tapestry specialists,
I have 2 corresponding PropertySelections in my page.
In Firefox everything works like expected.
As soon as I select a species in Prope
Well I tried to do the following:
@Component(id="deleteButton", type="DirectLink", bindings={
"parameters=ognl:currCase",
"renderer=bean:buttonRenderer",
"listener=listener:deleteCaseListener",
"onclick=ognl:confirmC
If you are using a DirectLink or a Submit button you do not need to use
the @EventListener annotation. You can specify using updateComponents
which elements to refresh. See
http://tapestry.apache.org/tapestry4.1/components/link/directlink.html
and http://tapestry.apache.org/tapestry4.1/components/f
https://issues.apache.org/jira/browse/TAPESTRY-1405
In the meantime I'll use Christian's approach.
Thanks, J
On 5-Apr-07, at 11:19 AM, Julian Wood wrote:
Was this ever dealt with? Attaching an event listener to a radio
group component still doesn't work for me in the latest 4.1.2
snapshot
Was this ever dealt with? Attaching an event listener to a radio
group component still doesn't work for me in the latest 4.1.2
snapshot, though if i change it to a property selection, it does. I
couldn't find a JIRA issue which looked like it dealt with this
specifically - maybe http://iss
@EventListener(elements = "footerText", events = "onclick")
in Border.java also doesn't get called as no appropriate _javascript_ is generated.
Only
tapestry.cleanConnect(dojo.byId("xxx"), "onmouseover", "event1707250979");
tapestry.event1707250979=function(e){
var content={beventname:"onmouse
The actual bug in this instance was the value="" attribute not being
carried over on the field being managed by the DatePicker.
...I've implemented a more robust general solution for all scenarios
that ensures all properties (whether formal or made up ) are properly
carried over on xhr requests n
PLease, create a JIRA and post the patch (preferably just a diff) there
Lionel Touati wrote:
In fact this issue was raised by the fact the DatePicker does not
automatically updates after being changed during the AJAX response
Here's a patch to the DatePicker.script to handle that
L.
Lionel
In fact this issue was raised by the fact the DatePicker does not
automatically updates after being changed during the AJAX response
Here's a patch to the DatePicker.script to handle that
L.
Lionel Touati a écrit :
Hi ,
I'm trying to put up a sample to use two date pickers, and an event
l
16.02.2007 12:30Kopie
Thema
Bitte antworten Re: @EventListener: adding custo
As far as i know this is not possible yet.
There is a jira request registered for it.
In the mean time you might use directly the js function provided by
tapestry linkOnClick which does the job very well.
I think you can find an example of how to use it in the autocompleter
component.
Alex
On
Ok, I'll try to get an example up on the jira that demostrates this.
On 2/8/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
AhThat is the bread & butter sort of logic I use often as well.
I'd need a specific example of how it's not working to be more
helpful. (preferrably in JIRA, most time spe
AhThat is the bread & butter sort of logic I use often as well.
I'd need a specific example of how it's not working to be more
helpful. (preferrably in JIRA, most time spent on the list is fun
"talking time" whereas actually sitting down and fixing things is
reserved for fun "jira time" . ;) )
Well Simply put... something like... (in pseudo tapestry tags... hehe)
<@If condition=true >
<@Else>
content..
On 2/8/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Ah...I guess that depends on how something is "conditionally"
rendered. If the renderComponent() method gets
Ah...I guess that depends on how something is "conditionally"
rendered. If the renderComponent() method gets called on it and
Tapestry thinks you want it to get updated it'll happen.
Need more info on how it's being conditionally rendered.
On 2/7/07, Daniel Tabuenca <[EMAIL PROTECTED]> wrote:
I
It's necessary because of the slew of nightmares associated with
preventing memory leaks on the client side as well as not knowing
which actual dom nodes do and do not exist(in the browser) already for
each request.
There's no other way to know without some sort of state knowledge,
which would pr
Perhaps the tapestry.linkOnClick(url,id,isJson) will do the trick.
In the url you can put the info you want to send to the server.
Take a look at the timetracker application for a sample of how to use it.
Cheers,
Alex
On 12/29/06, Roberto Ramírez Vique <[EMAIL PROTECTED]> wrote:
Hello Jesse &
Hello Jesse & Mark,
I am in the same situation as Mark was some time ago, at least I think the
situation is the same. This email is to know if there is any other way to
solve my problem.
I want to have a component which has a simple EventListener to that goes to
the server and changes some value
Ok, I got it working now. I didn't use the and components.
Mahmut
Mahmut Izci schrieb:
Hi all,
I'm just trying out the new EventListener annotation in tapestry 4.1.1
according to the explanation at
"http://tapestry.apache.org/tapestry4.1/ajax/eventlistener.html"; and I
can't get it workin
I have :
@EventListener(targets="myTarget" , events="myEvent")
and also the javascript function :
myTarget.myEvent=function(customObject) {}
I would like to send customObject to the server in the same way the
BrowserEvent is sent..
Which is the best aproach ?
Alex
On 12/20/06, Alexandru Dra
It worked.
I just needed to make sure that the id of the widget is the same as the id
of the component. This is what i was missing in the begining.
(And i passed the id as a target.)
Alex
On 12/20/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Have you even tried it?
This is definitely thought
Have you even tried it?
This is definitely thought out and well supported so I don't see why
it wouldn't work. Dojo has an internal client side "manager" that
knows about widgetId's so it lets me do things like
dojo.widget.byId("yourComponent.clientId") to get a reference to your
widget without a
The tapestry component extends AbstractWidget but i don't think this has
any influence on targeting the widget..
Alex
On 12/20/06, Alexandru Dragomir <[EMAIL PROTECTED]> wrote:
I'm a bit confused..
What i want to target is not a tapestry component but the dojo widget
created by the component
I'm a bit confused..
What i want to target is not a tapestry component but the dojo widget
created by the component.
As a matter of fact , in the generated html, the tapestry component id is
not even present anymore.
Instead i have the javascript which created the tree with the parameters
provide
Yes that will work, but only if the component being targeted
implements IWidget. (or extends AbstractWidget)
On 12/19/06, Alexandru Dragomir <[EMAIL PROTECTED]> wrote:
I might be asking too much :
Is it possible to use the @EventListener with the target being a
programatically created widget ?
In the mean time i found out that the afterAddChild is a topic .
So my problem is solved by subscribing to this topic with whatever function
i want.
I'm still interested in the answer though.
thanks for any feedback !
Alex
On 12/19/06, Alexandru Dragomir <[EMAIL PROTECTED]> wrote:
I might be
Hello,
thanks for your answer.
In Firefox the problem has been solved but in IE it still does not work the
right way.
After calling the listener and updating the second PropertySelection
component the values of this selection have been lost.
Can you reproduce this behavior? Has anyone an idea h
I think what Jesse says is exactly what is expected and intuitive,
but I've just spent 3 hours proving that it needs those "redundant"
divs if you want it to work (unless I've misunderstood, or am
approaching this wrong).
Case in point, using the Dec 12, 4.1.1 snapshot:
@EventListener( eve
If you have FireBug installed you might try either upgrading to the
latest version or disabling it to see if the problem persists.
p.s. Please direct emails like this to the list only please. I'm
making it a point to completely ignore all emails sent to me directly
unless I have engaged or know w
Hello Jessek,
I've tried to implement a simple example where I can demonstrate my problem:
test.html:
Hello, I'm a dialog!
test.page:
component id="selectionOne" type="PropertySelection">
There i
Again, not run into this one but if someone gives me a definitive
example that I can see for myself I have a much better chance of
fixing / knowing what the problem is.
On 12/6/06, Tine <[EMAIL PROTECTED]> wrote:
Hello,
i need some help, please:
In my application I have some dialog components
No, it may very well be a bug. I wouldn't be surprised at least. I'm
still busy trying to refactor/etc the For component to work under
these "dynamic" conditions a little more friendlier but if a bug is
filed I will have a much better chance of remembering. (whereas emails
to this list are only li
After looking at this some more, it seems to me that listener methods can't
be in components (that is, if a component is contained within another
component, the container won't get the event, the page will). I think I was
wrong about DirectLink and Submit. In any case, I put my @EventListener on
t
https://issues.apache.org/jira/browse/TAPESTRY-1132
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Ohh,Right, parameters . I don't know if a JIRA issue is opened for it
(support parameters using @EventListener, somehow..) , but that would be a
good start towards getting that resolved.
On 10/27/06, Patrick Moore <[EMAIL PROTECTED]> wrote:
What I am hoping to do is something like this:
What I am hoping to do is something like this:
and code like this:
public void makeLink() {
IEventListener listener = getFoo().getEventListener("onclick");
listener.setEventHandler("bar");
listener.setParameters(new Object[]{ getCurrent().getEntityId()});
}
https://issues.apache.org/jira/browse/TAPESTRY-1128
Peter Beshai
From: "Jesse Kuhnert" <[EMAIL PROTECTED]>
Reply-To: "Tapestry users"
To: "Tapestry users"
Subject: Re: @EventListener issue with submitForm and Upload component
Date: Fri, 27 Oct 2006 11:54
I'm not sure I understand what you mean. What model do you think would feel
more natural?
On 10/25/06, Patrick Moore <[EMAIL PROTECTED]> wrote:
Is there any more on this?
I am just now starting to explore the EventListener model. I must
admit I find it a little odd that I can't wire things up
It's possible. Don't know if I tested that particular component. Can you
create a JIRA issue?
On 10/25/06, Peter Beshai <[EMAIL PROTECTED]> wrote:
Is it intended that if there is an Upload component in the form that is
attached to an EventListener (via setting submitForm="myform"), the
EventLis
Is there any more on this?
I am just now starting to explore the EventListener model. I must
admit I find it a little odd that I can't wire things up
programatically. It feels wrong that I need to decide at compile time
that two components are talking to each other.
Or is there something new?
-
I don't know Sam. What does the download page say?
On 10/23/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
for 4.1.1, I need to deal with setting up and figuring out maven, yes?
--sam
On 10/23/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
> I don't think any of your problems are relevant anymore
for 4.1.1, I need to deal with setting up and figuring out maven, yes?
--sam
On 10/23/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
I don't think any of your problems are relevant anymore in the current
4.1.1snapshot versions of the framework. I can't remember the
differences between
4.1 and 4.
I don't think any of your problems are relevant anymore in the current
4.1.1snapshot versions of the framework. I can't remember the
differences between
4.1 and 4.1.1 so I'm not even going to try.
Give 4.1.1 a try and then get back to me if you find problems there. ;)
On 10/22/06, Sam Gendler <[
Not sure, but a couple points:
-) Opera is supported, debug messages on the page are the intended result
without using console mode.
-) IE7 was released today - we aren't running a 0day op here ;)
On 10/19/06, bueggers <[EMAIL PROTECTED]> wrote:
Are the known problems with @EventListener and
Hah! That's pretty cool. I like it :)
If someone files a bug in JIRA I'll look into the radio button stuff
.(though I thought I remembered there being a ticket for this already - at
least I know we had to deal with it in tacos )
On 10/4/06, Christian Dutaret <[EMAIL PROTECTED]> wrote:
I found
I found a nice solution using dojo's ability to listen to an arbitrary
javascript function as if it were a native event.
I attach an empty js function to an arbitrary DOM element like this:
document.getElementById('someDiv').clickRadio=function(radio) {};
and an onclick attribute to my radio but
I'm glad someone else has a need for this as well. From doing a little
bit of research the other day, I found @EventListener annotation that
was introduced into tapestry 4.1+ that "sort of" fixes the problem. I'm
currently using stable release of tapestry 4.0.2, so I didn't bother
going that r
Hmmm... I will look into it. That should be working.
On 10/2/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
From reading the documentation I get the impression that listener
annotated
by @EventListener will be called regardless of wether async parameter is
true or false. In my case I see that
Awesome thanks, I'll look at it during the next triage. (Which should be
soon now since the date i18n issues seem to be fixed. )
FYI - you don't even need a jetty configuration file to configure it with
maven. It's literally like 2-3 lines of configuration in the pom.xml file.
On 9/28/06, Christ
https://issues.apache.org/jira/browse/TAPESTRY-1100
I tried to post this the "mark reynold's way", with a maven2 sample
application attached, except that I don't use Jetty (I use Tomcat), so no
Jetty configuration.
Hope this helps
Ch.
2006/9/27, Jesse Kuhnert <[EMAIL PROTECTED]>:
HmmmCan y
HmmmCan you still post a bug in JIRA anyways? This sounds like a
possible bug in one the services. (be as detailed as possible about what you
did to have it happen, if that's possible..)
On 9/27/06, Christian Dutaret <[EMAIL PROTECTED]> wrote:
I was running my application with caching disab
I was running my application with caching disabled on my dev environment. If
I enable caching, then guess what... it works as expected (events are sent
only once when A changes). Amazing.
After a closer look, it seems that the updated event registration script is
sent with a different id (formEven
Hello Jesse,
thanks for the fast reply !!!
That's good to know that you have already solved the problem, I tried that
solution and works fine !
I will wait for the new release to solve the problem.
Thanks you
robert
On 9/23/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
I ju
I just noticed and fixed it, but can't "quite" do a new snapshot release
until some date parsing issues get resolved.
It wouldn't be extremely hard for you to fix temporarily...The
tapestry.corepackage (
core.js) had a bug in the load() function...When it found an includescript
element it would c
Thanks Patrick!!!
I've look to this component and now I use a "workarround" I show a radio
button to select which item the user wants to remove. This radio button
keeps the for index, and in the server side I can refer directly to the
correct element. This works fine!!! I'm happy to see that this
take a look at the For component docs. This component has pretty good doc
that talks about that issue.
Thanks you!!!
In fact I see this comment in another thread and I already did this.
Now I have another problem, probably a problem easy to be solved, but I
don't see how to do this. My problem is that I have a "remove" for the same
list, and I have to pass the list index to the serverside... but
Make sure that your "requestorsLoop" is outputting an actual html element on
render. If you can't view source of a rendered page and find an existing
html element then there is nothing to "update". I think using the For
component you have to specify element="div || span || whatever " to get it
to
Problem solved, sorry, it was an stupid problem ... just a duplicated id for
the addLink element.
Anyway now this part works.
On 9/21/06, Roberto Ramírez Vique <[EMAIL PROTECTED]> wrote:
Hi everybody,
I'm an starter in Tapestry 4.1, using tomcat 5.5 and jdk 1.5
I want to have a link (a plus
when i changed the initialization from @InitialValues to finishLoad(...) it
started working. It really is amazingly simple to make this kind of
functionality with EventListener.
On 9/19/06, Jani Lindqvist <[EMAIL PROTECTED]> wrote:
Hello,
should the model of component B be persisted or set a
This brings a question: what is the proper strategy to initialize property
values when using ajax submits? Does finishLoad() does the trick? I am still
a bit confused about when all those methods/listeners are invoked and in
which order
I've got a question about this as well, although I am Tap
Hello,
should the model of component B be persisted or set as property?
I have a page that has the same logic as in this example, but the
dynamically populated combobox value is always null when the post is done
(and also in the eventlistener method).
If i change the model to be fetch from a ge
1 - 100 of 133 matches
Mail list logo
