Subject: Still having xupdate activity difficulty
- Next message: Tom Sugden: "RE: Still having xupdate activity difficulty"
- Previous message: neil p chue hong: "Re: How to run with http port number 80"
- Next in thread: Tom Sugden: "RE: Still having xupdate activity difficulty"
- Reply: Tom Sugden: "RE: Still having xupdate activity difficulty"
From: Chris Thatcher (thatcher@butterfly.net)
Date: Oct 15, 2003 20:04
Hi All,
I have been trying get xupdate activities to work with the DAI 3.0.2
release which I built from source. I replaced to ogsadai.jar in
<tomcat-webapps-ogsa-WEB-INF>/lib, and the entirety of the
<tomcat-ROOT-schema>/ogsadai directory. I also rebuilt the xindice1.0
distribution from source making the change specified by Tom Sugden in
"RE: xupdate activity difficulty with dai 3.0" which I had previously
overlooked in the release notes. I replaced the xindice.jar, as well as
the xmldb*.jars that come with that distribution. I was able to
successfully use all activity types, EXCEPT, xupdate activities. The
xindice db that I'm hitting uses the rebuilt source and seems to be
working. I am having a hard time tracking down the problem even with
log4j.properties spitting out all debug messages, which for most
activities is a very large number of logged messages. I don't get any
debug messages from the xupdate activity! Whats is very mysterious is
that my perform document (attached) disappears physically from my
machine when I push the "Perform Request " button on the graphical
demonstrator. Perhaps I should check with another test client... I
have gone back over the install notes and release notes though it
wouldn't been the first time I was guilty of over looking something simple.
Any ideas?
Christopher Thatcher
- text/xml attachment: updateResource1.xml