Hello,
The new concept of X-Application is that we are using BusinessNode only when Schema information is required. This is only useful when anonymous structure like nested sequences have to be addressed or choices have to be flipped.
The common way should be to work on the document model, in this case JDOM.
To your exception:
AnchorCursor docCursor = ws.xquery(null, "Ortopedi", qstr, 10);
</pre><BR><BR>The documents you get from the cursor do not relate to a schema since the doctype information is 'null'. <BR><BR>You have two alternatives:<BR><BR>1) Work without BusinessNode objects. I would use this way if I have not to deal with nested sequences and do not need the switching of choices. In this case, don't use <BR><BR><pre class="ip-ubbcode-code-pre">
BusinessNode root = doc.getRoot();
</pre><BR><BR>but <BR><BR><pre class="ip-ubbcode-code-pre">
Element root = doc.selectElement("/Combo");
</pre><BR><BR>2) Assign a schema to your documents. A to be done, load the schema containing the element definition of 'Combo' to your workspace, e.g. by<BR><BR><pre class="ip-ubbcode-code-pre">
workspace.getSchemaSet().add(SchemaFactory.forTamino(store, collection, "schema's name"));
</pre><BR><BR>Then, use<BR><BR><pre class="ip-ubbcode-code-pre">
AnchorCursor docCursor = ws.xquery("Combo", "Ortopedi", qstr, 10);
Bye,
Christian.
#Tamino#API-Management#webMethods