There is a (possibly partial) solution to this problem implemented on
the lp:~zorba-coders/zorba/temp-csx-schema branch. Luis introduced
Item::getTypeCode(), which returns an enum for atomic types. This
information already existed in the store; the change exposes it through
the public API.

** Branch linked: lp:~zorba-coders/zorba/temp-csx-schema

You received this bug notification because you are a member of Zorba
Coders, which is the registrant for Zorba.

  Item types need to have their own class

Status in Zorba - The XQuery Processor:

Bug description:
  Items need to be extended to have a class that define base types, currently 
we have a class named:
  which has some functionality, but is not implemented all along zorba, also 
the class:
  with two sets:

  We should have another set for basic types, for example in the Item
  case, when you get the type, you actually get another Item that gives
  you the type in a String, this is not efficient for XQJ API
  implementation trying to identify the type and convert it into a

  Here is a link where you can see how XQJ defines all types and node

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to