From jira-events at lists.jboss.org Fri Jan 2 08:21:54 2009 From: jira-events at lists.jboss.org (Nick Belaevski (JIRA)) Date: Fri, 2 Jan 2009 08:21:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Resolved: (RF-3510) toolTip: JS API doesn't work for toolTip, which doesn't contain parent component. In-Reply-To: <8968944.1211464499947.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <20715976.1230902514567.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Belaevski resolved RF-3510. -------------------------------- Resolution: Cannot Reproduce Bug Assignee: Mikhail Vitenkov (was: Nick Belaevski) DEFAULT VALUE > toolTip: JS API doesn't work for toolTip, which doesn't contain parent component. > --------------------------------------------------------------------------------- > > Key: RF-3510 > URL: https://jira.jboss.org/jira/browse/RF-3510 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.1 > Environment: IE, FF, Safari, Opera(3.2.1.CR5) > Reporter: Mikhail Vitenkov > Assignee: Mikhail Vitenkov > > Step 1. Add rich:toolTip on the page: > hideDelay="#{tooltip.hideDelay}" showDelay="#{tooltip.showDelay}" layout="#{tooltip.layout}" > horizontalOffset="#{tooltip.horizontalOffset}" verticalOffset="#{tooltip.verticalOffset}" followMouse="#{tooltip.followMouse}" > direction="#{tooltip.direction}" disabled="#{tooltip.disabled}" rendered="#{tooltip.rendered}" > event="#{tooltip.event}" onclick="#{event.onclick}" oncomplete="#{event.oncomplete}" ondblclick="#{event.ondblclick}" onhide="#{event.onhide}" onkeydown="#{event.onkeydown}" onkeypress="#{event.onkeypress}" onkeyup="#{event.onkeyup}" onmousedown="#{event.onmousedown}" onmousemove="#{event.onmousemove}" onmouseout="#{event.onmouseout}" onmouseover="#{event.onmouseover}" onmouseup="#{event.onmouseup}" onshow="#{event.onshow}"> > > Link > > Step 2. Add "show" JS API functionality: > > Step 3. Click on "show" ajax link. > Actual behavior: > toolTip doesn't appear. -- 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 From jira-events at lists.jboss.org Fri Jan 2 08:31:54 2009 From: jira-events at lists.jboss.org (Nick Belaevski (JIRA)) Date: Fri, 2 Jan 2009 08:31:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Updated: (RF-5499) drag'n'drop in tree: dropListener isn't called after tree node selection when ajaxSubmitSelection="true". In-Reply-To: <31477528.1230642955962.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <31725363.1230903114627.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Belaevski updated RF-5499: ------------------------------- Fix Version/s: 3.3.0 > drag'n'drop in tree: dropListener isn't called after tree node selection when ajaxSubmitSelection="true". > --------------------------------------------------------------------------------------------------------- > > Key: RF-5499 > URL: https://jira.jboss.org/jira/browse/RF-5499 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.3.0 > Environment: IE6, IE7, FF 3.1.3, Safari 3.1, Opera 9.62(3.3.0.CR1) > Reporter: Mikhail Vitenkov > Assignee: Nick Belaevski > Fix For: 3.3.0 > > > Precondition - use following code: > > > value="#{documentDirectoryTreeDAO.rootNode}" > id="tree" > treeNodeVar="treeNode" > reRender="documents" > switchType="client" > acceptedTypes="#{item.group.name}" > nodeSelectListener="#{documentDirectoryTreeDAO.listenerNodeSelected}" > ajaxSubmitSelection="true"> > dragType="#{item.group.name}" > dragIndicator="indicator2" > dropListener="#{documentDirectoryTreeDAO.listenerDropToTree}" > id="treeNode" > rendered="#{accountDAO.account.admin}" > reRender="documents, tree"> > > > > > > > > > > > > #1. Navigate to the page. > #2. Expand a node. > #3. Select sub node and drag it to parent node. > #4. Verify dropListener call. -- 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 From jira-events at lists.jboss.org Fri Jan 2 08:31:54 2009 From: jira-events at lists.jboss.org (Nick Belaevski (JIRA)) Date: Fri, 2 Jan 2009 08:31:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Assigned: (RF-5509) CSS Classes Not picked up (styleClass, viewClass, editClass, etc.) In-Reply-To: <20232090.1230759894326.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <29500808.1230903115005.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-5509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Belaevski reassigned RF-5509: ---------------------------------- Assignee: Anton Belevich > CSS Classes Not picked up (styleClass, viewClass, editClass, etc.) > ------------------------------------------------------------------ > > Key: RF-5509 > URL: https://jira.jboss.org/jira/browse/RF-5509 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.3.0 > Environment: Windows, JDK 1.6, Seam 2.1.0 w/upgraded Richfaces to 3.3.0.CR1, facelets > Reporter: Greg Zoller > Assignee: Anton Belevich > > If I specify code like below, none of my CSS styling of the inplaceSelect widget is picked up--only the default is visible. > styleClass="editable" viewClass="editable" editClass="editable" changedClass="editable" showValueInView="true"> > > > > The styling was working fine in 3.2.2 but broke in 3.3.0 betas onward. -- 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 From jira-events at lists.jboss.org Fri Jan 2 08:31:55 2009 From: jira-events at lists.jboss.org (Nick Belaevski (JIRA)) Date: Fri, 2 Jan 2009 08:31:55 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Assigned: (RF-5510) inplaceSelect visual display stuck in edit mode (doesn't re-draw itself) In-Reply-To: <12675980.1230760134347.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <10218011.1230903115358.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-5510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Belaevski reassigned RF-5510: ---------------------------------- Assignee: Anton Belevich > inplaceSelect visual display stuck in edit mode (doesn't re-draw itself) > ------------------------------------------------------------------------ > > Key: RF-5510 > URL: https://jira.jboss.org/jira/browse/RF-5510 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.3.0 > Environment: Windows, Seam 3.2.1 w/upgraded Richfaces 3.3.0.CR1, facelets, JDK 1.6 > Reporter: Greg Zoller > Assignee: Anton Belevich > > When using any rich:inplaceSelect widget the view state initially renders. I then click on the widget to drop the selection list down. Of course this triggers the edit mode and visualization. But after I select an option the drop-down list disappears but the value field does not re-draw itself in a view-mode rendering, but rather stays drawn in the edit mode rendering (yellow background w/little arrow on the right). > If I re-render the widget manually it seems to behave fine, but before I didn't have to do this. The widget took care of this itself. -- 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 From jira-events at lists.jboss.org Fri Jan 2 08:31:55 2009 From: jira-events at lists.jboss.org (Nick Belaevski (JIRA)) Date: Fri, 2 Jan 2009 08:31:55 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Assigned: (RF-5511) inplaceSelect with a4j:support not sending values to backing bean In-Reply-To: <7977000.1230762294320.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <8979540.1230903115607.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Belaevski reassigned RF-5511: ---------------------------------- Assignee: Anton Belevich > inplaceSelect with a4j:support not sending values to backing bean > ----------------------------------------------------------------- > > Key: RF-5511 > URL: https://jira.jboss.org/jira/browse/RF-5511 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.3.0 > Environment: Windows, JDK 1.6, Seam 2.1.0 w/Richfaces 3.3.0.CR1, Firefox 3, and IE7 > Reporter: Greg Zoller > Assignee: Anton Belevich > > See code below. This worked until this latest 3.3.0.CR1 release. > When a value is selected the setter (foo.setHey()) is not called. Although this worked with a4j:support event=onviewactivated before, I've also tried with onchange but the result is the same. > styleClass="editable" viewClass="editable" editClass="editable" changedClass="editable" > showValueInView="true"> > > > > NOTE: This might be related to https://jira.jboss.org/jira/browse/RF-5510 -- 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 From jira-events at lists.jboss.org Fri Jan 2 08:33:54 2009 From: jira-events at lists.jboss.org (Nick Belaevski (JIRA)) Date: Fri, 2 Jan 2009 08:33:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Updated: (RF-5508) Provide a facility to cache on the browser the data/records that were already loaded through AJAX in tabPanel/scrollableDataTable. Also a refresh machanism is desired. In-Reply-To: <7904885.1230758634250.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <13190843.1230903234234.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-5508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Belaevski updated RF-5508: ------------------------------- Fix Version/s: Wishes > Provide a facility to cache on the browser the data/records that were already loaded through AJAX in tabPanel/scrollableDataTable. Also a refresh machanism is desired. > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: RF-5508 > URL: https://jira.jboss.org/jira/browse/RF-5508 > Project: RichFaces > Issue Type: Feature Request > Affects Versions: 3.2.2 > Environment: Any JEE supporting Web/App Server and any standards compliant Browser > Reporter: Samba Siva Rao Kolusu > Fix For: Wishes > > > It would be highly desirable to have the data already loaded through AJAX be cached on the Browser rather than fetching it again every time the component accessed! > For example,in scrollableDataTable caching the data while we scroll down and showing the same when the user scrolls up reduces lot of requests to the server and database. Similarly, In case of tabPanel, loading the data through AJAX only when the tab is created,and then displaying the cached data on every subsequent tab focus reduces many server calls. Similarly the tree nodes can be cached if loaded through AJAX. In general,this feature can be applied to other components in situations where data is loaded through AJAX. Preferably, this caching feature should be made optional by providing an attribute at the component level. > Also a means to refresh the cached data in the browser should be put in the component itself in either or both of the following ways : > 1.the end user explicitly requesting "refresh cache" by clicking a link on the corresponding component or > 2.based on some input or on meeting certain criteria, the page developer should be able to clear the cache and load records freshly. > It should be noticed that loading the same number of records as were there before clearing the cache (if they are still available) would be better from usability perspective. > Caching the data on the client-side improves performance manifold for those sites where there won't be any changes in the existing data set. But if there would be new records being added or existing records being deleted in the database , then client-side caching may not be any option to choose. Or may be we must ponder over how we can detect if there is a difference between the client-side cache and the data in the database,and then refresh the cache when a change is found! -- 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 From jira-events at lists.jboss.org Fri Jan 2 08:45:54 2009 From: jira-events at lists.jboss.org (Nick Belaevski (JIRA)) Date: Fri, 2 Jan 2009 08:45:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Updated: (RF-5456) Non-Ajax requests badly handled if ViewExpiredExceptions are managed on client In-Reply-To: <22607511.1229963108814.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <29159760.1230903954593.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-5456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Belaevski updated RF-5456: ------------------------------- Fix Version/s: (was: Future) > Non-Ajax requests badly handled if ViewExpiredExceptions are managed on client > ------------------------------------------------------------------------------ > > Key: RF-5456 > URL: https://jira.jboss.org/jira/browse/RF-5456 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.2 > Environment: Tomcat 6 + Facelets + JSF 1.2_09 RI > Reporter: Pierre Wargnier > > If you activate org.ajax4jsf.handleViewExpiredOnClient in web.xml, the ViewExpiredExceptions are catched by the Ajax filter and a Ajax response will create a javascript "confim" window to ask the user to reload the page. > If the request that cause the ViewExpiredExceptions is not an AJAX one: only a blank page with the AJAX XML behind. > Proposed solution: Handle ViewExpired on client _only_ if request is AJAX. Throw the exception the normal way otherwise. > In org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(FilterChain, HttpServletRequest, HttpServletResponse) > instead of > log.error("Exception in the filter chain", e); > if(handleViewExpiredOnClient && isViewExpired(e)){ > do this: > if(handleViewExpiredOnClient && isViewExpired(e) && request.getParameterMap().containsKey("AJAXREQUEST")){ > log.info("View expired handling sent to client"); //View expired exceptions are quite commons, don't clog the logs tracing them -- 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 From jira-events at lists.jboss.org Sat Jan 3 01:36:55 2009 From: jira-events at lists.jboss.org (Lincoln Baxter III (JIRA)) Date: Sat, 3 Jan 2009 01:36:55 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Commented: (RF-3314) CommandLink action within dataTable is not executed in request scope In-Reply-To: <30032012.1209569239224.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <31844253.1230964615523.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444403#action_12444403 ] Lincoln Baxter III commented on RF-3314: ---------------------------------------- This also occurs using h:dataTable on Mojarra 1.2_10, using facelets 1.1.14. This same issue also occurs in facelets using the ui:repeat. > CommandLink action within dataTable is not executed in request scope > -------------------------------------------------------------------- > > Key: RF-3314 > URL: https://jira.jboss.org/jira/browse/RF-3314 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.0 > Environment: myfaces 1.2.2 > Reporter: Robert Stone > Assignee: Nick Belaevski > Fix For: Future > > Attachments: rf3314.zip > > > When clicking on links within datatable action/actionListener/actionparam is not executed when bean is placed in request scope. Code works with backing bean in the session scope. > value="${modalForm.searchResults}"> > > id="selectSearchValue" reRender="modalMasterValue"> > assignTo="#{modalMaster.searchFor}" /> > > event="onclick" /> > > > Backing beans Spring configuration (works if the second bean is moved to the session scope): > > > > -- 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 From jira-events at lists.jboss.org Sat Jan 3 01:50:54 2009 From: jira-events at lists.jboss.org (Lincoln Baxter III (JIRA)) Date: Sat, 3 Jan 2009 01:50:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Commented: (RF-3314) CommandLink action within dataTable is not executed in request scope In-Reply-To: <30032012.1209569239224.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <18937935.1230965454578.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444404#action_12444404 ] Lincoln Baxter III commented on RF-3314: ---------------------------------------- I'm not sure if I can use keepAlive, because the bean which would require serialization contains objects which cannot be serialized. (Namely spring-hibernate services.) Is there a way around this? > CommandLink action within dataTable is not executed in request scope > -------------------------------------------------------------------- > > Key: RF-3314 > URL: https://jira.jboss.org/jira/browse/RF-3314 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.0 > Environment: myfaces 1.2.2 > Reporter: Robert Stone > Assignee: Nick Belaevski > Fix For: Future > > Attachments: rf3314.zip > > > When clicking on links within datatable action/actionListener/actionparam is not executed when bean is placed in request scope. Code works with backing bean in the session scope. > value="${modalForm.searchResults}"> > > id="selectSearchValue" reRender="modalMasterValue"> > assignTo="#{modalMaster.searchFor}" /> > > event="onclick" /> > > > Backing beans Spring configuration (works if the second bean is moved to the session scope): > > > > -- 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 From jira-events at lists.jboss.org Sun Jan 4 05:10:54 2009 From: jira-events at lists.jboss.org (Rong Tao (JIRA)) Date: Sun, 4 Jan 2009 05:10:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Created: (RF-5512) Scrollable DataTable cannot be used when adding @charset statement to css files. Message-ID: <11365731.1231063854503.JavaMail.jira@cloud.prod.atl2.jboss.com> Scrollable DataTable cannot be used when adding @charset statement to css files. -------------------------------------------------------------------------------- Key: RF-5512 URL: https://jira.jboss.org/jira/browse/RF-5512 Project: RichFaces Issue Type: Bug Components: portal Affects Versions: 3.2.2 Environment: windows xp + glassfish v2u2 + jdk 1.6 Reporter: Rong Tao This is a very strange bug, when I add a statement '@charset "utf-8"' to a css file or the css section of the xhtml file, the Scrollable DataTable becomes very strange and cannot be used, the problems are: 1. the table header is not displayed. 2. scroll bar is not displayed. 3. cannot select any rows. 4. the 1st and 2nd columns are overlap. Very easy to reproduce: download and deploy the demo scrollableDataTable.xhtml and DataTableScrollerBean.java; then add '@charset "utf-8"' to scrollableDataTable.xhtml, the Refresh the page and you will see the problems. Not only "utf-8", other charset such as "iso-8859-1" can also cause the issue. -- 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 From jira-events at lists.jboss.org Sun Jan 4 09:05:06 2009 From: jira-events at lists.jboss.org (Nick Belaevski (JIRA)) Date: Sun, 4 Jan 2009 09:05:06 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Commented: (RF-3314) CommandLink action within dataTable is not executed in request scope In-Reply-To: <30032012.1209569239224.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <20799051.1231077906073.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444425#action_12444425 ] Nick Belaevski commented on RF-3314: ------------------------------------ Use session-scoped or conversation-scoped (Seam) beans > CommandLink action within dataTable is not executed in request scope > -------------------------------------------------------------------- > > Key: RF-3314 > URL: https://jira.jboss.org/jira/browse/RF-3314 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.0 > Environment: myfaces 1.2.2 > Reporter: Robert Stone > Assignee: Nick Belaevski > Fix For: Future > > Attachments: rf3314.zip > > > When clicking on links within datatable action/actionListener/actionparam is not executed when bean is placed in request scope. Code works with backing bean in the session scope. > value="${modalForm.searchResults}"> > > id="selectSearchValue" reRender="modalMasterValue"> > assignTo="#{modalMaster.searchFor}" /> > > event="onclick" /> > > > Backing beans Spring configuration (works if the second bean is moved to the session scope): > > > > -- 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 From jira-events at lists.jboss.org Sun Jan 4 09:08:54 2009 From: jira-events at lists.jboss.org (Nick Belaevski (JIRA)) Date: Sun, 4 Jan 2009 09:08:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Created: (RF-5513) Regression-area setup application on Hudson Message-ID: <19885218.1231078134410.JavaMail.jira@cloud.prod.atl2.jboss.com> Regression-area setup application on Hudson ------------------------------------------- Key: RF-5513 URL: https://jira.jboss.org/jira/browse/RF-5513 Project: RichFaces Issue Type: Task Affects Versions: 3.3.0 Reporter: Nick Belaevski Assignee: Nick Belaevski Priority: Critical Fix For: 3.3.0 -- 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 From jira-events at lists.jboss.org Sun Jan 4 09:08:54 2009 From: jira-events at lists.jboss.org (Nick Belaevski (JIRA)) Date: Sun, 4 Jan 2009 09:08:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Created: (RF-5514) Refactor application Message-ID: <17315427.1231078134640.JavaMail.jira@cloud.prod.atl2.jboss.com> Refactor application -------------------- Key: RF-5514 URL: https://jira.jboss.org/jira/browse/RF-5514 Project: RichFaces Issue Type: Sub-task Affects Versions: 3.3.0 Reporter: Nick Belaevski Assignee: Nick Belaevski Fix For: 3.3.0 -- 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 From jira-events at lists.jboss.org Sun Jan 4 09:10:54 2009 From: jira-events at lists.jboss.org (Nick Belaevski (JIRA)) Date: Sun, 4 Jan 2009 09:10:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Created: (RF-5515) Setup cargo plugin for execution on Hudson Message-ID: <7222958.1231078254349.JavaMail.jira@cloud.prod.atl2.jboss.com> Setup cargo plugin for execution on Hudson ------------------------------------------ Key: RF-5515 URL: https://jira.jboss.org/jira/browse/RF-5515 Project: RichFaces Issue Type: Sub-task Affects Versions: 3.3.0 Reporter: Nick Belaevski Assignee: Nick Belaevski Fix For: 3.3.0 -- 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 From jira-events at lists.jboss.org Sun Jan 4 09:16:55 2009 From: jira-events at lists.jboss.org (Nick Belaevski (JIRA)) Date: Sun, 4 Jan 2009 09:16:55 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Updated: (RF-4813) actionparam not working in rich:dataTable In-Reply-To: <10397588.1225661960764.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <1938856.1231078615046.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Belaevski updated RF-4813: ------------------------------- Original Estimate: (was: 4 hours) Remaining Estimate: (was: 4 hours) Component/s: (was: planning_all) Due Date: (was: 12/Dec/08) Assignee: Denis Morozov (was: Nick Belaevski) > actionparam not working in rich:dataTable > ----------------------------------------- > > Key: RF-4813 > URL: https://jira.jboss.org/jira/browse/RF-4813 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.2 > Reporter: Nick Belaevski > Assignee: Denis Morozov > Fix For: 3.3.0 > > -- 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 From jira-events at lists.jboss.org Sun Jan 4 09:30:56 2009 From: jira-events at lists.jboss.org (Nick Belaevski (JIRA)) Date: Sun, 4 Jan 2009 09:30:56 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Work started: (RF-4226) Tree:oncontextmenu attribute is missing In-Reply-To: <5182715.1219099686506.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <14131568.1231079456726.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on RF-4226 started by Nick Belaevski. > Tree:oncontextmenu attribute is missing > --------------------------------------- > > Key: RF-4226 > URL: https://jira.jboss.org/jira/browse/RF-4226 > Project: RichFaces > Issue Type: Bug > Components: planning_all > Affects Versions: 3.2.2 > Reporter: Nick Belaevski > Assignee: Nick Belaevski > Fix For: 3.3.0 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > -- 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 From jira-events at lists.jboss.org Sun Jan 4 09:49:54 2009 From: jira-events at lists.jboss.org (Nick Belaevski (JIRA)) Date: Sun, 4 Jan 2009 09:49:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Resolved: (RF-4226) Tree:oncontextmenu attribute is missing In-Reply-To: <5182715.1219099686506.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <19743544.1231080594827.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Belaevski resolved RF-4226. -------------------------------- Resolution: Done Assignee: Tsikhon Kuprevich (was: Nick Belaevski) > Tree:oncontextmenu attribute is missing > --------------------------------------- > > Key: RF-4226 > URL: https://jira.jboss.org/jira/browse/RF-4226 > Project: RichFaces > Issue Type: Bug > Components: planning_all > Affects Versions: 3.2.2 > Reporter: Nick Belaevski > Assignee: Tsikhon Kuprevich > Fix For: 3.3.0 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > -- 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 From jira-events at lists.jboss.org Sun Jan 4 09:51:54 2009 From: jira-events at lists.jboss.org (Nick Belaevski (JIRA)) Date: Sun, 4 Jan 2009 09:51:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Commented: (RF-5477) Refactor test suite to obtain correct tests report In-Reply-To: <31164130.1230507895073.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <178595.1231080714572.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444428#action_12444428 ] Nick Belaevski commented on RF-5477: ------------------------------------ Moved to next iteration due to Hudson server inaccessible > Refactor test suite to obtain correct tests report > -------------------------------------------------- > > Key: RF-5477 > URL: https://jira.jboss.org/jira/browse/RF-5477 > Project: RichFaces > Issue Type: Sub-task > Components: planning_all > Affects Versions: 3.3.0 > Reporter: Nick Belaevski > Assignee: Nick Belaevski > Fix For: 3.3.0 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- 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 From jira-events at lists.jboss.org Sun Jan 4 09:51:54 2009 From: jira-events at lists.jboss.org (Nick Belaevski (JIRA)) Date: Sun, 4 Jan 2009 09:51:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Commented: (RF-5476) Check Firefox version In-Reply-To: <19972685.1230507894882.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <28050291.1231080714718.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444429#action_12444429 ] Nick Belaevski commented on RF-5476: ------------------------------------ Moved to next iteration due to Hudson server inaccessible > Check Firefox version > --------------------- > > Key: RF-5476 > URL: https://jira.jboss.org/jira/browse/RF-5476 > Project: RichFaces > Issue Type: Sub-task > Components: planning_all > Affects Versions: 3.3.0 > Reporter: Nick Belaevski > Assignee: Nick Belaevski > Fix For: 3.3.0 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > -- 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 From jira-events at lists.jboss.org Sun Jan 4 09:51:54 2009 From: jira-events at lists.jboss.org (Nick Belaevski (JIRA)) Date: Sun, 4 Jan 2009 09:51:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Updated: (RF-5477) Refactor test suite to obtain correct tests report In-Reply-To: <31164130.1230507895073.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <15606934.1231080714873.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Belaevski updated RF-5477: ------------------------------- Due Date: 11/Jan/09 (was: 04/Jan/09) > Refactor test suite to obtain correct tests report > -------------------------------------------------- > > Key: RF-5477 > URL: https://jira.jboss.org/jira/browse/RF-5477 > Project: RichFaces > Issue Type: Sub-task > Components: planning_all > Affects Versions: 3.3.0 > Reporter: Nick Belaevski > Assignee: Nick Belaevski > Fix For: 3.3.0 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- 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 From jira-events at lists.jboss.org Sun Jan 4 09:51:54 2009 From: jira-events at lists.jboss.org (Nick Belaevski (JIRA)) Date: Sun, 4 Jan 2009 09:51:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Updated: (RF-5476) Check Firefox version In-Reply-To: <19972685.1230507894882.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <23879645.1231080715056.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Belaevski updated RF-5476: ------------------------------- Due Date: 11/Jan/09 (was: 04/Jan/09) > Check Firefox version > --------------------- > > Key: RF-5476 > URL: https://jira.jboss.org/jira/browse/RF-5476 > Project: RichFaces > Issue Type: Sub-task > Components: planning_all > Affects Versions: 3.3.0 > Reporter: Nick Belaevski > Assignee: Nick Belaevski > Fix For: 3.3.0 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > -- 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 From jira-events at lists.jboss.org Sun Jan 4 17:13:54 2009 From: jira-events at lists.jboss.org (Pjotr Andreev (JIRA)) Date: Sun, 4 Jan 2009 17:13:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Created: (RF-5516) Add the onContextMenu event to the ExtendedDataTable and ScrollableDataTable Message-ID: <27939183.1231107234343.JavaMail.jira@cloud.prod.atl2.jboss.com> Add the onContextMenu event to the ExtendedDataTable and ScrollableDataTable ---------------------------------------------------------------------------- Key: RF-5516 URL: https://jira.jboss.org/jira/browse/RF-5516 Project: RichFaces Issue Type: Feature Request Components: planning_all Affects Versions: Wishes Environment: Any Reporter: Pjotr Andreev It would be nice to add the onContextMenu event to the ExtendedDataTable and ScrollableDataTable either. -- 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 From jira-events at lists.jboss.org Sun Jan 4 17:17:54 2009 From: jira-events at lists.jboss.org (Pjotr Andreev (JIRA)) Date: Sun, 4 Jan 2009 17:17:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Updated: (RF-5516) Add the onContextMenu event to the ExtendedDataTable and ScrollableDataTable In-Reply-To: <27939183.1231107234343.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <2179538.1231107474347.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pjotr Andreev updated RF-5516: ------------------------------ Attachment: ui_onRowContextMenu_ExtDT_ScrollDT.zip The implementation for onRowContextMenu support. JAR-ed file contains sources and configurations, placed relative to the SVN-root path. SVN-version as of 04 Jan 2009. > Add the onContextMenu event to the ExtendedDataTable and ScrollableDataTable > ---------------------------------------------------------------------------- > > Key: RF-5516 > URL: https://jira.jboss.org/jira/browse/RF-5516 > Project: RichFaces > Issue Type: Feature Request > Components: planning_all > Affects Versions: Wishes > Environment: Any > Reporter: Pjotr Andreev > Attachments: ui_onRowContextMenu_ExtDT_ScrollDT.zip > > > It would be nice to add the onContextMenu event to the ExtendedDataTable and ScrollableDataTable either. -- 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 From jira-events at lists.jboss.org Sun Jan 4 17:23:54 2009 From: jira-events at lists.jboss.org (Pjotr Andreev (JIRA)) Date: Sun, 4 Jan 2009 17:23:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Updated: (RF-5516) Add the onRowContextMenu event to the ExtendedDataTable and ScrollableDataTable In-Reply-To: <27939183.1231107234343.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <4863623.1231107834288.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pjotr Andreev updated RF-5516: ------------------------------ Summary: Add the onRowContextMenu event to the ExtendedDataTable and ScrollableDataTable (was: Add the onContextMenu event to the ExtendedDataTable and ScrollableDataTable) Description: It would be nice to add the onRowContextMenu event to the ExtendedDataTable and ScrollableDataTable either. (was: It would be nice to add the onContextMenu event to the ExtendedDataTable and ScrollableDataTable either.) > Add the onRowContextMenu event to the ExtendedDataTable and ScrollableDataTable > ------------------------------------------------------------------------------- > > Key: RF-5516 > URL: https://jira.jboss.org/jira/browse/RF-5516 > Project: RichFaces > Issue Type: Feature Request > Components: planning_all > Affects Versions: Wishes > Environment: Any > Reporter: Pjotr Andreev > Attachments: ui_onRowContextMenu_ExtDT_ScrollDT.zip > > > It would be nice to add the onRowContextMenu event to the ExtendedDataTable and ScrollableDataTable either. -- 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 From jira-events at lists.jboss.org Mon Jan 5 04:03:54 2009 From: jira-events at lists.jboss.org (Ilya Shaikovsky (JIRA)) Date: Mon, 5 Jan 2009 04:03:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Resolved: (RF-5504) Queue demo: remove delay in action In-Reply-To: <28985531.1230676255241.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <20190454.1231146234306.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shaikovsky resolved RF-5504. --------------------------------- Resolution: Done > Queue demo: remove delay in action > ---------------------------------- > > Key: RF-5504 > URL: https://jira.jboss.org/jira/browse/RF-5504 > Project: RichFaces > Issue Type: Task > Affects Versions: 3.3.0 > Reporter: Nick Belaevski > Assignee: Ilya Shaikovsky > Fix For: 3.3.0 > > > http://livedemo.exadel.com/richfaces-demo-3.3.0.CR1/richfaces/queue.jsf?tab=queueSettings - Thread.sleep in action should be removed from this demo -- 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 From jira-events at lists.jboss.org Mon Jan 5 04:24:54 2009 From: jira-events at lists.jboss.org (Ilya Shaikovsky (JIRA)) Date: Mon, 5 Jan 2009 04:24:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Resolved: (RF-5505) queue: In "Queue Settings" example requestDelay doesn't affect to time of request delay, plus exception take place java.lang.IllegalArgumentException: argument type mismatch In-Reply-To: <19333826.1230714354522.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <32401899.1231147494381.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shaikovsky resolved RF-5505. --------------------------------- Resolution: Done was already there in nightly. So broken repeat after incorrect input - was not reproducible for me. Do you really waited 5000 mls? :) I've added just message component in order to show error and made the input disabled if there are incorrect input. Also exception doesn't thrown anymore. > queue: In "Queue Settings" example requestDelay doesn't affect to time of request delay, plus exception take place java.lang.IllegalArgumentException: argument type mismatch > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-5505 > URL: https://jira.jboss.org/jira/browse/RF-5505 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.3.0 > Environment: IE6, IE7, FF 3.1.3, Safari 3.1, Opera 9.62(3.3.0.CR1) > Reporter: Mikhail Vitenkov > Assignee: Ilya Shaikovsky > Priority: Minor > Fix For: 3.3.0 > > > #1. Navigate to Ajax Support -> Queue -> Queue Settings richfaces-demo example. > #2. Enter 5,000 in "requestDelay" input. > #3. Click "Apply" button. > #4. Enter "something" in "Type here:" input and verify real delay. > Actual behavior: > requestDelay isn't applied, plus exception take place: > SEVERE: /richfaces/queue/examples/repeater.xhtml @37,53 value="#{queueBean.requestDelay}": java.lang.IllegalArgumentException: argument type mismatch > java.lang.IllegalArgumentException: argument type mismatch > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at javax.el.BeanELResolver.setValue(BeanELResolver.java:108) > at javax.el.CompositeELResolver.setValue(CompositeELResolver.java:68) > at com.sun.faces.el.FacesCompositeELResolver.setValue(FacesCompositeELResolver.java:100) > at org.apache.el.parser.AstValue.setValue(AstValue.java:114) > at org.apache.el.ValueExpressionImpl.setValue(ValueExpressionImpl.java:249) > at com.sun.facelets.el.TagValueExpression.setValue(TagValueExpression.java:93) > at javax.faces.component.UIInput.updateModel(UIInput.java:771) > at javax.faces.component.UIInput.processUpdates(UIInput.java:703) > at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:1081) > at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:1081) > at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:1081) > at javax.faces.component.UIForm.processUpdates(UIForm.java:261) > at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:1081) > at org.richfaces.component.UISwitchablePanel.processUpdates(UISwitchablePanel.java:208) > at org.ajax4jsf.component.AjaxViewRoot$2.invokeContextCallback(AjaxViewRoot.java:416) > at org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:238) > at org.ajax4jsf.component.AjaxViewRoot.processUpdates(AjaxViewRoot.java:432) > at com.sun.faces.lifecycle.UpdateModelValuesPhase.execute(UpdateModelValuesPhase.java:78) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100) > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178) > at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) > at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390) > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > at java.lang.Thread.run(Unknown Source) -- 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 From jira-events at lists.jboss.org Mon Jan 5 05:00:54 2009 From: jira-events at lists.jboss.org (Andrei Markavtsov (JIRA)) Date: Mon, 5 Jan 2009 05:00:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Created: (RF-5517) Rich:columns cannot be used without facelet Message-ID: <10475490.1231149654580.JavaMail.jira@cloud.prod.atl2.jboss.com> Rich:columns cannot be used without facelet ------------------------------------------- Key: RF-5517 URL: https://jira.jboss.org/jira/browse/RF-5517 Project: RichFaces Issue Type: Bug Components: planning_all Reporter: Andrei Markavtsov Assignee: Andrei Markavtsov Fix For: 3.3.0 -- 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 From jira-events at lists.jboss.org Mon Jan 5 05:03:04 2009 From: jira-events at lists.jboss.org (Andrei Markavtsov (JIRA)) Date: Mon, 5 Jan 2009 05:03:04 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Work started: (RF-5517) Rich:columns cannot be used without facelet In-Reply-To: <10475490.1231149654580.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <11144608.1231149784486.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on RF-5517 started by Andrei Markavtsov. > Rich:columns cannot be used without facelet > ------------------------------------------- > > Key: RF-5517 > URL: https://jira.jboss.org/jira/browse/RF-5517 > Project: RichFaces > Issue Type: Bug > Components: planning_all > Reporter: Andrei Markavtsov > Assignee: Andrei Markavtsov > Fix For: 3.3.0 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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 From jira-events at lists.jboss.org Mon Jan 5 05:06:54 2009 From: jira-events at lists.jboss.org (Alexander Dubovsky (JIRA)) Date: Mon, 5 Jan 2009 05:06:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Created: (RF-5518) ModalPanel: incorrect view under Opera. Message-ID: <20171895.1231150014582.JavaMail.jira@cloud.prod.atl2.jboss.com> ModalPanel: incorrect view under Opera. --------------------------------------- Key: RF-5518 URL: https://jira.jboss.org/jira/browse/RF-5518 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Environment: 3.3.0.CR1, Opera 9.62 Reporter: Alexander Dubovsky Assignee: Nick Belaevski Attachments: 34.png Open modalPanel page in richfaces-demo and show panel. Result: see screen shot. -- 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 From jira-events at lists.jboss.org Mon Jan 5 05:06:54 2009 From: jira-events at lists.jboss.org (Alexander Dubovsky (JIRA)) Date: Mon, 5 Jan 2009 05:06:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Updated: (RF-5518) ModalPanel: incorrect view under Opera. In-Reply-To: <20171895.1231150014582.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <4067517.1231150014995.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Dubovsky updated RF-5518: ----------------------------------- Attachment: 34.png > ModalPanel: incorrect view under Opera. > --------------------------------------- > > Key: RF-5518 > URL: https://jira.jboss.org/jira/browse/RF-5518 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.3.0 > Environment: 3.3.0.CR1, Opera 9.62 > Reporter: Alexander Dubovsky > Assignee: Nick Belaevski > Attachments: 34.png > > > Open modalPanel page in richfaces-demo and show panel. > Result: see screen shot. -- 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 From jira-events at lists.jboss.org Mon Jan 5 05:19:54 2009 From: jira-events at lists.jboss.org (Andrei Markavtsov (JIRA)) Date: Mon, 5 Jan 2009 05:19:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Resolved: (RF-5517) Rich:columns cannot be used without facelet In-Reply-To: <10475490.1231149654580.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <18494219.1231150794524.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrei Markavtsov resolved RF-5517. ----------------------------------- Resolution: Done Assignee: Alexander Dubovsky (was: Andrei Markavtsov) > Rich:columns cannot be used without facelet > ------------------------------------------- > > Key: RF-5517 > URL: https://jira.jboss.org/jira/browse/RF-5517 > Project: RichFaces > Issue Type: Bug > Components: planning_all > Reporter: Andrei Markavtsov > Assignee: Alexander Dubovsky > Fix For: 3.3.0 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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 From jira-events at lists.jboss.org Mon Jan 5 05:38:54 2009 From: jira-events at lists.jboss.org (Alexander Dubovsky (JIRA)) Date: Mon, 5 Jan 2009 05:38:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Created: (RF-5519) Calendar problem under IE6-7 if dir="rtl" for body tag. Message-ID: <24713303.1231151934381.JavaMail.jira@cloud.prod.atl2.jboss.com> Calendar problem under IE6-7 if dir="rtl" for body tag. ------------------------------------------------------- Key: RF-5519 URL: https://jira.jboss.org/jira/browse/RF-5519 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Environment: 3.3.0.CR1, IE6-7 Reporter: Alexander Dubovsky Assignee: Nick Belaevski Source: # Open page under IE 6 or 7. # Try to show calendar pop up. Result: it is not shown. # Repeate the same stepd after define direction="bottom-left" for calendar Result: pop up appears, but in incorrect place. -- 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 From jira-events at lists.jboss.org Mon Jan 5 06:07:54 2009 From: jira-events at lists.jboss.org (Andrei Markavtsov (JIRA)) Date: Mon, 5 Jan 2009 06:07:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Resolved: (RF-5300) columns: begin attribute ignore last columns, instead of earliest under facelets & seamApp application(jsf1.2_10) In-Reply-To: <18538598.1228911526755.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <22095455.1231153674373.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrei Markavtsov resolved RF-5300. ----------------------------------- Resolution: Done Assignee: Tsikhon Kuprevich (was: Andrei Markavtsov) > columns: begin attribute ignore last columns, instead of earliest under facelets & seamApp application(jsf1.2_10) > ----------------------------------------------------------------------------------------------------------------- > > Key: RF-5300 > URL: https://jira.jboss.org/jira/browse/RF-5300 > Project: RichFaces > Issue Type: Bug > Components: planning_all > Affects Versions: 3.3.0 > Environment: IE6, IE7, FF 3.1.3, Safari 3.1, Opera 9.62(3.3.0.BETA3) > Reporter: Mikhail Vitenkov > Assignee: Tsikhon Kuprevich > Fix For: 3.3.0 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > #1. Add rich:columns inside rich:dataTable following way: > > ... columns="#{columns.columns}" index="index" rowspan="#{columns.rowspan}" begin="#{columns.begin}" end="#{columns.end}" width="#{columns.width}" style="#{style.style}" styleClass="#{style.styleClass}" > sortOrder="#{columns.orderings[index]}" sortBy="#{d1.str0}" > filterBy="#{d1.str0}" selfSorted="true" sortable="true" > filterValue="#{columns.filterValue[index]}" filterMethod="#{columns.filterMethod}"> > > > > > Link > > > > > ... > #2. Define data for columns and fill it: > private ArrayList data2; > for (int i = 0; i < length1; i++) { > data2.add("data[" + i + "]"); > } > getter & setter. > #3. Set begin attribute to '2'; > #4. Navigate to page & verify columns' data. > Actual behavior: > The last colunm is ignored. > Expected behavior: > The first colunm is ignored. -- 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 From jira-events at lists.jboss.org Mon Jan 5 06:17:54 2009 From: jira-events at lists.jboss.org (Denis Morozov (JIRA)) Date: Mon, 5 Jan 2009 06:17:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Resolved: (RF-4813) actionparam not working in rich:dataTable In-Reply-To: <10397588.1225661960764.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <32135852.1231154274390.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Morozov resolved RF-4813. ------------------------------- Resolution: Won't Fix Assignee: Alexander Dubovsky (was: Denis Morozov) richfaces guide says: "The extends , so the "name" attribute is mandatory " > actionparam not working in rich:dataTable > ----------------------------------------- > > Key: RF-4813 > URL: https://jira.jboss.org/jira/browse/RF-4813 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.2 > Reporter: Nick Belaevski > Assignee: Alexander Dubovsky > Fix For: 3.3.0 > > -- 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 From jira-events at lists.jboss.org Mon Jan 5 06:53:54 2009 From: jira-events at lists.jboss.org (Alexander Dubovsky (JIRA)) Date: Mon, 5 Jan 2009 06:53:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Closed: (RF-4813) actionparam not working in rich:dataTable In-Reply-To: <10397588.1225661960764.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <15163409.1231156434674.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Dubovsky closed RF-4813. ---------------------------------- > actionparam not working in rich:dataTable > ----------------------------------------- > > Key: RF-4813 > URL: https://jira.jboss.org/jira/browse/RF-4813 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.2 > Reporter: Nick Belaevski > Assignee: Alexander Dubovsky > Fix For: 3.3.0 > > -- 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 From jira-events at lists.jboss.org Mon Jan 5 07:07:54 2009 From: jira-events at lists.jboss.org (Alexander Dubovsky (JIRA)) Date: Mon, 5 Jan 2009 07:07:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Closed: (RF-4518) Bug introduces on suggestionbox when upgrading from 3.2.1 to 3.2.2 In-Reply-To: <32470516.1222097781389.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <21610693.1231157274632.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Dubovsky closed RF-4518. ---------------------------------- Assignee: Alexander Dubovsky (was: Tsikhon Kuprevich) > Bug introduces on suggestionbox when upgrading from 3.2.1 to 3.2.2 > ------------------------------------------------------------------ > > Key: RF-4518 > URL: https://jira.jboss.org/jira/browse/RF-4518 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.2 > Environment: JBoss 4.2.2 , Seam 2.0.2.SP1 > Reporter: Shervin Asgari > Assignee: Alexander Dubovsky > Attachments: correct_WithRichFaces_3_2_1.jpg, operaBug.png, pageSource.html, protected.zip, screenshot-1.jpg, screenshot-2.jpg, template_4level1.xhtml > > > I have just upgraded to 3.2.2.GA from 3.2.1.GA and suddenly something is terribly wrong with my suggestionbox. > It looks like it is a styling issue of some sort. > Because combined it is correct. > The suggestionbox lists all the elements withouth any styling, but however the styling appears on top left corner of the screen. > And I cannot select. > The code worked on 3.2.1 > Please see the forum link for more description on the code. > There are other suggestionboxes we use in the same project and there it works correctly. -- 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 From jira-events at lists.jboss.org Mon Jan 5 07:19:56 2009 From: jira-events at lists.jboss.org (Alexander Dubovsky (JIRA)) Date: Mon, 5 Jan 2009 07:19:56 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Closed: (RF-4329) rich:calendar in modalPanel is cutoff In-Reply-To: <7666000.1219953878702.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <32464230.1231157996300.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-4329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Dubovsky closed RF-4329. ---------------------------------- Assignee: Alexander Dubovsky (was: Tsikhon Kuprevich) > rich:calendar in modalPanel is cutoff > ------------------------------------- > > Key: RF-4329 > URL: https://jira.jboss.org/jira/browse/RF-4329 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.2 > Environment: IE7/Firefox3 > Reporter: Michael Edwards > Assignee: Alexander Dubovsky > > A rich:calendar in popup mode near the bottom of a modal will have the parts that extend past the modalPanel cut off. Let me know if you need a test case... -- 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 From jira-events at lists.jboss.org Mon Jan 5 07:27:54 2009 From: jira-events at lists.jboss.org (Alexander Dubovsky (JIRA)) Date: Mon, 5 Jan 2009 07:27:54 -0500 (EST) Subject: [richfaces-issues] [JBoss JIRA] Closed: (RF-4982) rich:calendar component styleClass is applied on the table and not the actual input component In-Reply-To: <18892713.1227093276660.JavaMail.jira@cloud.prod.atl2.jboss.com> Message-ID: <9588627.1231158474316.JavaMail.jira@cloud.prod.atl2.jboss.com> [ https://jira.jboss.org/jira/browse/RF-4982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Dubovsky closed RF-4982. ---------------------------------- Assignee: Alexander Dubovsky (was: Tsikhon Kuprevich) > rich:calendar component styleClass is applied on the table and not the actual input component > --------------------------------------------------------------------------------------------- > > Key: RF-4982 > URL: https://jira.jboss.org/jira/browse/RF-4982 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.0.0, 3.0.1, 3.0.2, 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 3.1.5, 3.1.6, 3.2.0, 3.2.0.SR1, 3.2.1, 3.2.2 > Environment: Win XP, Linux Ubuntu 8.10, Jboss 4.2.2, JDK1.5 / JDK1.6 JSF1.2 RI (mojarra) > Reporter: Mike > Assignee: Alexander Dubovsky > > In case of a validation error we add a styleClass property (e.g. css-class 'failureMarker') on the relevant element (input, select etc.) > Unfortunately the rich:calendar component added this property on the table of the calendar-popup, not at the input field as expected, see example: > Section of the rendered html of a calendar component: > Actual > ... > > ... > > >