Hi,
Further to this, I now wonder whether there is a more general problem with the behaviour of concat as I having the same problem (with the same elements) in my page-flow.xml.
I am trying a workaround to the setvalue problem so in my page-flow.xml I have:
<xu:update select="/form/document/vr:Resource/vr:identifier" xmlns:vr="http://www.ivoa.net/xml/VOResource/v0.10";>
<xu:value-of select="concat(document('oxf:instance')/form/authority, document('oxf:instance')/form/document/vr:Resource/vr:identifier)"/>
</xu:update>
but again this does not anything.
Any ideas?
Cheers,
Matthew
On Jan 22, 2005, at 12:13 AM, Matthew J. Graham wrote:
Hi,
It looks as though a bug has crept into the behaviour of xforms:setvalue from 2.6 to 2.7.2:
in my view I have:
<xforms:setvalue ref="/form/document/vr:Resource/vr:identifier" value="concat(/form/authority, /form/document/vr:Resource/vr:identifier)"/>
However, all this actually does is set the value of /form/document/vr:Resource/vr:identifier to just the value of /form/authority and not the concatenation of the two elements. If, however, I use something else, e.g. value="concat(/form/authority, /form/document/vr:Resource/vr:title", then the concatenation works fine. So it just seems to be that the same element cannot appear in the ref and the value statements.
Any ideas?
Cheers,
Matthew
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ orbeon-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/orbeon-user
