Jesse - i just fell in love with you :-) (hopefully my wife will not
read this :-p)
Absolutely unbelievable - but you were right.
Despite the fact that I was using FireBug 0.41 (I think this is the
newest one): after uninstalling ALL plugins and restarting the
javascript errors are gone.
After installing FireBug again, they occasionally reappear (very seldom)
when using more than one tab.
So the only thing left is the problem with DIVs disappearing when using
cycle.getResponseBuilder().updateComponent("nameOfTheDiv").
But that is something I can narrow down and isolate for testing -
hopefully :-)
Thank you very much for your quick help and a solution I do not even
think of. Awesome !
Gary
Jesse Kuhnert schrieb:
It is hard to say, but is it possible that you are a victim of the
early beta release of FireBug ? If you are using it I'd try either
disabling the plugin to see what is happening or upgrade to the latest
version where these initial hiccups were fixed.
On 12/17/06, Gary <[EMAIL PROTECTED]> wrote:
First to mention: I know this kind of messages aren't helpful at all
because I am unable to narrow things down nor can I provide some
concrete examples at this time - but I hope someone could give me a hint
how to get rid of this mess :-)
Some weeks ago I did a tapestry view for my order entry application.
Using Tapestry 4.1.1 on maven/jetty.
After doing some serious back end programming and testing for the last
few weeks, yesterday I returned to the web application.
Since I use maven, configured to use the SNAPSHOT version, it
automatically updated to the newest snapshot of tapestry.
And now 'everything' in conjunction with AJAX/dojo seems to be broken -
absolutely no idea why :-(
First 'SortableTable' was removed from dojo - ok, so I switched to
FilteringTable - components for the win :-)
When starting the application the first thing I see is an
javascript-error (firebug) 'Could not load 'dojo.logger.Logger'.
While navigating through the view, occasionally 'tapestry.bind is not a
function' error messages are displayed.
Using cycle.getResponseBuilder().updateComponent("nameOfTheDiv") will
redraw the named div - but some other divs on the page will disappear -
resulting in 'createWidget() Node not found with specified id of
...'-errors.
Occasionally the 'tapestry.cleanConnect is not a function' error is
displayed.
Doing a reload of the page sometimes helps against the 'tapestry.xxx is
not a function' errors.
I am absolutely clueless how to get things working again - it is a
really huge application with tons of components/pages.
So I hope there is a 'global' change I have missed - to get things fixed
with relatively little effort.
I could try to rewind to the snapshot-version I used to develop the view
- but than I am stuck on this version :-(
After 2 full days of trying to fix things I am close to surrender :-(
So hopefully someone could point me out a different view on this
problem.
Any help/hint would be really appreciated.
Gary
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
