[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 resolved RFPL-3281.
-------------------------------
Resolution: Done
> 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, 8 months
[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:
-----------------------------------
Thanks to prompt fix of [~okiss], the ARQGRA-455 is resolved now. I have tried tests with Graphene SNAPSHOT and it works. Resolving.
> 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, 8 months
[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 resolved RFPL-3371.
---------------------------------
Resolution: Done
> 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.Beta1
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> 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, 8 months
[JBoss JIRA] (RFPL-3372) Component reference 4.5.0.Alpha3 updates
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RFPL-3372?page=com.atlassian.jira.plugin.... ]
Brian Leathem resolved RFPL-3372.
---------------------------------
Assignee: Brian Leathem
Resolution: Done
> 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
> Assignee: Brian Leathem
> Fix For: 4.5.0.Beta1
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> 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, 8 months
[JBoss JIRA] (RFPL-3418) Metamer with MyFaces
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RFPL-3418?page=com.atlassian.jira.plugin.... ]
Matej Novotny resolved RFPL-3418.
---------------------------------
Resolution: Done
Resolved along with RF-13758.
> Metamer with MyFaces
> --------------------
>
> Key: RFPL-3418
> URL: https://issues.jboss.org/browse/RFPL-3418
> Project: RichFaces Planning
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.5.0.Alpha3
> Environment: Tomcat 7/8
> MyFaces (2.1.x, 2.2.x)
> RF 4.5.0.Alpha3
> Reporter: Matej Novotny
> Assignee: Matej Novotny
>
> Metamer with MyFaces does not display components correctly.
> It can be deployed (to Tomcat) without errors but once you load the [main page|http://localhost:8080/metamer-tomcat7-myfaces/faces/index.xhtml], you can see that the panel is not rendered correctly. Also one can browse to for instance [accordion page|http://localhost:8080/metamer-tomcat7-myfaces/faces/components/richAccordion/simple.xhtml] which is displayed as plain text.
> This is likely to be due to some resources (styling) not loaded.
> Showcase and simpleapp work both fine with MyFaces so it's Metamer related only.
> Also this bug cannot be reproduced with 4.3.x.
> With MyFaces the following CSS files are present on the accordion page:
> * common.ecss
> * attributes.ecss
> * skinning.ecss
> While with Mojarra these are present:
> * common.ecss
> * attributes.ecss
> * accordion.css
> * icons.css
> * log.css
> * skinning.ecss
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[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:
--------------------------------
Sprint: 4.5.0.Beta1 - Upgrade Sprint (was: 4.5.0.Beta1 - Doc Sprint)
> 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.Beta1
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> 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, 8 months