Hmmm ... embedded elements indeed used the current value of the
template tag as their embed value. This was done before it was
possible to pass a data object to processEmbeddedElement as a way to
be able to provide data to the embedded element. This is now not
needed anymore and actually (as you just showed) not a good idea. I
reverted it to the initial behavior (of a few months ago) where the
embedded element's value tag's default content is now always used.
Your issue should thus be solved with the next nightly build.
Best regards,
Geert
On 16 Jun 2006, at 13:55, [EMAIL PROTECTED] wrote:
Hi,
Triggered and inspired by Eddy's Component example and Frederic's
Sortable
table, I tried this in my dynamic embedded situation in an attempt
to make
more generic component:
template snippet:
<table id="row" class="displaytag">
${v seatEntries}
<tr><td>No travellers</td></tr>
${/v}
${b seatEntry}
${v ELEMENT:+.SeatEntry:}
MODE = ManageReservation
${/v}
${/b}
</table>
In the code of the embedded element only the first invocation
'found' the
MODE properties, the second invocation saw the 'generated html' of the
first invocation.
Does this have anything to do with the structure of my template or
is it
'normal' cq intended behaviour?
Regards,
Adriaan
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
--
Geert Bevin
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
