[JBoss JIRA] Created: (RF-4599) scrollableDataTable: PrototypeScript crash during increase data length from 100 to 1000.
by Mikhail Vitenkov (JIRA)
scrollableDataTable: PrototypeScript crash during increase data length from 100 to 1000.
----------------------------------------------------------------------------------------
Key: RF-4599
URL: https://jira.jboss.org/jira/browse/RF-4599
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.0
Environment: Facelets - jdk1.5.0_12 - tomcat 6.0.16 - jsf 1.2_09 - FF 3.0.3(RichFaces 3.3.0-SNAPSHOT )
Reporter: Mikhail Vitenkov
Assignee: Nick Belaevski
Priority: Critical
Step 1. Set following precondition for SDT component:
length=" 100" rows="100" first="0" timeout="0" frozencolcount="0" limitToList="false"
bypassUpdates="false" ajaxSingle="true" hideWhenScrolling="false".
Step 2. Start the server(see Environment section) & open page in Firefox.
Step 3. Set rows to 500 & click mouse out.
Step 4. Set length to 1000 & click "OK" button.
Actual behavior:
Modal dialog window with suggestions to stop script, to debug script or to continue appears. For more information see attached PrototypeScriptError.png
--
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, 9 months
[JBoss JIRA] Created: (RF-4362) inplaceSelect: oneditactivation fired after oneditactivated
by Tatyana Romanovich (JIRA)
inplaceSelect: oneditactivation fired after oneditactivated
-----------------------------------------------------------
Key: RF-4362
URL: https://jira.jboss.org/jira/browse/RF-4362
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.2
Environment: RF-3.2.2.CR2
Reporter: Tatyana Romanovich
Assignee: Nick Belaevski
Priority: Minor
1. Create tested application with code:
<rich:inplaceSelect id="iSId1"
............................
oneditactivation="if (!confirm('Are you sure you want to change value?')){return false;}">
<f:selectItems value="#{inplaceComponentsBean.capitals}" />
<f:selectItem itemLabel="Outras Atividades" itemValue="10" />
<a4j:support event="onviewactivated" oncomplete="alert ('Some functions');"/>
</rich:inplaceSelect>
2. Run application on the server
3. Click on the inplaceSelect component.
Result: confirm dialog appears
4. Click OK button.
Result: alert appears (oneditactivated fired)
5. Click Ok button
FAILURE: confirm dialog appears again, i.e. oneditactivation fired again.
--
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, 9 months
[JBoss JIRA] Created: (RF-4455) Implement Maven 2 Seam application for regression testing
by Nick Belaevski (JIRA)
Implement Maven 2 Seam application for regression testing
----------------------------------------------------------
Key: RF-4455
URL: https://jira.jboss.org/jira/browse/RF-4455
Project: RichFaces
Issue Type: Task
Affects Versions: 3.3.0
Reporter: Nick Belaevski
Assignee: Vladimir Molotkov
Priority: Critical
Fix For: 3.3.0
Implement Seam application for regression testing
Requirements:
1. Seam & RichFaces versions set in pom file and should be switched easily by setting properties from command line
2. Application should be packaged as EAR deployable to JBoss 4.2 or 4.3
3. Datasource for HSQL DB should be set up and SQL import should happen on JBoss startup
4. JSP and Facelet pages should be working side-by-side
5. Selenium should be set up and ready to to run integration tests by invoking mvn clean integration-test
--
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, 9 months
[JBoss JIRA] Created: (RF-4248) a serious design defect
by zhou careprad (JIRA)
a serious design defect
-----------------------
Key: RF-4248
URL: https://jira.jboss.org/jira/browse/RF-4248
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.4
Reporter: zhou careprad
Priority: Minor
Fix For: 3.1.x
We encounter a serious problem in the project that based on richfaces.
for example:
<h:panelGrid id="boxGrid" binding="#{bean.boxGrid}">
</h:panelGrid>
<a4j:commandButton ajaxSingle="true" id="testButton" value="TEST"
binding="#{bean.testButton}"></a4j:commandButton>
<h:panelGrid style="display:none">
<a4j:poll id="poll"
actionListener="#{pollRequestBean.poll}"
binding="#{pollRequestBean.pollButton}" interval="2000"
/>
</h:panelGrid>
as you see,we want to modify the panelGrid(id="boxGrid") when user click the button(id="testButton"),then when rerender,some changes will show in the content
of the panelgrid.And,the poll is also what we needed(the reason is affirmative). But this has a big problem--synchronization!
in such case:a user click a button,richfaces fire the event to it's listener(alias as 'la'),and the listener(la) began to update the boxGrid(the back-binding of the
panelGrid),in the same time,the poll also come to request,what happen--the new comming request will update the richfaces' component tree,the boxGrid(the back-binding)
also update,but the listener(la) did not know this,it still hold the old model,this cause the change to the model has no mean to the ui.
We have try many method to solve this problem,but all is in vain.you may think push,the push alos will update the component tree when the event is fired.
I think this a serious problem to richfaces.
--
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, 9 months