Hi James-
If you use Facelets with MyFaces 1.1.3, then you'll have the full unified EL. :)
Adam Brod
Product Development Team
| "James Richards"
<[EMAIL PROTECTED]>
06/16/2006 12:32 PM
|
|
Is it correct to assume, based upon the following:
http://mail-archives.apache.org/mod_mbox/myfaces-dev/200605.mbox/%3c30773=
[EMAIL PROTECTED]
that Unified EL is not supported in MyFaces 1.1.3? If that's true,
I =
have an interesting question:
I have a custom scrolling implementation which is somewhat working but
=
is losing its state during certain view actions. I would like to
be =
able to declaratively attach one visual component to another to resolve
=
the problem properly. For example, I have a=20
<z:paginationState id=3D"paginationState" bean=3D"#{facilityForm}"/>
<z:customPaginationDataTable id=3D"facilityLedgerData"
styleClass=3D"data"
rowClasses=3D"oddRow,evenRow"
=
columnClasses=3D"width125,width100,width100,width100,width100,width300,bu=
ttons"
footerClass=3D"footer"
var=3D"entry"
rows=3D"#{facilityForm.ledgerHandler.rows}"
value=3D"#{facilityForm.ledgerModel}"
cellspacing=3D"1"
width=3D"100%"
preserveSort=3D"true"
rowIndexVar=3D"index">
<% /* ... */ %>
</z:customPaginationDataTable>
What I would *like* to be able to do is attach the paginationState =
directly to the custom table using something like
<z:paginationState id=3D"paginationState" =
bean=3D"#{facilityLedgerData}"/>
So that the facilityLedgerData can query its pagination state. When
the =
scroller fires an scrolling event, custom pagination for the table will
=
be disabled until a new view is created.
I tried this on 1.1.1 and it didn't work so I used a very ugly hardcoded
=
approach of locating the scroller and the pagination state in Java code
=
via the ViewRoot and then attaching the pagination state to the scroller
=
as an ActionListener.
What I would like to do is be able to add the paginationState to the =
scroller using something like "actionListener=3D"#{paginationState}"
but =
it seems that I would need Unified EL to do this? I tried this out
on =
1.1.1 but it didn't work, though I could attach a backing bean as an =
action listener.
Is there any way to declaratively, in the JSF, bind one UI Component to
=
another?
This solution:
http://www.mail-archive.com/[email protected]/msg16266.html
is not what I am looking for.
Thanks,
James
Disclaimer: This electronic mail and any attachments are confidential and may be privileged. If you are not the intended recipient, please notify the sender immediately by replying to this email, and destroy all copies of this email and any attachments. Thank you.
