xxforms:if test -> problem

> Hello
>
> Congratulations on an excellent product!
>
> A question:
> I would like test for the existence of a node in the empty-instance file or data file, and only display an input field, if the corresponding element is present.
>
> I have the following code in the xsl file:
> <xxforms:if test="boolean(claim:criteria_for_selecting_genome)">
>                 <tr><th align="right" valign="middle">Criteria for Selecting Genome</th><td>
>                 <xforms:textarea ref="claim:criteria_for_selecting_genome">
>                 <xforms:hint></xforms:hint>
>                 <xforms:help></xforms:help>
>                 </xforms:textarea>
>
>                 </td></tr>
>         </xxforms:if>
>
> This works fine if I exclude the input field. However, an error occurs if the input field is included:
> Single-node binding expression 'claim:criteria_for_selecting_genome' returned an empty nodeset
>
> My question is:
> Does anyone know what the problem is with the above code and/or can suggest a method whereby I can test for the existence of a node in an xml file, and display an xforms input field only if the node exists?
>
> thank you for any help with this
> Tanya
>
>
>
>
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>

> Hi Tanya,
>
> What version of OPS are you using? If you are using OPS 2.8 (or 3.0 in
> "XForms Classic" mode) this should work and I would have to ask you if
> you can send us an example of your code.
>
> If you are using OPS 3.0, xxforms:if is an extension that we are not
> planning to support it in OPS 3.0. However in OPS 3.0, the behavior
> you expect will come out of the box. That means that if the "ref"
> expression on your control returns an empty nodeset, then the control
> is not displayed, as specified in the XForms W3C recommendation. The
> current build do not implement this yet. Instead it returns an error
> in this case ("Single-node binding expression 'xxx' returned an empty
> nodeset"), but this will change by the time the final OPS 3.0 is
> released. For reference see:
>
> http://forge.objectweb.org/tracker/index.php?func=detail&aid=304146&group_id=168&atid=350207

> Alex, thank you for your explanation. I am using OPS version 3 beta. Has a date been set for the final release of version 3?
>
> Regarding Erik's message, the error occurred in a modified version of the detail-1.xsl page of the bizdoc example. Extracts from this file are below.
>
> Tanya
>
> test.xsl page
> ============
>
>
> <xforms:group ref="/form" xxforms:show-errors="{doc('input:instance')/form/show-errors = 'true'}">
>                 <xi:include href="../summary/view-logo.xml"/>
>                 <xi:include href="detail-view-header.xml"/>
>                 <xforms:group ref="document">
>                     <xforms:group ref="claim:claim">
>                        
> <xxforms:if test="boolean(claim:criteria_for_selecting_genome)">
> <tr><th align="right" valign="middle">Criteria for Selecting Genome</th><td>
> <xforms:textarea ref="claim:criteria_for_selecting_genome">
> <xforms:hint></xforms:hint>
> <xforms:help></xforms:help>
> </xforms:textarea>
>
> </td></tr>
> </xxforms:if>

> I have a slight problem with the <xforms:help> tags in the page below.
> It's a simple search xform with 7 input fields. Each field has a
> different <cforms:help> element but when I access the page, all the help
> icons get assigned the same help text (from the first field). I don't
> see thi problem in the example pages but not sure what I'm doing wrong
> (using OPS Beta 3.0).
> thanks
> Pascal
>
>
>
>
>
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <xsl:stylesheet version="2.0"
>     xmlns="http://www.w3.org/1999/xhtml"
>     xmlns:dyn="http://exslt.org/dynamic"
>     xmlns:ev="http://www.w3.org/2001/xml-events"
>     xmlns:f="http://orbeon.org/oxf/xml/formatting"
>     xmlns:str="http://exslt.org/strings"
>     xmlns:xforms="http://www.w3.org/2002/xforms"
>     xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>     xmlns:xs="http://www.w3.org/2001/XMLSchema"
>     xmlns:xxforms="http://orbeon.org/oxf/xml/xforms"
>     >
>     <xsl:template match="/">
>         <html>
>             <head>
>                 <title>Survey Search Page</title>
>                 <!-- XFORMS MODEL -->
>                 <xforms:model id="main-model">
>                     <xforms:instance id="search-instance">
>                         <form xmlns="">
>                             <action/>
>                             <ddi>
>                                 <title/>
>                                 <yearFrom/>
>                                 <yearTo/>
>                                 <country/>
>                                 <type/>
>                                 <surveyKeywords/>
>                                 <dataKeywords/>
>                             </ddi>
>                         </form>
>                     </xforms:instance>
>                     <xforms:bind nodeset="/form/ddi/yearFrom"
> type="xs:integer" constraint=".='' or (. castable as xs:integer and . >=
> 1990 and 2020 >= .)"/>
>                     <xforms:bind nodeset="/form/ddi/yearTo"
> type="xs:integer" constraint=".='' or (. castable as xs:integer and . >=
> 1990 and 2020 >= .)"/>
>                     <xforms:submission id="search" method="post"
> action="/catalog/search"/>
>                 </xforms:model>
>             </head>
>             <body class="maincontent">
>                 <h1>Search survey catalog</h1>
>                 <div style="margin-left:20px;">
>                     <xforms:group ref="/form">
>                         <p>
>                             *<xforms:input ref="ddi/title">*
>                                 <xforms:label
> class="fixed-width">Title</xforms:label>
>                                 *<xforms:help>Search for words in the
> survey title, subtitle, translated title or abbreviation.</xforms:help>*
>                             </xforms:input>
>                         </p>
>                         <p>
>                            * <xforms:input ref="ddi/country">*
>                                 <xforms:label
> class="fixed-width">Country</xforms:label>
>                                 *<xforms:help>Search for words in the
> survey country or ISO code.</xforms:help>*
>                             </xforms:input>
>                         </p>
>                         <p>
>                             *<xforms:input ref="ddi/yearFrom"
> style="width: 4em;">*
>                                 <xforms:label
> class="fixed-width">Starting Year</xforms:label>
>                                 <xforms:alert>START YEAR must be a
> number between 1990 and 2020</xforms:alert>
>                                 *<xforms:help>Search in year of data
> collection or survey temporal coverage. Must be between 1990 and
> 2020.</xforms:help>*
>                             </xforms:input>
>                         </p>
>                         <p>
>                             *<xforms:input ref="ddi/yearTo"
> style="width: 4em;">*
>                                 <xforms:label class="fixed-width">End
> Year</xforms:label>
>                                 <xforms:alert>END YEAR must be a number
> between 1990 and 2020</xforms:alert>
>                                * <xforms:help>Search in year of data
> collection or survey temporal coverage. Must be between 1990 and
> 2020.</xforms:help>*
>                             </xforms:input>
>                         </p>
>                         <p>
>                             *<xforms:input ref="ddi/surveyKeywords">*
>                                 <xforms:label class="fixed-width">Survey
> keywords</xforms:label>
>                                 *<xforms:help>Search for keywords in all
> the descripive elements of the survey</xforms:help>*
>                             </xforms:input>
>                         </p>
>                         <p>
>                             *<xforms:input ref="ddi/dataKeywords">*
>                                 <xforms:label class="fixed-width">Data
> keywords</xforms:label>
>                                 *<xforms:help>Search for keywords in the
> data dictionary</xforms:help>*
>                             </xforms:input>
>                         </p>
>                         <p>
>                             <span class="fixed-width"> </span>
>                             <xforms:trigger submission="search">
>                                 <xforms:label>Search in files</xforms:label>
>                                 <xforms:action ev:event="DOMActivate">
>                                     <xforms:setvalue
> ref="/form/action">search-files</xforms:setvalue>
>                                     <xforms:send submission="search"/>
>                                 </xforms:action>
>                             </xforms:trigger>
>                             <xforms:trigger submission="search">
>                                 <xforms:label>Search in XML
> catalog</xforms:label>
>                                 <xforms:action ev:event="DOMActivate">
>                                     <xforms:setvalue
> ref="/form/action">search-xml-catalog</xforms:setvalue>
>                                     <xforms:send submission="search"/>
>                                 </xforms:action>
>                             </xforms:trigger>
>                             <xforms:trigger submission="search">
>                                 <xforms:label>Search in
> XML-DB</xforms:label>
>                                 <xforms:action ev:event="DOMActivate">
>                                     <xforms:setvalue
> ref="/form/action">search-db</xforms:setvalue>
>                                     <xforms:send submission="search"/>
>                                 </xforms:action>
>                             </xforms:trigger>
>                         </p>
>                     </xforms:group>
>                 </div>
>             </body>
>         </html>
>     </xsl:template>
> </xsl:stylesheet>
>
>
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

