There's bug 924987 (with a merge proposal that still needs some work) that addresses a similar problem. I think that the goal in both cases is the same: to provide complete information about a sequence type on the public API. Probably we can extend/modify TypeIdentifier in a way that provides sufficient information to be able to efficiently build an instance of XQItemType for XQJ. (If we actually need to modify TypeIdentifier, this would be an incompatible change and thus would need to go into 3.0).
-- You received this bug notification because you are a member of Zorba Coders, which is the registrant for Zorba. https://bugs.launchpad.net/bugs/935666 Title: Item types need to have their own class Status in Zorba - The XQuery Processor: New Bug description: Items need to be extended to have a class that define base types, currently we have a class named: zorba::TypeIdentifier which has some functionality, but is not implemented all along zorba, also the class: zorba::IdentTypes with two sets: kind_t quantifier_t 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 constant. Here is a link where you can see how XQJ defines all types and node kinds: http://www.xqj.net/javadoc/javax/xml/xquery/XQItemType.html To manage notifications about this bug go to: https://bugs.launchpad.net/zorba/+bug/935666/+subscriptions -- Mailing list: https://launchpad.net/~zorba-coders Post to : zorba-coders@lists.launchpad.net Unsubscribe : https://launchpad.net/~zorba-coders More help : https://help.launchpad.net/ListHelp