This is my last posting on this subject to this list. I have posted
a more detailed message on the wonder list. It turns out that it
isn't an obvious configuration problem after all. There is an error
in setting a request header that doesn't make sense. Currently, as a
workaround (?) I have had to change the prototype.js file to catch
and disregard the DOM Exception 12 error. I don't know if this will
work, or why it is happening, but it looks like it kind of works. I
don't understand why I am getting this error and it doesn't appear
that anyone else is.
John
On Jul 23, 2007, at 3:35 PM, John Larson wrote:
As a follow-up, it definitely looks like something screwy with my
Eclipse project configuration. Like I wrote before, a new project
works fine. The same project that I can't get to use 4.0 in
development works just fine in a ssdd deployment with 4.0. But
that is no help when debugging. I've cleaned the project and
restarted Eclipse too.
Thanks for any leads,
John
On Jul 23, 2007, at 12:14 PM, John Larson wrote:
Sorry about posting to the wrong list - I will repost on Wonder (?).
I do have the frameworks update, which is what is so weird. Like
I said, I have two different projects in the same workspace and
one works, and the other doesn't. If I just update the
Ajax.framework, then I get the class not found error about
ERXResponse. Then when I add ERXExtensions that error goes away.
That at least says to me that I've got the build path kind of right.
John
On Jul 23, 2007, at 11:07 AM, Timo Hoepfner wrote:
Hi,
this should probably better go to the Wonder discussion list.
Have you updated the WebServerResources of the web server (e.g. /
Library/WebServer/Documents/WebObjects/Frameworks/Ajax.framework)?
Timo
Am 23.07.2007 um 17:40 schrieb John Larson:
I've been using the Ajax components of 3.0 for some time with no
problems. I upgraded to 4.0 and they no longer work. I've done
a lot of sleuthing and have some info that I hope can elicit
some help on where to look.
1) If I make a new woapplication in Eclipse everything works
fine. (I've been doing my testing with a simple update link and
update container that increments a number)
2) None of my existing update links, sortable lists, or update
areas work in my application. The client stuff works (update
areas highlight, draggables drag, etc.) but the actions never
get called. I get no errors in either the Safari java console
nor the app log.
3) if I put my simple test component in my application template
(a wrapper for the page layout), then nothing happens.
4) if I take the component out of the template and just show
it, the update container shows a session timeout page).
5) when I revert to the 3.0 frameworks everything works again.
I do extend erxapplication, erxsession and erxdirectaction
totally vanilla - I don't subclass them further.
Thanks in advance for any help.
John
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/th-dev%
40onlinehome.de
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/the_larsons%
40mac.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/the_larsons%
40mac.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
