Jos Vos wrote:

> Hmm, yes, but this introduces another problem in my case: I *also*
> want to use the "new" data *inside* the when/otherwise clause
> itself, and as soon as I do this, the associated id is not
> recognized outside the p:choose as it is considered to be an
> "choose-internal" id:
>
>
>  <p:config>
>     <p:param name="abc" type="output">
>     ...
>     <p:choose ...>
>        <p:when ...>
>           <p:processor ...>
>              <p:output name="data" id="abc-output" ref="abc"/>
>           </p:processor>
>           <p:processor ...>
>              <p:input name="data" href="#abc-output"/>
>           </p:processor>
>         </p:when>
>         ...
>      </p:choose>
>
>      <!-- THIS DOES NOT WORK NOW -->
>      <p:processor name="oxf:null-serializer">
>         <p:input name="data" href="#abc-output"/>
>      </p:processor>
>
>  </p:config>
>
>
> Do you maybe have a "smart" solution for this (except calling
> another identity processor in the when part)? ;-)

Do all the branches "export" the id "abc-output"? If so, this should
work. If not, it cannot work, because then if another branch is taken
href="#abc-output" doesn't refer to anything.

-Erik



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
orbeon-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/orbeon-user

Reply via email to