If you download the jetty package from their website you will find
that there is an /etc directory. In that directory are numerous
examples of how to configure different aspects of jetty. I would take
a look at jetty.xml and jetty-logging.xml in particular. I think it
may be easier to leave apache out of the equation until you are sure
it's not part of the problem.
-Anthony
On Jul 10, 2008, at 12:03 PM, Christine Karman wrote:
On Thu, 2008-07-10 at 07:38 -0400, Benson Margulies wrote:
Christine,
I'm trying to find some time to build up an example. Until then, I
want to try to clarify something.
The cxfjsutils.js file and the server itself have to be on the same
host:port. The rest of the html need not.
The web service works ok and the javascript download from the web
service works ok. But somewhere inside the javascript the call to the
webservice doesn't work. Not on port 9000 and not on a rewritten /soap
url. The error it gives suggests that the call is ok.
Is there a way of activating the log in Jetty so I can see if Jetty
receives the call?
dagdag
Christine
On Wed, Jul 9, 2008 at 12:34 PM, Christine <[EMAIL PROTECTED]>
wrote:
Benson,
this is what the js trace gives me:
emptyClient constructorrequest
http://www.christine.nl/soap/wendyBotabout to open POST
http://www.christine.nl/soap/wendyBotabout to send dataPOST
http://www.christine.nl/soap/wendyBotonreadystatechange
1onreadystatechange 2onreadystatechange 4onreadystatechange
DONE
0
then it calls the error function with code -1.
--
dagdag is just a two character rotation of byebye
www.christine.nl
