March 2014 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13406) Create a new showcase for RichFaces 5

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13406?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13406: ------------------------------- Sprint: (was: 5.0.0.Alpha4 - Sprint 1) > Create a new showcase for RichFaces 5 > ------------------------------------- > > Key: RF-13406 > URL: https://issues.jboss.org/browse/RF-13406 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: showcase > Reporter: Brian Leathem > Fix For: 5.0.0.Alpha4 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > The new showcase should: > # Include the examples from the existing RichFaces4 showcase > #* Simplications should be made as appropriate to reduce complexity (eg. no JMS, no JPA - these can be addressed in standalone examples) > # Be based on the RichFaces Sandbox Bootstrap demo > #* The layout will have to be changed to use generic bootstrap CSS as required > # Drop (as much as possible) the container specific configuration found in the RichFaces4 showcase > #* consider any sample simplifications required to achieve this goal -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13272) Manage the RichFaces jquery.js dependency with RichWidgets

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13272?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13272: ------------------------------- Sprint: (was: 5.0.0.Alpha4 - Sprint 1) > Manage the RichFaces jquery.js dependency with RichWidgets > ---------------------------------------------------------- > > Key: RF-13272 > URL: https://issues.jboss.org/browse/RF-13272 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha4 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The jQuery UI dependencies are currently set within RichWidgets and copied into RichFaces via a grunt task. > The jQuery.js dpendency should be similarly managed. While making this change, the jQuery.js library should be changed to _com.jquery_. -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13334) Upgrade jQuery UI to 1.10.3

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13334?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13334: ------------------------------- Fix Version/s: 4.5-Tracking (was: 5.0.0.Alpha4) > Upgrade jQuery UI to 1.10.3 > --------------------------- > > Key: RF-13334 > URL: https://issues.jboss.org/browse/RF-13334 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > Fix For: 4.5-Tracking > > > RichWidgets issue: > https://github.com/richwidgets/richwidgets/issues/99 -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13514) Support file upload progress tracking in Servlets >= 3.0 environment

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13514?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13514: ------------------------------- Fix Version/s: 4.5.0.Alpha3 (was: 5.0.0.Alpha4) > Support file upload progress tracking in Servlets >= 3.0 environment > -------------------------------------------------------------------- > > Key: RF-13514 > URL: https://issues.jboss.org/browse/RF-13514 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-input, core > Affects Versions: 5.0.0.Alpha3 > Reporter: Lukáš Fryč > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > > We currently support two approaches for file upload: > * Servlets 2.5: own request form data parser [{{MultipartRequestParser}}|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/request/MultipartRequestParser.java] > * Servlets 3.0: leveraging {{HttpServletRequest#getParts()}} > However as we have discussed RF-13444, we had to finally do a trade-off of limiting support of file progress tracking. I.e. in Servlets 3.0 we have no simple way how to track file upload progress since getParts() returns data for completed request. > There are several possible outcomes: > 1) drop server-side file upload progress tracking and leverage XHR2/HTML5 that has built-in ability to track progress > * imho we are already prepared to switch to XHR2 and client-side progress (possibly leveraging some third-party widget) since [all major browsers support it at least one version back|http://caniuse.com/#feat=xhr2] > * existing implementation: http://www.script-tutorials.com/pure-html5-file-upload/ > 2) use a {{ServletFilter}} to wrap a request as our {{FileUploadFacesContextFactory}} currently do and so have an earlier access to the request object > * this principle has a drawback - we have to ensure our filter has high-enough priority so the servlet container won't touch the request body yet -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-11453) Add autocomplete functionality to the rich:select component

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-11453?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11453: ------------------------------- Fix Version/s: 4.5-Tracking (was: 5.0.0.Alpha4) > Add autocomplete functionality to the rich:select component > ----------------------------------------------------------- > > Key: RF-11453 > URL: https://issues.jboss.org/browse/RF-11453 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Reporter: Cody Lerum > Assignee: Lukáš Fryč > Fix For: 4.5-Tracking > > > Add an "autocompleteMethod" to rich:select -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13579) Upgrade CDK 4.3 to JBoss Java EE BOM 3.0.2

by Pavol Pitonak (JIRA)

