From: KevinBenson <km...@ms...> - 2005-03-14 14:02:39
|
I was wondering if anybody had any ideas on this one. I did investigate a little more there is nothing to do with missing a jar. Just seems to be the query mechanism in a embedded eXist that is causing that namespace to get lost. If it helps my queries are always getting at the vor:Resource for example normally I declare a bunch of namespaces and do a (for $x in vor:Resource where vr:identifier='ivo://astrogrid.mssl/fits_trace') In general it happens on all the queries I do. Also I tend to do a getMembersAsResource() method, so I do need to verify by going into the actual ResourceSet, but I am fairly certain the same thing will happen. cheers, Kevin -----Original Message----- From: KevinBenson [mailto:km...@ms...] Sent: 09 March 2005 16:35 To: Exist-Open Subject: Problem with lost namespace in embedded eXist I cannot figure out if there is a jar I am missing or something else. But in general i store a file very similiar to the one below. Using XMLdb api querying in embedded mode. I tend to lose the namespace of the <table> element hence the VODataService namespace (also <coverage> element). The storage seems to be correct and I can query on the table(and sub elements) with the VODataService namespace. But when I receive the xml back it seems to be gone. I changed things around to point to a external eXist via xmlrpc and everything seems to be correct there. I thought at first it might be a jar file missing, I noticed a few of the original eXist/lib/endorsed missing from my web-inf/lib directory, but I have now fixed that and still same result. Any ideas? Is there something in the conf.xml that would cause this? Thank you for your answers. Sample XML below, table element essentially gets the vr(VOResource) namespace on the query in embedded mode (because it has no namespace given back) it should be the vs namespace (VODataService). (I believe it is happening on the coverage element as well, but right now been focused on the table element.) <vor:Resource status="active" updated="2005-03-09T14:51:00Z" xmlns="http://www.ivoa.net/xml/VOResource/v0.10" xmlns:vm="http://www.ivoa.net/xml/VOMetadata/v0.1" xmlns:vr="http://www.ivoa.net/xml/VOResource/v0.10" xmlns:vs="http://www.ivoa.net/xml/VODataService/v0.5" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="vs:TabularSkyService"> <title>Trace Instrument Fits</title> <identifier>ivo://astrogrid.mssl/fits_trace</identifier> <curation> <publisher>MSSL/UCL Mullard Space Science Laboratory</publisher> <creator> <name>Kevin Benson</name> </creator> <contact> <name>Kevin Benson</name> <email>km...@ms...</email> </contact> </curation> <content> <subject>solar events</subject> <subject>NOAA</subject> <description>Fits File information from the Trace instrument, mainly the PROG_RUN keyword is the most important dealing with the event in time.</description> <referenceURL>http://radiosun.ts.astro.it/sec/sec_ui.php</refere nceURL> <type>Catalog</type> </content> <interface xsi:type="vs:WebService"> <accessURL use="full">http://msslxy.mssl.ucl.ac.uk:8080/astrogrid-cea-commandline-MSSL/ services/CommonExecutionConnectorService</accessURL> </interface> <coverage xmlns="http://www.ivoa.net/xml/VODataService/v0.5"> <!-- result from embeded mode query is <coverage> --> <spatial> <region xsi:type="vs:AllSky"/> <regionOfRegard>180</regionOfRegard> </spatial> <spectral> <waveband>Radio</waveband> <waveband>Millimeter</waveband> <waveband>Infrared</waveband> <waveband>Optical</waveband> <waveband>UV</waveband> </spectral> </coverage> <table xmlns="http://www.ivoa.net/xml/VODataService/v0.5"> <!-- result from embeded mode query is <table> --> <name>fits_trace</name> <column> <name>Keywords/PROG_RUN</name> <description>Date and Time of the event.</description> <dataType arraysize="*">char</dataType> </column> </table> </vor:Resource> |