[JBoss JIRA] (RF-13186) Showcase 4.5.x fails
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13186?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13186:
---------------------------------
Thanks Michal,
I will look into remaining issues, I have described them in separated issues:
* RF-13214 - TreeModelAdaptor and TreeModelRecursive Adaptor doesn't work
* RF-13213 - RichFaces 4.5 CSV should share logic with RichFaces 5
* RF-13212 - Re-factor RichFaces 4.5 Queues so that they will share client-side queuing implementation
* RF-13211 - Rewrite Push 4.5 component so that it will re-use RichFaces 5 renderer
* RF-13210 - Move RichFaces resources from META-INF/resources/ to org.richfaces library
> Showcase 4.5.x fails
> --------------------
>
> Key: RF-13186
> URL: https://issues.jboss.org/browse/RF-13186
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Michal Petrov
> Assignee: Lukáš Fryč
> Fix For: 5.0.0.Alpha2
>
>
> [https://github.com/michpetrov/richfaces/tree/showcase-4.5.x/examples/show...] - showcase 4.5
> [https://github.com/richfaces4/components/tree/4.5.x] - 4.5.x components
> [https://github.com/richfaces4/dev-examples/tree/4.5.x] - 4.5 dev-examples
> Builds and deploys fine.
> Examples that do not work:
> * -several examples (e.g. actionListener) produce "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"-
> * validation - fails because rf.rf4.ui.Message is not defined, the resource is not being included due to resource optimization
> * trees/rich:tree - missing …/javax.faces.resource/node_icon.gif.jsf?ln=org.richfaces
> * menus/rich:contextMenu and rich:dropDownMenu - not working, probably for the same reason as validators (missing proper javascript resource)
> * inputs/rich:inplaceInput - ditto
> * selects/rich:inplaceSelect - ditto
> * output/rich:tooltip - ditto
> When resource optimization some components (dataTables) are missing background image causing a badly generated CSS. {{background-image: url()}}
> h5. resource optimization turned off
> h6. Issue with Validator
> - org.richfaces.validator.FacesObjectDescriptor.getMessage()
> - collision between RF4.5 and RF5
> the interface is the same in both versions but the Message class is in different packages in the two
> h6. Issue with menus
> - org.richfaces.renderkit.html.MenuItemRendererBase.getUtils()
> - probably the same problem
--
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, 9 months
[JBoss JIRA] (RF-13211) Rewrite Push 4.5 component so that it will re-use RichFaces 5 renderer
by Lukáš Fryč (JIRA)
Lukáš Fryč created RF-13211:
-------------------------------
Summary: Rewrite Push 4.5 component so that it will re-use RichFaces 5 renderer
Key: RF-13211
URL: https://issues.jboss.org/browse/RF-13211
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: component-push/poll
Affects Versions: 4.5.0.Alpha1
Reporter: Lukáš Fryč
a4j:push and r:push will should reuse same logic since they share client-side Push service that implements topic registration, etc.
That's why they shouldn't be two non-conflicting (name-spaced) components, but just one which shares logic (even renderers).
--
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, 9 months
[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-12802:
-----------------------------
Assignee: Brian Leathem (was: Juraj Húska)
> Move page fragments from repository qa to richfaces5
> ----------------------------------------------------
>
> Key: RF-12802
> URL: https://issues.jboss.org/browse/RF-12802
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 5.0.0.Alpha1
> Reporter: Pavol Pitonak
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
>
> As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework.
> We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations.
--
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, 9 months
[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ]
Juraj Húska commented on RF-12802:
----------------------------------
We have finished the first round of the refactoring.
In this is the [last|https://github.com/richfaces/richfaces-qa/commit/6e8f58cac501848c614...] commit I have added a showcase class for each page fragment. It is always in the package with the specific fragment, and the the name pattern for it is {{*Showcase.java}}. I wanted to showcase the high level API of each fragment in this way. It is how the end non-rf tester should use the fragment.
I was wondering about adding such a piece of code to the component reference for each component, so it can be reused.
Now, we would like to kindly ask the development team for a review.
Then we can proceed with JavaDoc or other refactorings.
> Move page fragments from repository qa to richfaces5
> ----------------------------------------------------
>
> Key: RF-12802
> URL: https://issues.jboss.org/browse/RF-12802
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 5.0.0.Alpha1
> Reporter: Pavol Pitonak
> Assignee: Juraj Húska
> Fix For: 5.0.0.Alpha2
>
>
> As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework.
> We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations.
--
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, 9 months
[JBoss JIRA] (RF-13208) Push: error "not well-formed" appears in browser console in Firefox
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13208?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13208:
---------------------------------
I can confirm that this *isn't* regression caused by Atmosphere upgrade (the response is same as with RichFaces 4.3.3.Final).
> Push: error "not well-formed" appears in browser console in Firefox
> -------------------------------------------------------------------
>
> Key: RF-13208
> URL: https://issues.jboss.org/browse/RF-13208
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.4
> Environment: RichFaces 4.3.4.Final
> Metamer 4.3.4.20130919-Final
> Mojarra 2.1.19
> EAP 6.1.1
> OpenJDK Runtime Environment 1.7.0_40-mockbuild_2013_09_19_20_10-b00 @ Linux
> Firefox 24.0 @ Linux x86_64
> Reporter: Pavol Pitonak
> Fix For: 4.3.5, 5.0.0.Alpha3
>
> Attachments: firefox_console.png
>
>
> # deploy Metamer and open http://127.0.0.1:8080/metamer/faces/components/a4jPush/twoPush.xhtml
> # open browser console
> # click "Push 2!" button
> result:
> * browser console contains "not well-formed" JavaScript error (see screenshot)
> * when you click on the error, you can see something like this:
> {quote}
> <"topic":"jmsSampleAddress2","data":"day: 23, month: 9, time: 11:01:12.829","number":0>
> {quote}
> * component seems to work fine despite this error
> * I couldn't see this error in Chrome 29
--
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, 9 months
[JBoss JIRA] (RF-13204) Loading of com.jqueryui library fails, most of the components which depend on it do not work
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13204?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13204:
------------------------------------
Note that the jquery resources are now contained in a git submodule. When you do a git checkout, you have to ensure that you include the git submodule:
http://stackoverflow.com/questions/3796927/how-to-git-clone-including-sub...
Can you verify whether this step was performed before we proceed with further issue verification?
> Loading of com.jqueryui library fails, most of the components which depend on it do not work
> --------------------------------------------------------------------------------------------
>
> Key: RF-13204
> URL: https://issues.jboss.org/browse/RF-13204
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: base functionality, resource handling
> Affects Versions: 5.0.0.Alpha2
> Environment: JBoss AS 7.1.1.Final, Tomcat 7
> Chrome, Firefox
> Reporter: Juraj Húska
> Priority: Blocker
> Labels: regression
> Fix For: 5.0.0.Alpha2
>
>
> When loading page with components which {{@ResourceDependency}} links to library {{com.jqueryui}}, following error is rendered into the AS console:
> {code}
> 11:15:08,155 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-1) JSF1064: Unable to find or serve resource, jquery.ui.core.js, from library, com.jqueryui.
> {code}
> There is an error on browser console (This one e.g. for DaD):
> {code}
> GET http://localhost:8080/showcase/richfaces/RES_NOT_FOUND 404 (Not Found) component-sample.jsf:23
> Uncaught TypeError: Object [object Object] has no method 'draggable'
> {code}
> Following components are affected:
> # DaD
> # Calendar
> # Autocomplete
> # Focus
> Those components functionality is broken.
--
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, 9 months