Trigger in repeat in group

nicolaspujol73 wrote

Hi,

 I am not sure if this by design or a bug but why is it that the nodeset arg of
an xforms:insert seems
to ignore the context established by a surrounding a group ? I have to refer to
make the nodeset absolute to the instance doc not relative, I also tried the
xforms 1.1 context function . No luck. Any suggestions? Thanks!

<xforms:group ref="section[@id='FORM_OA_ADDRESS_PHONE']>
   <xforms:trigger>
          <xforms:action ev:event="DOMActivate">
         
                   
                  <xforms:insert
nodeset="instance('fr-metadata')/section[@id='FORM_OA_ADDRESS_PHONE']/item"
at="last()" position="after"></xforms:insert>
   
                   
                       <xforms:insert nodeset="item" at="last()"
position="after"></xforms:insert>
                    </xforms:insert>

         
                       <xforms:insert nodeset="context()/item" at="last()"
position="after"></xforms:insert>
                    </xforms:insert>

           </xforms:action>
   </xforms:trigger>       
  <xforms:repeat id="repeat-FORM_OA_ADDRESS_PHONE" nodeset="item">     
   ....
  </xforms:repeat>                           
<xforms:group>


--
You receive this message as a subscriber of the ops-users@ow2.org mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Philip.Cantin wrote

Nicolas,

Have a look at this link here:

http://wiki.orbeon.com/forms/how-to/repeat-insert-position


Notice how you use the 'context' attribute of <xforms:insert> to establish the context of where you want to add the node, and the 'origin' attribute to establish what node you would like to add.

Also, within an <xforms:group>, the context attribute of an <xforms:insert> statement will be relative to the ref attribute of the enclosing <xforms:group> statement.


Hope this helps,

Philip

nicolaspujol73 wrote

Hi,

 I am not sure if this by design or a bug but why is it that the nodeset arg of
an xforms:insert seems
to ignore the context established by a surrounding a group ? I have to refer to
make the nodeset absolute to the instance doc not relative, I also tried the
xforms 1.1 context function . No luck. Any suggestions? Thanks!

<xforms:group ref="section[@id='FORM_OA_ADDRESS_PHONE']>
   <xforms:trigger>
          <xforms:action ev:event="DOMActivate">
         
                   
                  <xforms:insert
nodeset="instance('fr-metadata')/section[@id='FORM_OA_ADDRESS_PHONE']/item"
at="last()" position="after"></xforms:insert>
   
                   
                       <xforms:insert nodeset="item" at="last()"
position="after"></xforms:insert>
                    </xforms:insert>

         
                       <xforms:insert nodeset="context()/item" at="last()"
position="after"></xforms:insert>
                    </xforms:insert>

           </xforms:action>
   </xforms:trigger>       
  <xforms:repeat id="repeat-FORM_OA_ADDRESS_PHONE" nodeset="item">     
   ....
  </xforms:repeat>                           
<xforms:group>


--
You receive this message as a subscriber of the ops-users@ow2.org mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

npujol wrote

Great . Just tried that and it worked very well. Quick follow up question, do you have any suggestions as to setting up a binding on a trigger so as to limit the number of entries WHEN in a nested repeat situation? If I refer to the binding by name how do i refer to a nested trigger if orbeon's recommendation is NOT to use the index function outside an action.

Thanks for any ideas and the tip from earlier.

Philip.Cantin wrote

Nicolas,

Have a look at this link here:

http://wiki.orbeon.com/forms/how-to/repeat-insert-position


Notice how you use the 'context' attribute of <xforms:insert> to establish the context of where you want to add the node, and the 'origin' attribute to establish what node you would like to add.

Also, within an <xforms:group>, the context attribute of an <xforms:insert> statement will be relative to the ref attribute of the enclosing <xforms:group> statement.


Hope this helps,

Philip

nicolaspujol73 wrote

Hi,

 I am not sure if this by design or a bug but why is it that the nodeset arg of
an xforms:insert seems
to ignore the context established by a surrounding a group ? I have to refer to
make the nodeset absolute to the instance doc not relative, I also tried the
xforms 1.1 context function . No luck. Any suggestions? Thanks!

<xforms:group ref="section[@id='FORM_OA_ADDRESS_PHONE']>
   <xforms:trigger>
          <xforms:action ev:event="DOMActivate">
         
                   
                  <xforms:insert
nodeset="instance('fr-metadata')/section[@id='FORM_OA_ADDRESS_PHONE']/item"
at="last()" position="after"></xforms:insert>
   
                   
                       <xforms:insert nodeset="item" at="last()"
position="after"></xforms:insert>
                    </xforms:insert>

         
                       <xforms:insert nodeset="context()/item" at="last()"
position="after"></xforms:insert>
                    </xforms:insert>

           </xforms:action>
   </xforms:trigger>       
  <xforms:repeat id="repeat-FORM_OA_ADDRESS_PHONE" nodeset="item">     
   ....
  </xforms:repeat>                           
<xforms:group>


--
You receive this message as a subscriber of the ops-users@ow2.org mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws