xpath constrictions?

HansGrund

Hi BIRT-fellows,<br />
<br />
seems I have a similar problem like Marco in<br />
[post]43214[/post] <br />
<br />
For a data set from an xml-file I try to<br />
map a data set column to this xpath expression<br />
<br />
<strong class='bbc'>//partner/child::*[rollenid = 1]/name</strong><br />
<br />
and BIRT just brings an empty field,<br />
whereas other xpath-interpreters, e.g. Xerces or Saxon,<br />
bring the correct value.<br />
<br />
Maybe BIRT has some serious constrictions<br />
on xpath predicates and language elements?<br />
<br />
Is there some documentation on how BIRT does<br />
xpath evaluation, and what versions or xpath<br />
expressions are (not) supported by BIRT?<br />
<br />
Thank you for any help!

HansGrund

Looking at the XML source of the rptdesign
the data set property "queryText" contains:

<property name="queryText">
table0#-TNAME-#table0#:#[//partner/*[rollenid=1]]#:#
{ort;STRING;ort},{vorname;STRING;vorname},{name;STRING;name},
{geburtsdatum;STRING;geburtsdatum},{rollenid;STRING;rollenid}</property>

When I omit the xpath predicate "[rollenid=1]" all runs well.
So obviously BIRT cannot cope with Xpath predicates!?
If this holds true, I would assess this issue as a rather severe limitation
of BIRT XML data set usage.

Thanks for any advice or further information!