> Pascal,
>
> I thought this bug had been fixed, but I may be wrong. Are you using
> OPS 3.0 beta 3, or OPS 3.0 beta 2? First thing is to make sure you are
> using beta 3 (released on September 2).
>
> -Erik
>
> Pascal Heus wrote:
>
>> I have a slight problem with the <xforms:help> tags in the page
>> below. It's a simple search xform with 7 input fields. Each field has
>> a different <cforms:help> element but when I access the page, all the
>> help icons get assigned the same help text (from the first field). I
>> don't see thi problem in the example pages but not sure what I'm
>> doing wrong (using OPS Beta 3.0).
>> thanks
>> Pascal
>>

> Erik:
> I'm running Beta-2.... I just updated my Eclipse plugin and restarted
> but it still starts ops beta-2 version when I run. The plugin is
> reported as 1.2.3.200509020246. Is there an Eclipse upgrade procedure?
> Is beta-3 available as a stand alone package as well or only in CVS?
> thanks
> Pascal
>
> Erik Bruchez wrote:
>
>> Pascal,
>>
>> I thought this bug had been fixed, but I may be wrong. Are you using
>> OPS 3.0 beta 3, or OPS 3.0 beta 2? First thing is to make sure you are
>> using beta 3 (released on September 2).
>>
>> -Erik
>>
>> Pascal Heus wrote:
>>
>>> I have a slight problem with the <xforms:help> tags in the page
>>> below. It's a simple search xform with 7 input fields. Each field has
>>> a different <cforms:help> element but when I access the page, all the
>>> help icons get assigned the same help text (from the first field). I
>>> don't see thi problem in the example pages but not sure what I'm
>>> doing wrong (using OPS Beta 3.0).
>>> thanks
>>> Pascal
>>>
>
>
>
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

