[ https://issues.apache.org/jira/browse/XERCESC-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131875#comment-16131875 ]
Yannick Müller commented on XERCESC-1532: ----------------------------------------- Same applies to base64Binary values. > PSVI: I/F doesn't provide length of hexBinary data > -------------------------------------------------- > > Key: XERCESC-1532 > URL: https://issues.apache.org/jira/browse/XERCESC-1532 > Project: Xerces-C++ > Issue Type: Bug > Components: Validating Parser (XML Schema) > Affects Versions: 2.7.0 > Reporter: Steve Magnani > > When PSVIItem::getActualValue() is called for a hexBinary attribute, > XSValue::getActValStrings() produces a binary bytestream equivalent of the > hexBinary string. It also appends a zero byte at the end of the bytestream. > While clients are able to access the bytestream (via > XSValue::fData.fValue.f_byteVal), there does not seem to be any way for > clients to tell how many bytes are in the stream without replicating some of > the logic used by XSValue::getActValStrings(). Checking for a zero byte is > not reliable, because zero bytes are valid in hexBinary values. > Suggest making XSValue::fData.fValue.f_byteVal a struct that includes the > length of the byte stream, as well as a pointer to it. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org