Pavol Pitonak created RF-13579: ---------------------------------- Summary: Upgrade CDK 4.3 to JBoss Java EE BOM 3.0.2 Key: RF-13579 URL: https://issues.jboss.org/browse/RF-13579 Project: RichFaces Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: cdk Affects Versions: 4.3.1 Reporter: Pavol Pitonak org.richfaces.cdk:parent:4.3.1.Final contains old dependency: {code:xml} <dependency> <groupId>org.jboss.spec</groupId> <artifactId>jboss-javaee-web-6.0</artifactId> <version>${version.jboss-javaee}</version> <type>pom</type> <scope>import</scope> </dependency> {code} version.jboss-javaee is set to 3.0.1.Final. Upgrade it to 3.0.2.Final. -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13505) Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactory (blocked by Mojarra issue)

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13505?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on RF-13505: ---------------------------------- So I finally managed to run the job with proper versions. I have found one major bug, which IMHO affects other demos. {{r:ajax}} - {{render}} attribute, and overall rendering of components does not work correctly. How to reproduce: # download metamer.war built in the job, from [here|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view...] # deploy it on WildFly 8.0.0.Final # load page: http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml # set {{render}} attribute to: {{[output1]}} # submit some value # see that both outputs are rendered, only first one should be Other demos (other failed tests) are affected as well: * fileupload - after successful picture uploading, the info about it is not rendered correctly * all the other components and {{r:ajax}} render attribute > Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactory (blocked by Mojarra issue) > ----------------------------------------------------------------------------------------------------------------- > > Key: RF-13505 > URL: https://issues.jboss.org/browse/RF-13505 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha3 > Reporter: Lukáš Fryč > Assignee: Juraj Húska > Fix For: 5.0.0.Alpha4 > > > Mojarra issue: https://java.net/jira/browse/JAVASERVERFACES-3151 > We will still need to use some: > * resolve values in runtime > * add IDs for execution of AjaxOutput's > * collect list of meta-components to render > * wrap PartialResponseWriter#endDocument() for RichFaces extensions and JavascriptService -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13505) Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactory (blocked by Mojarra issue)

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13505?page=com.atlassian.jira.plugin.s... ] Juraj Húska edited comment on RF-13505 at 3/18/14 1:02 PM: ----------------------------------------------------------- So I finally managed to run the job with proper versions. I have found one *major* bug, which IMHO affects other demos. {{r:ajax}} - {{render}} attribute, and overall rendering of components does not work correctly. How to reproduce: # download metamer.war built in the job, from [here|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view...] # deploy it on WildFly 8.0.0.Final # load page: http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml # set {{render}} attribute to: {{[output1]}} # submit some value # see that both outputs are rendered, only first one should be Other demos (other failed tests) are affected as well: * fileupload - after successful picture uploading, the info about it is not rendered correctly * all the other components and {{r:ajax}} render attribute was (Author: jhuska): So I finally managed to run the job with proper versions. I have found one major bug, which IMHO affects other demos. {{r:ajax}} - {{render}} attribute, and overall rendering of components does not work correctly. How to reproduce: # download metamer.war built in the job, from [here|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view...] # deploy it on WildFly 8.0.0.Final # load page: http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml # set {{render}} attribute to: {{[output1]}} # submit some value # see that both outputs are rendered, only first one should be Other demos (other failed tests) are affected as well: * fileupload - after successful picture uploading, the info about it is not rendered correctly * all the other components and {{r:ajax}} render attribute > Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactory (blocked by Mojarra issue) > ----------------------------------------------------------------------------------------------------------------- > > Key: RF-13505 > URL: https://issues.jboss.org/browse/RF-13505 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha3 > Reporter: Lukáš Fryč > Assignee: Juraj Húska > Fix For: 5.0.0.Alpha4 > > > Mojarra issue: https://java.net/jira/browse/JAVASERVERFACES-3151 > We will still need to use some: > * resolve values in runtime > * add IDs for execution of AjaxOutput's > * collect list of meta-components to render > * wrap PartialResponseWriter#endDocument() for RichFaces extensions and JavascriptService -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13505) Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactory (blocked by Mojarra issue)

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13505?page=com.atlassian.jira.plugin.s... ] Juraj Húska updated RF-13505: ----------------------------- Assignee: (was: Juraj Húska) > Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactory (blocked by Mojarra issue) > ----------------------------------------------------------------------------------------------------------------- > > Key: RF-13505 > URL: https://issues.jboss.org/browse/RF-13505 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha3 > Reporter: Lukáš Fryč > Fix For: 5.0.0.Alpha4 > > > Mojarra issue: https://java.net/jira/browse/JAVASERVERFACES-3151 > We will still need to use some: > * resolve values in runtime > * add IDs for execution of AjaxOutput's > * collect list of meta-components to render > * wrap PartialResponseWriter#endDocument() for RichFaces extensions and JavascriptService -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-12289) rich:dataTable and rich:dataScroller inside h:panelGroup - doesn't display the correct number of rows when number of rows is updated

by Jonáš Trantina (JIRA)

[ https://issues.jboss.org/browse/RF-12289?page=com.atlassian.jira.plugin.s... ] Jonáš Trantina commented on RF-12289: ------------------------------------- The issue is reproducible even with <a4j:outputPanel> instead of <h:panelGroup>. > rich:dataTable and rich:dataScroller inside h:panelGroup - doesn't display the correct number of rows when number of rows is updated > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: RF-12289 > URL: https://issues.jboss.org/browse/RF-12289 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.1.Final, 4.2.2.Final, 4.3.5 > Reporter: Nicolas Daniels > Fix For: 5-Tracking > > Attachments: another-reproducer.zip, richfaces-sandbox.zip, rich_dataTable-rows.png, test.jspx, TestFace.java > > > Trying to have datascroller with dynamic rows number, but it works only if dataScroller is above the table. > Basically, what I have is: > <h:selectOneMenu value="#{myBean.batchRows}"> > <f:selectItem itemLabel="10" itemValue="10"/> > <f:selectItem itemLabel="20" itemValue="20"/> > <f:ajax render="table table-ds" /> > </h:selectOneMenu> > ... > <h:panelGroup> > <rich:dataTable id="table" rows="#{myBean.batchRows}" value="#{myBean.dataModel}" var="var"> > ... > </rich:dataTable> > </h:panelGroup> > <rich:dataScroller id="table-ds" page="#{myBean.batchPage}" for="table" renderIfSinglePage="false" boundaryControls="hide" fastControls="hide"> > ... > </rich:dataScroller> > > And the behaviour with 21 elements: > - on page 2 displaying 20 element (so only 1 is visible), if I switch to 10, I stay on page 2 but I still have only 1 element visible. > > If my datascroller is above my table it works fine. If the table is not wrapped within a panelGroup, it works as well. > > Debugging a bit, it seems that when UIDataAdaptor.walk method is 1st called, getComponentState() is updating the state rows and first properties with values: > - rows: 10 (correct) > - first: 20 (weird) > > Following calls to this method is setting those properties to: > - rows: 10 (correct) > - first: 10 (correct) > -- 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

10 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues March 2014