[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: XML Query - Frustration
Hello Lars,
Thank you so much. This time I installed ozone using make and everything
worked fine.
-Sarva
-----Original Message-----
From: Lars Martin [mailto:lars@smb-tec.com]
Sent: Tuesday, August 29, 2000 1:27 AM
To: ozone-users@ozone-db.org
Subject: Re: XML Query - Frustration
Hi Sarva,
On Son, 27 Aug 2000, Bellan Saravanan wrote:
> After getting the following exception on my Work Machine (Sun SOlaris),
>
> >>ojvm XML.Query -q //NAME test.xml
> >>Querying file: test.xml
> >>Query String: //NAME
> >>XPath Processor: org.ozoneDB.xml.xpath.XtXPathProcessor
> >>java.lang.ClassCastException: java.lang.Integer
> >> at java.lang.Throwable.fillInStactTrace(Native Method)
> >> at org.ozoneDB.xml.dom.DocumentImpl_Proxy.getDocumentElement
> >>(DocumentImpl_Proxy.java:833)
> >> at XML.Query.main(Compiled Code)
>
> I came home and installed Ozone on my Win95. Installation, Database setup
> and Server start all went fine. When I run the same XML query example I
get
>
> Querying file: test1.xml
> Query string: /PERSON
> XPath processor: org.ozoneDB.xml.xpath.XtXPathProcessor
> java.lang.ClassCastException: org.ozoneDB.xml.dom.NodeListImpl
> at
>
org.ozoneDB.xml.dom.DocumentImpl_Proxy.getDocumentElement(DocumentImpl_Proxy
.java:833)
> at XML.Query.main(Query.java, Compiled Code)
Strange! Because the getDocumentElement() method has nothing to do with
NodeListImpl class nor Integer class from your first stacktrace. I presume
that
the autogenerated proxies don't match the currently compiled classes. So the
first step would be an 'ant clean' to make sure that no 'old' proxies exist.
At
next restart the compilation and build the whole source tree.
> I cant even put debug messages in DocumentImpl_Proxy.java and compile
since
> it is a autogenerated file and i cant modify and even if I can, it wont
> compile.
Please use '-debug3' to start the Ozone server with debug level 3. If the
XPath
Query still crashes you can read something like the following output in the
server side debug messages:
[debug](648) TransactionManager: newTransaction()
*****************************
[debug](648) TransactionManager: performCommand(): ta(-50), [DbDeleteObj]
Most important is the last 'performCommand' which specifies the real
database
method call. I presume that no 'getDocumentElement' is called in the
database.
> There are no warnings in the server log. I could see that the
> getDocumentElement() in DocumentImpl_Proxy.java does of type casting using
> Result Converter, but couldnt understand any of it.
>
> Ozonies, please guide me . I'm really frustrated.
Hope this helps a little bit,
Lars
--
___________________________________________________________________
Lars Martin mailto:lars@smb-tec.com
SMB GmbH http://www.smb-tec.com