[JBoss JIRA] Created: (RF-3517) Entered values in rich:subTable are lost upon validation errors
by Jonck van der Kogel (JIRA)
Entered values in rich:subTable are lost upon validation errors
---------------------------------------------------------------
Key: RF-3517
URL: http://jira.jboss.com/jira/browse/RF-3517
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.4
Environment: Windows Vista, JBoss 4.0.5, JSF 1.2
Reporter: Jonck van der Kogel
Given the following sample code:
<rich:dataTable
value="#{backingBean.holders}"
var="holder">
<f:facet name="header">
<rich:columnGroup>
<rich:column>
<h:outputText value="Test">
</rich:column>
</rich:columnGroup>
</f:facet>
<rich:column>
<h:inputText value="#{holder.requiredTest}" required="true" />
</rich:column>
<rich:subTable
value="#{holder}"
var="holderSubTable">
<rich:column colspan="1">
<h:inputText value="#{holderSubTable.test}" />
</rich:column>
</rich:subTable>
</rich:dataTable>
When the surrounding form is submitted, the "test" field in the rich:subTable is cleared when a validation error occurs. This is not the expected behavior, normally in JSF when a validation error occurs the entered values remain.
To illustrate this, I rebuilt the above scenario but now placed all fields within the same rich:dataTable like so:
<rich:dataTable
value="#{backingBean.holders}"
var="holder">
<f:facet name="header">
<rich:columnGroup>
<rich:column>
<h:outputText value="Test">
</rich:column>
<rich:column>
<h:outputText value="Test2">
</rich:column>
</rich:columnGroup>
</f:facet>
<rich:column>
<h:inputText value="#{holder.requiredTest}" required="true" />
</rich:column>
<rich:column>
<h:inputText value="#{holder.test}" />
</rich:column>
</rich:dataTable>
In this case when the form is submitted and a validation error occurs the "test" field is not cleared, as expected.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (RF-5598) a4j:push is not portlet session aware
by Dirk Pitt (JIRA)
a4j:push is not portlet session aware
-------------------------------------
Key: RF-5598
URL: https://jira.jboss.org/jira/browse/RF-5598
Project: RichFaces
Issue Type: Bug
Components: portal
Affects Versions: 3.3.0
Environment: Richfaces 3.3.0.CR2, JBoss Portletbridge 1.0.0.B5, JBoss Portal 2.6.4
Reporter: Dirk Pitt
Hallo,
I have funny problem with a4j:pushBean...
We have a web application, which runs perfectly in test environment with single web client.
But if for the same page in the web application another browser client is opened, second browser start receiving the events intended for the first browser...
So my first impression is that push functionality make no distinction about from which session is called...
So I surf little bit in the source code and here what I found....
In org.ajax4jsf.webapp.BaseFilter an instance of PushEventsCounter is obtained with the following call
PushEventsCounter listener = eventsManager .getListener(ajaxPushHeader);
which my debuging shows ajaxPushHeader contains no session specific information. At this point I have to say I am using the JBoss Portal and JBoss Portlet Bridge.
I made some more debuging and I found this....
In org.ajax4jsf.component.UIPush in method getListenerId method only HttpSession case taking into count....
Object session = context.getExternalContext().getSession(false);
StringBuffer id = new StringBuffer();
if(null != session && session instanceof HttpSession){
HttpSession httpSession = (HttpSession) session;
id.append(httpSession.getId());
}
id.append(context.getViewRoot().getViewId());
id.append(NamingContainer.SEPARATOR_CHAR);
id.append(getClientId(context));
return id.toString();
But portal delivers PortletSession object so the SessionId is not there at that is causing the mentioned problem...
Now this problem is quite critical for our project and I can actually deliver code solution to be commited jboss source tree also but the question is how to solve this without putting portal dependencies to Richfaces classes...
Or can we solve this PortletBridge?
--
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, 7 months
[JBoss JIRA] Created: (RF-4398) Form: ajax form doesn't handle ajaxSingle in the right way
by Nick Belaevski (JIRA)
Form: ajax form doesn't handle ajaxSingle in the right way
----------------------------------------------------------
Key: RF-4398
URL: https://jira.jboss.org/jira/browse/RF-4398
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.2
Reporter: Nick Belaevski
Assignee: Alexander Smirnov
Fix For: Future
<a4j:form ajaxSubmit="true" ajaxSingle="true" id="a4jform">
Ajax single
<h:inputText />
<h:commandButton actionListener="#{capitalsBean.action}" value="Button" id="button" />
</a4j:form>
Pressing button submits the following parameters:
AJAXREQUEST _viewRoot
a4jform a4jform
a4jform a4jform
a4jform:button Button
a4jform:j_id236 22
ajaxSingle a4jform
autoScroll
javax.faces.ViewState j_id2
ajaxSingle should be a4jform:button, duplicate parameters should not be submitted
--
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, 7 months