[
https://issues.jboss.org/browse/RF-13095?page=com.atlassian.jira.plugin.s...
]
Salvo Isaja commented on RF-13095:
----------------------------------
Brian, I'm no longer able to reproduce the problem and now the setter is called for
me, even downgrading from 4.3.3 back to 4.3.2. Unfortunately my project was not under
version control, so I can't check against the code as it was when I filed this issue.
It's likely it was due to my fault, as I've messed around with transient views,
request-only backing beans and fiddling with the request parameters to fool JSF and make
it accept my postbacks even in the stateless case (see also issue RF-13093). By the way,
the tableState setter is called even in this scenario, now.
If the reporter of RF-13126 has not a counterexample, please feel free to close this
issue. Thank you for your help.
extendedDataTable tableState setter not called on column
resize/reorder
-----------------------------------------------------------------------
Key: RF-13095
URL:
https://issues.jboss.org/browse/RF-13095
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-tables
Affects Versions: 4.3.2
Environment: GlassFish 3.1.2.2 with Mojarra 2.1.23, tested on Firefox 22 and
Chrome 28.
Reporter: Salvo Isaja
Assignee: Brian Leathem
Labels: waiting_on_user
Fix For: 4.3.4
Original Estimate: 1 hour
Remaining Estimate: 1 hour
Not sure if this qualifies as a bug or a feature request.
I have an extendedDataTable with the tableState attribute bound to a String property of a
backing bean (tried both a request scoped bean on a transient view and a session scoped
bean on a stateful view).
When resizing or reordering columns, an Ajax request is posted to the server, and I
correctly see the new column layouts in the request, but the setter of the tableState
property in the backing bean is not called. If I execute @form on a a4j:commandLink or
commandButton, it is called instead.
Thanks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira