Re: [T4.1.2] stale link on ajax modified form

2007-10-09 Thread Martino Piccinato
Well it ended up to be a firebug strange behaviour (or bug?). The
request/response cycle was perfectly showed in the console as
expected, while in the XHR tab was showed the request/exception
response cycle mentioned before. It appears that by disabling firebug
the network monitoring option (Options - Disable Network Monitoring)
that request/response wasn't happening anymore so I must think that
was something firebug was generating by his own.

Don't know whether I'm missing something about firebug behaviour or if
it's just a bug, in my opinion network monitoring should be just
monitoring and not issuing requests.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [T4.1.2] stale link on ajax modified form

2007-10-08 Thread Martino Piccinato
just to be precise:

customerDetailsForm does contain much more than 0 fields while
roleSelect form contains just 1 field. On the ajax request a couple of
customerDetailsForm are made visible/invisible (actually I tried both:
using If that makes them disappear from the DOM and using a
component that simply wrap them as visible:none; that does not, same
result).

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [T4.1.2] stale link on ajax modified form

2007-10-08 Thread andyhot

Did you resolve this?
Looks like some state is different between render and rewind... and this 
might be caused by a lot of things.


Try persisting things to session till you find what causes the problem, 
then roll back  use

... the new knowledge

Martino Piccinato wrote:

just to be precise:

customerDetailsForm does contain much more than 0 fields while
roleSelect form contains just 1 field. On the ajax request a couple of
customerDetailsForm are made visible/invisible (actually I tried both:
using If that makes them disappear from the DOM and using a
component that simply wrap them as visible:none; that does not, same
result).

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  


--
Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr
Tapestry / Tacos developer
Open Source / JEE Consulting


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [T4.1.2] stale link on ajax modified form

2007-10-08 Thread Martino Piccinato
in fact the only thing it were previously persisted in session were
IPropertySelectionModel but I thought this was just a mistake because
it had no much sense, giong to make some test more..

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [T4.1.2] stale link on ajax modified form

2007-10-08 Thread Martino Piccinato
Well, after some cleanup and further test now the component is
(apparently) working perfectly. There was in fact some bad old code in
there that was messing up things.

But the strangest thing ever is that  firebug still gives me that
stalelinkexception when I fire my ajax eventlistener!! even though the
component is working. Nor I see any other request/response (XHR/NET)
with the html fragments that I KNOW are being updated (I just see
screen changing...)

So the situation is this:

I change a select, see a single request starting in firebug XHR/Net,
going to the correct listener and marked as dojo-ajax-request: true I
get the response, the second select is correctly updated, I look into
the response content with firebug and I see the above reported stale
link exception!


I'm puzzled.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]