[JBoss JIRA] Created: (RF-8531) org.ajax4jsf.model.SequenceRange is not serializable
by Darryl Smith (JIRA)
org.ajax4jsf.model.SequenceRange is not serializable
----------------------------------------------------
Key: RF-8531
URL: https://jira.jboss.org/jira/browse/RF-8531
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.3.2.SR1
Reporter: Darryl Smith
Caused by: java.io.NotSerializableException: org.ajax4jsf.model.SequenceRange
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156) [na:1.6.0_16]
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) [na:1.6.0_16]
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) [na:1.6.0_16]
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) [na:1.6.0_16]
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) [na:1.6.0_16]
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) [na:1.6.0_16]
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) [na:1.6.0_16]
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) [na:1.6.0_16]
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) [na:1.6.0_16]
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) [na:1.6.0_16]
at org.apache.catalina.session.StandardSession.writeObject(StandardSession.java:1478) [catalina.jar:na]
at org.apache.catalina.session.StandardSession.writeObjectData(StandardSession.java:948) [catalina.jar:na]
at org.apache.catalina.session.StandardManager.doUnload(StandardManager.java:517) [catalina.jar:na]
at org.apache.catalina.session.StandardManager.unload(StandardManager.java:463) [catalina.jar:na]
at org.apache.catalina.session.StandardManager.stop(StandardManager.java:667) [catalina.jar:na]
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4360) [catalina.jar:na]
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1067) [catalina.jar:na]
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1067) [catalina.jar:na]
at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:448) [catalina.jar:na]
at org.apache.catalina.core.StandardService.stop(StandardService.java:510) [catalina.jar:na]
at org.apache.catalina.core.StandardServer.stop(StandardServer.java:734) [catalina.jar:na]
at org.apache.catalina.startup.Catalina.stop(Catalina.java:602) [catalina.jar:na]
at org.apache.catalina.startup.Catalina.start(Catalina.java:577) [catalina.jar:na]
... 6 common frames omitted
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (RF-8524) Update JSF 2 version of 3.3.x to use built-in exception handler
by Nick Belaevski (JIRA)
Update JSF 2 version of 3.3.x to use built-in exception handler
----------------------------------------------------------------
Key: RF-8524
URL: https://jira.jboss.org/jira/browse/RF-8524
Project: RichFaces
Issue Type: Task
Security Level: Public (Everyone can see)
Components: core, JSF 2.0
Affects Versions: 3.3.3.CR1
Reporter: Nick Belaevski
Assignee: Andrey Markhel
Fix For: 3.3.3.Final
Implement support for built-in exception handlers in 3.3.x.
To achieve this:
1. Compare AjaxViewRoot#broadcastEvents method with UIViewRoot#broadcastEvents(FacesContext, PhaseId).
2. Replace AjaxViewRoot#broadcastEvents method with UIViewRoot#broadcastEvents(FacesContext, PhaseId) for JSF 2 branch of code.
3. Make sure events are being delivered properly. Subclasses of AjaxEvent (queued for RENDER_RESPONSE phase) should be checked either as action & value change events.
4. Check that exceptions from action listeners are handled the same as in JSF 1.2.
5. Attach custom exception handler and check that it actually works.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Commented: (RF-7813) Tablestate of ExtendedDataTable not read from managed Bean during Render-Response
by Lukas Fryc (JIRA)
[ https://jira.jboss.org/jira/browse/RF-7813?page=com.atlassian.jira.plugin... ]
Lukas Fryc commented on RF-7813:
--------------------------------
Reproducing sample - attached sample with modifications:
EDT have binding to TableBean.
+
call `edt.resetState()`; inside TableBean.actionListenerNewTableState method
> Tablestate of ExtendedDataTable not read from managed Bean during Render-Response
> ---------------------------------------------------------------------------------
>
> Key: RF-7813
> URL: https://jira.jboss.org/jira/browse/RF-7813
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 3.3.1
> Environment: Windows XP, Java 1.5.0_16, JSF Sun RI 1.2_13b01
> Reporter: Tobias Peper
> Assignee: Andrey Markhel
> Priority: Minor
> Fix For: 3.3.3.Final
>
> Attachments: sample-src.zip
>
>
> I hava a ExtendedDataTable and a CommandButton on the Page.
> The TableState of the table is bound to a String in a managed Bean.
> ActionListener of the CommandButton changes the tableState (for example column ordering) - but with no effect because the tableState is not read from the managed Bean during the Render-Response-Phase.
> Quick fix for me was inserting the follings two lines to the Method beforeRenderResponse(FacesContext) of org.richfaces.component.UIExtendedDataTable:
> ----------
> state = null;
> setTableState(null);
> ----------
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Closed: (RF-7813) Tablestate of ExtendedDataTable not read from managed Bean during Render-Response
by Lukas Fryc (JIRA)
[ https://jira.jboss.org/jira/browse/RF-7813?page=com.atlassian.jira.plugin... ]
Lukas Fryc closed RF-7813.
--------------------------
> Tablestate of ExtendedDataTable not read from managed Bean during Render-Response
> ---------------------------------------------------------------------------------
>
> Key: RF-7813
> URL: https://jira.jboss.org/jira/browse/RF-7813
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 3.3.1
> Environment: Windows XP, Java 1.5.0_16, JSF Sun RI 1.2_13b01
> Reporter: Tobias Peper
> Assignee: Andrey Markhel
> Priority: Minor
> Fix For: 3.3.3.Final
>
> Attachments: sample-src.zip
>
>
> I hava a ExtendedDataTable and a CommandButton on the Page.
> The TableState of the table is bound to a String in a managed Bean.
> ActionListener of the CommandButton changes the tableState (for example column ordering) - but with no effect because the tableState is not read from the managed Bean during the Render-Response-Phase.
> Quick fix for me was inserting the follings two lines to the Method beforeRenderResponse(FacesContext) of org.richfaces.component.UIExtendedDataTable:
> ----------
> state = null;
> setTableState(null);
> ----------
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Commented: (RF-7813) Tablestate of ExtendedDataTable not read from managed Bean during Render-Response
by Lukas Fryc (JIRA)
[ https://jira.jboss.org/jira/browse/RF-7813?page=com.atlassian.jira.plugin... ]
Lukas Fryc commented on RF-7813:
--------------------------------
Reproduced in 3.3.3.CR1, verified in 3.3.3.Final
> Tablestate of ExtendedDataTable not read from managed Bean during Render-Response
> ---------------------------------------------------------------------------------
>
> Key: RF-7813
> URL: https://jira.jboss.org/jira/browse/RF-7813
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 3.3.1
> Environment: Windows XP, Java 1.5.0_16, JSF Sun RI 1.2_13b01
> Reporter: Tobias Peper
> Assignee: Andrey Markhel
> Priority: Minor
> Fix For: 3.3.3.Final
>
> Attachments: sample-src.zip
>
>
> I hava a ExtendedDataTable and a CommandButton on the Page.
> The TableState of the table is bound to a String in a managed Bean.
> ActionListener of the CommandButton changes the tableState (for example column ordering) - but with no effect because the tableState is not read from the managed Bean during the Render-Response-Phase.
> Quick fix for me was inserting the follings two lines to the Method beforeRenderResponse(FacesContext) of org.richfaces.component.UIExtendedDataTable:
> ----------
> state = null;
> setTableState(null);
> ----------
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months