[JBoss JIRA] (RF-13484) Photoalbum: cannot interact with some components in images search result view
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/RF-13484?page=com.atlassian.jira.plugin.s... ]
Michal Petrov commented on RF-13484:
------------------------------------
There's something wrong with rendering
The reason it's not working is because
{code}
<a4j:outputPanel id="imagesList">
<ui:include src="/includes/image/inputNumberSlider.xhtml">
<ui:param name="renderArea" value="userAlbumImages" />
<ui:param name="size" value="#{fn:length(result)}" />
</ui:include>
<br />
<br />
<h:panelGroup id="userAlbumImages">
<rich:dataGrid …
{code}
is rendered as
{code}
<span id="overForm:j_idt534">
<div> … </div>
<br>
<br>
<table …
{code}
Meaning the a4j:outputPanel is rendered but without the proper id and the h:panelGroup is not rendered at all (causing the failure as the renderers cannot find the id), similar code is used in other places and it works there.
> Photoalbum: cannot interact with some components in images search result view
> -----------------------------------------------------------------------------
>
> Key: RF-13484
> URL: https://issues.jboss.org/browse/RF-13484
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.3.5
> Environment: JBoss AS 7.1.1
> Reporter: Jiří Štefek
> Assignee: Michal Petrov
> Labels: photoalbum
> Fix For: 4.3.5
>
>
> Works on EAP 6.1.
--
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-13482) Photoalbum: after edit user profile view is opened the application does not respond correctly
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13482?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč edited comment on RF-13482 at 1/17/14 9:10 AM:
----------------------------------------------------------
I have found that the popup is not rendered because the commandLink is not executed.
During debugging we have revealed that doDecode method of the commandLinked's renderer is not executed.
It is caused by a fact that when the component should be executed during APPLY_REQUEST_VALUES phase, the tree is traversed by EPVC and it uses JSF's native traversal mechanism to visit all components that are in EPVCI's {{executedIds}} collection (which is {{["j_idt330"]}}).
But the debugging revealed that where the component {{"j_idt330"}} should be, the same component lies but with different ID ({{"j_idt666"}}). Which is somehow related to partial state saving (I would actually try to this on MyFaces).
Initially I have though that it is caused by UIOutputPanelWorkaround component that wraps the commandLink, but that's not the case (when disabled it didn't help). What helped to overcome this issue is turning {{javax.faces.PARTIAL_STATE_SAVING=false}}. This can be used as workaround.
However the root cause is not known yet and as [~michpetrov] pointed out, turning partial state saving off causes drag-n-drop to stop to work.
was (Author: lfryc):
I have found that the popup is not rendered because the commandLink is not executed.
During debugging we have revealed that doDecode method of the commandLinked's renderer is not executed.
It is caused by a fact that when the component should be executed during APPLY_REQUEST_VALUES phase, the tree is traversed by EPVC and it uses JSF's native traversal mechanism to visit all components that are in EPVCI's {{executedIds}} collection (which is {{["j_idt330"]}}).
But the debugging revealed that where the component {{"j_idt330"}} should be, the same component lies but with different ID ({{"j_idt666"}}.
Initially I have though that it is caused by UIOutputPanelWorkaround component that wraps the commandLink, but that's not the case (when disabled it didn't help). What helped to overcome this issue is turning {{javax.faces.PARTIAL_STATE_SAVING=false}}. This can be used as workaround.
However the root cause is not known yet and as [~michpetrov] pointed out, turning partial state saving off causes drag-n-drop to stop to work.
> Photoalbum: after edit user profile view is opened the application does not respond correctly
> ---------------------------------------------------------------------------------------------
>
> Key: RF-13482
> URL: https://issues.jboss.org/browse/RF-13482
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.3.4
> Reporter: Jiří Štefek
> Assignee: Michal Petrov
> Labels: photoalbum
> Fix For: 4.3.5
>
>
--
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-13482) Photoalbum: after edit user profile view is opened the application does not respond correctly
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13482?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13482:
---------------------------------
I have found that the popup is not rendered because the commandLink is not executed.
During debugging we have revealed that doDecode method of the commandLinked's renderer is not executed.
It is caused by a fact that when the component should be executed during APPLY_REQUEST_VALUES phase, the tree is traversed by EPVC and it uses JSF's native traversal mechanism to visit all components that are in EPVCI's {{executedIds}} collection (which is {{["j_idt330"]}}).
But the debugging revealed that where the component {{"j_idt330"}} should be, the same component lies but with different ID ({{"j_idt666"}}.
Initially I have though that it is caused by UIOutputPanelWorkaround component that wraps the commandLink, but that's not the case (when disabled it didn't help). What helped to overcome this issue is turning {{javax.faces.PARTIAL_STATE_SAVING=false}}. This can be used as workaround.
However the root cause is not known yet and as [~michpetrov] pointed out, turning partial state saving off causes drag-n-drop to stop to work.
> Photoalbum: after edit user profile view is opened the application does not respond correctly
> ---------------------------------------------------------------------------------------------
>
> Key: RF-13482
> URL: https://issues.jboss.org/browse/RF-13482
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.3.4
> Reporter: Jiří Štefek
> Assignee: Michal Petrov
> Labels: photoalbum
> Fix For: 4.3.5
>
>
--
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-13274) Use QSTools:archetypeSync to keep the kitchensink archetype synchronized with the kithensink-rf quickstart
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13274?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak closed RF-13274.
------------------------------
Seems to work fine. Enterprise version verified with 4.3.4.Final-redhat-1 bits because there is no 4.3.5.Final-redhat-1 version yet.
> Use QSTools:archetypeSync to keep the kitchensink archetype synchronized with the kithensink-rf quickstart
> -----------------------------------------------------------------------------------------------------------
>
> Key: RF-13274
> URL: https://issues.jboss.org/browse/RF-13274
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 4.3.5
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> As per [~rafabene]'s description in IRC:
> {quote}
> use QSTools:archetypeSync to keep your Archetype Synchornized with the kithensink-rf Quickstart as we did for our Archetypes
> look at an example here: https://github.com/jboss-developer/jboss-eap-archetypes/blob/master/jboss...
> you tell where the quickstart is projectGitRepo projectPath
> tell what's your branch or commit or tag
> them what's your rootPackage
> you can configure expression that will be replaced by $\{artifactId} with archetypeExpressionReplaceValues
> so every fix that you make on Quickstarts will be available on your next Archetype build
> call me if you have any issues with QSTools:archetypeSync
> {quote}
--
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-13239) Popup panel: CSS class rf-pp-hdr contains invalid property repeat-x
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13239?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-13239:
------------------------------------
Works fine in 4.3.5-SNAPSHOT.
I couldn't verify in 4.5 because of RF-13495 nor in 5.0 because of RF-13496.
> Popup panel: CSS class rf-pp-hdr contains invalid property repeat-x
> -------------------------------------------------------------------
>
> Key: RF-13239
> URL: https://issues.jboss.org/browse/RF-13239
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 5.0.0.Alpha1
> Environment: RichFaces 5.0.0-SNAPSHOT
> Reporter: Pavol Pitonak
> Assignee: Brian Leathem
> Priority: Minor
> Labels: needs-qe
> Fix For: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richPopupPanel/simple.xhtml
> # check browser console
> result:
> * Invalid CSS property name: repeat-x (in popupPanel.ecss, line 40)
> possible solution:
> * replace
> {code}
> .rf-pp-hdr {
> background: url(...);
> repeat-x: top left #BED6F8;
> ...
> }
> {code}
> * with
> {code}
> .rf-pp-hdr {
> background: url(...) repeat-x top left #BED6F8;
> ...
> }
> {code}
--
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