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
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.
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.
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
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
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'