> If you are using OPS 3.0, xxforms:if is an extension that we are not
> planning to support it in OPS 3.0. However in OPS 3.0, the behavior
> you expect will come out of the box. That means that if the "ref"
> expression on your control returns an empty nodeset, then the control
> is not displayed, as specified in the XForms W3C recommendation. The
> current build do not implement this yet. Instead it returns an error
> in this case ("Single-node binding expression 'xxx' returned an empty
> nodeset"), but this will change by the time the final OPS 3.0 is
> released. For reference see:
>
> http://forge.objectweb.org/tracker/index.php?func=detail&aid=304146&group_id=168&atid=350207

> If you are using OPS 3.0, xxforms:if is an extension that we are not
> planning to support it in OPS 3.0. However in OPS 3.0, the behavior
> you expect will come out of the box. That means that if the "ref"
> expression on your control returns an empty nodeset, then the control
> is not displayed, as specified in the XForms W3C recommendation. The
> current build do not implement this yet. Instead it returns an error
> in this case ("Single-node binding expression 'xxx' returned an empty
> nodeset"), but this will change by the time the final OPS 3.0 is
> released. For reference see:
>
> http://forge.objectweb.org/tracker/index.php?func=detail&aid=304146&group_id=168&atid=350207

> Hello,
>
> further to posts here, I have looked at the XFORMS NG examples provided with OPS, and find that I get the run-time error described previously, if I remove an element in the form empty instance, that is referenced by an xforms:input field.
>
> For example, the XFORMS Switch Wizard: removing the <firstname> element from the form instance causes a run-time error.
>
> I am using OPS 3 beta.
>
> regards
> Tanya