Hi,
in BaseX 6.7.2 beta we are hitting new issue, that we haven't observed in 6.7.1.
I store following xml:
<task oid="91919191-76e0-59e2-86d6-998877665544"
xmlns="http://midpoint.evolveum.com/xml/ns/public/common/common-1.xsd" xmlns:c="http://midpoint.evolveum.com/xml/ns/public/common/common-1.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:my="http://myself.me/schemas/whatever%22%3E
<extension> my:shipStatecapsized</my:shipState> <my:dead xsi:type="xsd:integer">42</my:dead> </extension>
</task>
... and when I retrieve it, the xsd namespace declaration is missing. However the xsd namespace is used in value of xsi:type attribute.
regards, Igor Farinic
Hi,
I am using ClientSession and following xquery command:
query.append(DECLARE_NAMESPACE_C); query.append("for $x in //c:object where $x/@oid="").append(oid).append("" return $x"); cq = session.query(query.toString());
On 08/16/2011 11:35 AM, Christian Grün wrote:
Hi Igor,
I store following xml: [...] ... and when I retrieve it, [...]
How do you retrieve it? Christian
I didn't manage to reproduce this behavior. Did you run the latest snapshot? Are you working with the sources? Note that the JAR snapshots are regularly updated (we might introduce a revision a number to the snapshot to avoid confusion). ___________________________
On Tue, Aug 16, 2011 at 11:46 AM, Igor Farinic igor.farinic@evolveum.com wrote:
Hi,
I am using ClientSession and following xquery command:
query.append(DECLARE_NAMESPACE_C); query.append("for $x in //c:object where $x/@oid="").append(oid).append("" return $x"); cq = session.query(query.toString());
On 08/16/2011 11:35 AM, Christian Grün wrote:
Hi Igor,
I store following xml: [...] ... and when I retrieve it, [...]
How do you retrieve it? Christian
I managed to reproduce the issue even with latest snapshot. Strange is that we have similar tag with value xsd:integer in different test and there it handles namespace declaration correctly.
To simplify testing of newest snapshots it would help, if you have a maven snapshot repository.
Igor
On 08/16/2011 11:55 AM, Christian Grün wrote:
I didn't manage to reproduce this behavior. Did you run the latest snapshot? Are you working with the sources? Note that the JAR snapshots are regularly updated (we might introduce a revision a number to the snapshot to avoid confusion). ___________________________
On Tue, Aug 16, 2011 at 11:46 AM, Igor Farinic igor.farinic@evolveum.com wrote:
Hi,
I am using ClientSession and following xquery command:
query.append(DECLARE_NAMESPACE_C); query.append("for $x in //c:object where$x/@oid="").append(oid).append("" return $x"); cq = session.query(query.toString());
On 08/16/2011 11:35 AM, Christian Grün wrote:
Hi Igor,
I store following xml: [...] ... and when I retrieve it, [...]
How do you retrieve it? Christian
I managed to reproduce the issue even with latest snapshot.
Hm.. do you have an sscce that will allow us to reproduce this issue as well? - Christian
Strange is that we have similar tag with value xsd:integer in different test and there it handles namespace declaration correctly.
To simplify testing of newest snapshots it would help, if you have a maven snapshot repository.
Igor
On 08/16/2011 11:55 AM, Christian Grün wrote:
I didn't manage to reproduce this behavior. Did you run the latest snapshot? Are you working with the sources? Note that the JAR snapshots are regularly updated (we might introduce a revision a number to the snapshot to avoid confusion). ___________________________
On Tue, Aug 16, 2011 at 11:46 AM, Igor Farinic igor.farinic@evolveum.com wrote:
Hi,
I am using ClientSession and following xquery command:
query.append(DECLARE_NAMESPACE_C); query.append("for $x in //c:object where $x/@oid="").append(oid).append("" return $x"); cq = session.query(query.toString());
On 08/16/2011 11:35 AM, Christian Grün wrote:
Hi Igor,
I store following xml: [...] ... and when I retrieve it, [...]
How do you retrieve it? Christian
basex-talk@mailman.uni-konstanz.de
-
Christian Grün -
Igor Farinic