We are doing our first steps with tamino. Based on this, the described problem may be in front of the screen.

We have to use a xsd which was designed externally. The type definitions inside the xsd are based on xs:extension, defining subclasses:

<xs:complexType name=“type.swiss”>
xs:complexContent
<xs:extension base=“type.person”>
…
The root is defined like this

<xs:element name = “reportedPerson”>
xs:complexType
xs:sequence
<xs:element name = “person” type = “type.person”></xs:element>

a) We were able to build a matching tsd from the xsd.

The tsd starts like this

<xs:schema targetNamespace = “http://www.ech.ch/2004/ech-0011”
elementFormDefault = “qualified”
xmlns = “http://www.ech.ch/2004/ech-0011”
xmlns:tsd = “http://namespaces.softwareag.com/tamino/TaminoSchemaDefinition”
xmlns:xs = “XML Schema”
xmlns:xsdconv = “http://namespaces.softwareag.com/tamino/TaminoSchemaEditor/ConverterXSDToTSD”>

b) We were able to load testdocuments into tamino, using the interactive interface.
c) When trying to display the document via X-plorer, we get a runtime error XPLXPE0058. We placed already a request on this.
d) When trying to X-Query the collection, using just “/” we are able to retrieve all documents.
e) When trying to access elements we fail, getting INOXIE8306

The loaded document looks like this:

4711
…
Behaviour is the same when xsi:schemaLocation is omitted.

Question: is it harmful for element retrieval to have xmlns, xmlns:xsi , xsi:schemaLocation in the root ?

Hi,

I don’t believe that your problems are caused by the xsi attributes. It might be that you are running into namespace problems. But to really understand your problem I would like to see your X-Query expression that is supposed to read elements in your “reportedPerson” doctype. In the meantime you can use the following XQuery expression:

declare namespace xyz=”http://www.ech.ch/2004/ech-0011&#8221;

input()/xyz:reportedPerson

Best Regards,

Thorsten Fiebig

Thx for your comment.

Here is the working x-query (plus result)

• <ino:response xmlns:ino=“http://namespaces.softwareag.com/tamino/response2” xmlns:xql=“XQL FAQ (XML Query Language - Frequently Asked Questions)”>
  xql:query/reportedPerson</xql:query>
• <ino:message ino:returnvalue=“0”>
  ino:messagelinefetching cursor</ino:messageline>
  </ino:message>
• xql:result
• 100.70.432.007 Muster Hans Hans 1

…
</xql:result>

• <ino:cursor ino:handle=“1”>
  <ino:current ino:position=“1” ino:quantity=“1” />
  </ino:cursor>
• <ino:message ino:returnvalue=“0”>
  ino:messagelinecursor fetched</ino:messageline>
  </ino:message>
  </ino:response>

Here the access to person, which fails:

• <ino:response xmlns:ino=“http://namespaces.softwareag.com/tamino/response2” xmlns:xql=“XQL FAQ (XML Query Language - Frequently Asked Questions)”>
  xql:query/reportedPerson/person</xql:query>
• <ino:cursor ino:handle=“1”>
  <ino:current ino:position=“0” ino:quantity=“0” />
  </ino:cursor>
• <ino:message ino:returnvalue=“8306”>
  <ino:messagetext ino:code=“INOXIE8306”>Invalid cursor position</ino:messagetext>
  </ino:message>
  </ino:response>

Thx in advance for further hints.
Christian

Local Software AG informed us, that the problem described should be fixed in Tamino Version 4.4.

This feedback, just to keep the community informed.