[MarkLogic Dev General] Bug in XCC - lone attributes reporting as elements.

[Sam Neth]

This would be the appropriate place to report a bug or RFE, assuming no support contract is in place.  In this case, the behavior you describe is a known limitation of XCC which we are already tracking as an RFE.  You may consider your interest noted.

On Mar 1, 2010, at 5:46 AM, Lee, David wrote:

Whats the best way to report this bug ?

If I run an ad-hoc query in XCC which returns a single attribute, for example :
       attribute {"foo"} {"bar"}

The resulting item in XCC is reporting itself as an element, but (of course) wont serialize.
I would like to be able to detect lone attributes for special handling but I cant because XCC is incorrectly representing them as Elements

Example code  fragment:

  while (rs.hasNext()) {
     ResultItem rsItem = rs.next();


     ItemType type = rsItem.getItemType();
     XdmItem item = rsItem.getItem();
     if( (type.isNode() && item instanceof XdmAttribute)  )
                                // FAILS TEST ...  item is an ElementImpl not an XdmAttribute


---
item       ElementImpl  (id=62)
   stream               null
   stringVal           "bar" (id=73)
   type                    NodeType  (id=58)





----------------------------------------
David A. Lee
Senior Principal Software Engineer
Epocrates, Inc.
dlee at epocrates.com<mailto:dlee at epocrates.com>
812-482-5224

_______________________________________________
General mailing list
General at developer.marklogic.com<mailto:General at developer.marklogic.com>
http://xqzone.com/mailman/listinfo/general

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://xqzone.marklogic.com/pipermail/general/attachments/20100301/f28a70ea/attachment-0001.html