June 2014 - richfaces-planning-issues

[JBoss JIRA] (RFPL-3371) Developer guide 4.5.0.Alpha3 updates

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-3371?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-3371: -------------------------------- Fix Version/s: 4.5.0.Alpha3 > Developer guide 4.5.0.Alpha3 updates > ------------------------------------ > > Key: RFPL-3371 > URL: https://issues.jboss.org/browse/RFPL-3371 > Project: RichFaces Planning > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj Húska > Fix For: 4.5.0.Alpha3 > > > Below you can find changes required to be made for Developer guide on {{4.5.0.Alpha3}} > * 2.1. Technical Requirements > ** update browser versions > * 2.1.1. Project libraries and dependencies > ** RichFaces library is not distributed as a single jar, list the jar files > ** update javax.faces.jar to 2.1.28 or higher > ** udpate guava version to 16.0.1 > ** css parser to 0.9.14 > ** atmosphere to 1.0.18 > ** weld-servlet 1.1.18 > * 2.4. Creating a project with JBoss Developer Studio > ** 3. Reference the tag library - missing a4j namespace > * 2.5.2. Using the RichFaces project archetype > ** for 4.5.x there are no archetypes, are we going to release them as well ? > * Import the project into an IDE > ** no need to install maven support to JBoss Developer studio > ** the address where the project is accessible when deployed: http://localhost:8080/jsf-app/ depends on the name a user would choose when creating the project from archetype - it should be mentioned that jsf-app is placeholder > * 3.1.1. Server requirements > ** it will not work with JBoss AS 7, need EAP 6.2.3+ or WildFly 8.0.0.Final+ > * 4.4. Component overview > ** The RichFaces framework is not made up of the sinlge tag library. > builidng -> building > * 6.4.1. Creating a new skin > blueSky.skin.properties is in richfaces-core-version.jar > * Appendix B. Migration Notes > popupPanel autosize and min, max attributes change - more info in RF-13629 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3373) Developer guide for 4.5.0-Alpha3 bugs

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RFPL-3373?page=com.atlassian.jira.plugin.... ] Juraj Húska updated RFPL-3373: ------------------------------ Priority: Critical (was: Major) > Developer guide for 4.5.0-Alpha3 bugs > ------------------------------------- > > Key: RFPL-3373 > URL: https://issues.jboss.org/browse/RFPL-3373 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj Húska > Priority: Critical > > There are some bugs in 4.5.0.Alpha3 Developer guide: > * with [this|https://github.com/richfaces/richfaces-docs/commit/74ec6117009436818...] commit it was intended to change {{r}} namespace to {{rich}}, however, words ending with 'r' are altered as well, so e.g. {{background-color}} CSS property was changed to {{background-colorich}} > * imho {{rich}} namespace should be used instead of {{r}}, like it is in 4.3.x. It looks more uniformed together with {{a4j}}. {{r}} is used e.g. in code snippet for _2.4. Creating a project with JBoss Developer Studio_ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3373) Developer guide for 4.5.0-Alpha3 bugs

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RFPL-3373?page=com.atlassian.jira.plugin.... ] Juraj Húska updated RFPL-3373: ------------------------------ Description: There are some bugs in 4.5.0.Alpha3 Developer guide: * with [this|https://github.com/richfaces/richfaces-docs/commit/74ec6117009436818...] commit it was intended to change {{r}} namespace to {{rich}}, however, words ending with 'r' are altered as well, so e.g. {{background-color}} CSS property was changed to {{background-colorich}} * imho {{rich}} namespace should be used instead of {{r}}, like it is in 4.3.x. It looks more uniformed together with {{a4j}}. {{r}} is used e.g. in code snippet for _2.4. Creating a project with JBoss Developer Studio_ was: There are some bugs in 4.5.0.Alpha3 Developer guide: * with [this|https://github.com/richfaces/richfaces-docs/commit/74ec6117009436818...] commit it was intended to change {{r}} namespace to {{rich}}, however, words ending with 'r' are altered as well, so e.g. {{background-color}} CSS property was changed to {{background-colorich}} > Developer guide for 4.5.0-Alpha3 bugs > ------------------------------------- > > Key: RFPL-3373 > URL: https://issues.jboss.org/browse/RFPL-3373 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj Húska > > There are some bugs in 4.5.0.Alpha3 Developer guide: > * with [this|https://github.com/richfaces/richfaces-docs/commit/74ec6117009436818...] commit it was intended to change {{r}} namespace to {{rich}}, however, words ending with 'r' are altered as well, so e.g. {{background-color}} CSS property was changed to {{background-colorich}} > * imho {{rich}} namespace should be used instead of {{r}}, like it is in 4.3.x. It looks more uniformed together with {{a4j}}. {{r}} is used e.g. in code snippet for _2.4. Creating a project with JBoss Developer Studio_ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3373) Developer guide for 4.5.0-Alpha3 bugs

by Juraj Húska (JIRA)

Juraj Húska created RFPL-3373: --------------------------------- Summary: Developer guide for 4.5.0-Alpha3 bugs Key: RFPL-3373 URL: https://issues.jboss.org/browse/RFPL-3373 Project: RichFaces Planning Issue Type: Bug Security Level: Public (Everyone can see) Components: doc Affects Versions: 4.5.0.Alpha3 Reporter: Juraj Húska There are some bugs in 4.5.0.Alpha3 Developer guide: * with [this|https://github.com/richfaces/richfaces-docs/commit/74ec6117009436818...] commit it was intended to change {{r}} namespace to {{rich}}, however, words ending with 'r' are altered as well, so e.g. {{background-color}} CSS property was changed to {{background-colorich}} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3370) Fix TraviCI build

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RFPL-3370?page=com.atlassian.jira.plugin.... ] Juraj Húska commented on RFPL-3370: ----------------------------------- [Last build|https://travis-ci.org/richfaces/richfaces/builds/28066878] for 4.5.x passed. > Fix TraviCI build > ----------------- > > Key: RFPL-3370 > URL: https://issues.jboss.org/browse/RFPL-3370 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.5.0.Alpha2 > Reporter: Pavol Pitonak > Assignee: Juraj Húska > Fix For: 4.5.0.Beta1 > > > https://travis-ci.org/richfaces/richfaces -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3372) Component reference 4.5.0.Alpha3 updates

by Juraj Húska (JIRA)

Juraj Húska created RFPL-3372: --------------------------------- Summary: Component reference 4.5.0.Alpha3 updates Key: RFPL-3372 URL: https://issues.jboss.org/browse/RFPL-3372 Project: RichFaces Planning Issue Type: Enhancement Security Level: Public (Everyone can see) Components: doc Affects Versions: 4.5.0.Alpha3 Reporter: Juraj Húska Below you can find some changes need to be done for Component reference in 4.5.0.Alpha3 * 3.8.9.2. Configuring JMS backend ** it should be used how to configure it for WildFly instead of JBoss AS * rich:editor ** alter the note which has links for CKEditor 3, to point to CKEditor 4 ** changing the skin needs to be done with its JS API from now on * togglePanel ** Example 9.4. Basic usage - code snippet contains redundant '?' characters * EDT ** 10.6.3.3. Row selection - code snippet, {{import org.richfaces.component.UIExtendedDataTable;}} needs to be changed to {{import org.richfaces.component.AbstractExtendedDataTable;}} and the usage of {{UIExtendedDataTable}} as well -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3371) Developer guide 4.5.0.Alpha3 updates

by Juraj Húska (JIRA)

Juraj Húska created RFPL-3371: --------------------------------- Summary: Developer guide 4.5.0.Alpha3 updates Key: RFPL-3371 URL: https://issues.jboss.org/browse/RFPL-3371 Project: RichFaces Planning Issue Type: Enhancement Security Level: Public (Everyone can see) Components: doc Affects Versions: 4.5.0.Alpha3 Reporter: Juraj Húska Below you can find changes required to be made for Developer guide on {{4.5.0.Alpha3}} * 2.1. Technical Requirements ** update browser versions * 2.1.1. Project libraries and dependencies ** RichFaces library is not distributed as a single jar, list the jar files ** update javax.faces.jar to 2.1.28 or higher ** udpate guava version to 16.0.1 ** css parser to 0.9.14 ** atmosphere to 1.0.18 ** weld-servlet 1.1.18 * 2.4. Creating a project with JBoss Developer Studio ** 3. Reference the tag library - missing a4j namespace * 2.5.2. Using the RichFaces project archetype ** for 4.5.x there are no archetypes, are we going to release them as well ? * Import the project into an IDE ** no need to install maven support to JBoss Developer studio ** the address where the project is accessible when deployed: http://localhost:8080/jsf-app/ depends on the name a user would choose when creating the project from archetype - it should be mentioned that jsf-app is placeholder * 3.1.1. Server requirements ** it will not work with JBoss AS 7, need EAP 6.2.3+ or WildFly 8.0.0.Final+ * 4.4. Component overview ** The RichFaces framework is not made up of the sinlge tag library. builidng -> building * 6.4.1. Creating a new skin blueSky.skin.properties is in richfaces-core-version.jar * Appendix B. Migration Notes popupPanel autosize and min, max attributes change - more info in RF-13629 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3281) Test new implemetation of file upload

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RFPL-3281?page=com.atlassian.jira.plugin.... ] Juraj Húska edited comment on RFPL-3281 at 6/18/14 8:42 AM: ------------------------------------------------------------ There still seems to be some problems to test new file upload. I think it is on Graphene side, but I need to investigate more on this. The problem is with: {{MetamerPage.waitRequest(fileUpload, WaitRequestType.XHR).upload();}}, the uploading is triggered correctly, however, it hangs on progress facelet, and therefore the uploading is not finished correctly, and the request time is not updated. Manually it works as it should. was (Author: jhuska): There still seems to be some problems. I think it is on Graphene side, but I need to investigate more on this. The problem is with: {{MetamerPage.waitRequest(fileUpload, WaitRequestType.XHR).upload();}}, the uploading is triggered correctly, however, it hangs on progress facelet, and therefore the uploading is not finished correctly, and the request time is not updated. Manually it works as it should. > Test new implemetation of file upload > ------------------------------------- > > Key: RFPL-3281 > URL: https://issues.jboss.org/browse/RFPL-3281 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 5.0.0.Alpha3 > Reporter: Pavol Pitonak > Assignee: Juraj Húska > > The file upload component in RichFaces 5 was reimplemented. > * Everything expected to work > * Using Servlet 3.0 API for file uploads - won't work on Tomcat 6 > * Files are sent through an XHR request (as opposed to the previous iframe approach) > * Originally had to intercept the request early to get upload progress updates > but now we monitor the upload progress on the client, so this is not needed -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3281) Test new implemetation of file upload

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RFPL-3281?page=com.atlassian.jira.plugin.... ] Juraj Húska commented on RFPL-3281: ----------------------------------- There still seems to be some problems. I think it is on Graphene side, but I need to investigate more on this. The problem is with: {{MetamerPage.waitRequest(fileUpload, WaitRequestType.XHR).upload();}}, the uploading is triggered correctly, however, it hangs on progress facelet, and therefore the uploading is not finished correctly, and the request time is not updated. Manually it works as it should. > Test new implemetation of file upload > ------------------------------------- > > Key: RFPL-3281 > URL: https://issues.jboss.org/browse/RFPL-3281 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 5.0.0.Alpha3 > Reporter: Pavol Pitonak > Assignee: Juraj Húska > > The file upload component in RichFaces 5 was reimplemented. > * Everything expected to work > * Using Servlet 3.0 API for file uploads - won't work on Tomcat 6 > * Files are sent through an XHR request (as opposed to the previous iframe approach) > * Originally had to intercept the request early to get upload progress updates > but now we monitor the upload progress on the client, so this is not needed -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3281) Test new implemetation of file upload

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RFPL-3281?page=com.atlassian.jira.plugin.... ] Juraj Húska updated RFPL-3281: ------------------------------ Comment: was deleted (was: The tests need to be rewritten a little bit. E.g. usage of {{Graphene.guardAjax}} is now preferred before {{MetamerPage.waitRequest}}.) > Test new implemetation of file upload > ------------------------------------- > > Key: RFPL-3281 > URL: https://issues.jboss.org/browse/RFPL-3281 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 5.0.0.Alpha3 > Reporter: Pavol Pitonak > Assignee: Juraj Húska > > The file upload component in RichFaces 5 was reimplemented. > * Everything expected to work > * Using Servlet 3.0 API for file uploads - won't work on Tomcat 6 > * Files are sent through an XHR request (as opposed to the previous iframe approach) > * Originally had to intercept the request early to get upload progress updates > but now we monitor the upload progress on the client, so this is not needed -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

richfaces-planning-issues June 2014