[JBoss JIRA] (RF-13518) Action Listener - invoking from composite component does not work
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13518?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13518:
---------------------------------
Okay, we have resolved this by making our impl Mojarra 2.1 and Mojarra 2.2 compatible. We will try to push the spec issue forward.
> Action Listener - invoking from composite component does not work
> -----------------------------------------------------------------
>
> Key: RF-13518
> URL: https://issues.jboss.org/browse/RF-13518
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 5.0.0.Alpha3
> Environment: WildFly 8.0.0.Final-SNAPSHOT
> Reporter: Juraj Húska
> Assignee: Lukáš Fryč
> Priority: Critical
> Labels: jsf22
> Fix For: 5.0.0.Alpha3
>
>
> Invoking Action Listener from composite component does not work. Please see the steps to reproduce the issue.
> Note that it works with JSF 2.1.x. It is similar to issue RF-10585, but that one is for MyFaces.
--
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, 4 months
[JBoss JIRA] (RF-13518) Action Listener - invoking from composite component does not work
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13518?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč edited comment on RF-13518 at 1/30/14 9:31 AM:
----------------------------------------------------------
I believe this is under-specified section and the JSF API should allow to attach handlers into composite components.
What we can do is having two implementations - one for MyFaces and one for Mojarra.
I would prefer using compile-time dependency instead of this silly constant-based dependency.
Sample of usage of compile-time dependency is [implementation-dependent {{ResourceTracker}}|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/resource/external/ResourceTrackerImpl.java#L72].
was (Author: lfryc):
I believe this is under-specified section and the JSF API should allow to attach handlers into composite components.
What we can do is having two implementations - one for MyFaces and one for Mojarra.
I would prefer using compile-time dependency instead this silly constant-based dependency.
> Action Listener - invoking from composite component does not work
> -----------------------------------------------------------------
>
> Key: RF-13518
> URL: https://issues.jboss.org/browse/RF-13518
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 5.0.0.Alpha3
> Environment: WildFly 8.0.0.Final-SNAPSHOT
> Reporter: Juraj Húska
> Assignee: Lukáš Fryč
> Priority: Critical
> Labels: jsf22
> Fix For: 5.0.0.Alpha3
>
>
> Invoking Action Listener from composite component does not work. Please see the steps to reproduce the issue.
> Note that it works with JSF 2.1.x. It is similar to issue RF-10585, but that one is for MyFaces.
--
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, 4 months
[JBoss JIRA] (RF-13518) Action Listener - invoking from composite component does not work
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13518?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč edited comment on RF-13518 at 1/30/14 9:28 AM:
----------------------------------------------------------
The problem here (and in MyFaces as well) is that in our ActionListenerHandler we use [TagHandlerUtils that hard-code a constant for accessing context|https://github.com/richfaces/richfaces/blob/master/framework/src/...] of attached handlers for Composite Component.
As you can guess (and as it is commented in the code ;-) - *it is implementation dependent*).
Mojarra changed the constant from [{{"javax.faces.RetargetableHandlers"}}|https://github.com/jboss/mojarra/blob/2.1.27-jbossorg-1/jsf-ri/src/main/java/com/sun/faces/facelets/tag/jsf/CompositeComponentTagHandler.java#L327] to [{{"javax.faces.view.AttachedObjectHandlers"}}|https://github.com/jboss/mojarra/blob/2.2.5-jbossorg-3/jsf-ri/src/main/java/com/sun/faces/facelets/tag/jsf/CompositeComponentTagHandler.java#L337].
On the other hand, MyFaces approach is little bit different with their [{{FaceletCompositionContext#getAttachedObjectHandlers(UIComponent)}}|http://svn.apache.org/repos/asf/myfaces/core/tags/myfaces-core-module-2.2.0/impl/src/main/java/org/apache/myfaces/view/facelets/FaceletCompositionContext.java].
was (Author: lfryc):
The problem here (and in MyFaces as well) is that in our ActionListenerHandler we use [TagHandlerUtils that hard-code a constant for accessing context|https://github.com/richfaces/richfaces/blob/master/framework/src/...] of attached handlers for Composite Component.
As you can guess (and as it is commented in the code ;-) - *it is implementation dependent*).
Mojarra changed the constant from [{{"javax.faces.RetargetableHandlers"}}|https://github.com/jboss/mojarra/blob/2.1.27-jbossorg-1/jsf-ri/src/main/java/com/sun/faces/facelets/tag/jsf/CompositeComponentTagHandler.java#L327] to [{{"javax.faces.view.AttachedObjectHandlers}}|https://github.com/jboss/mojarr...].
On the other hand, MyFaces approach is little bit different with their [{{FaceletCompositionContext#getAttachedObjectHandlers(UIComponent)|http://svn.apache.org/repos/asf/myfaces/core/tags/myfaces-core-module-2.2.0/impl/src/main/java/org/apache/myfaces/view/facelets/FaceletCompositionContext.java].
> Action Listener - invoking from composite component does not work
> -----------------------------------------------------------------
>
> Key: RF-13518
> URL: https://issues.jboss.org/browse/RF-13518
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 5.0.0.Alpha3
> Environment: WildFly 8.0.0.Final-SNAPSHOT
> Reporter: Juraj Húska
> Assignee: Lukáš Fryč
> Priority: Critical
> Labels: jsf22
> Fix For: 5.0.0.Alpha3
>
>
> Invoking Action Listener from composite component does not work. Please see the steps to reproduce the issue.
> Note that it works with JSF 2.1.x. It is similar to issue RF-10585, but that one is for MyFaces.
--
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, 4 months
[JBoss JIRA] (RF-13518) Action Listener - invoking from composite component does not work
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13518?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13518:
---------------------------------
I believe this is under-specified section and the JSF API should allow to attach handlers into composite components.
What we can do is having two implementations - one for MyFaces and one for Mojarra.
I would prefer using compile-time dependency instead this silly constant-based dependency.
> Action Listener - invoking from composite component does not work
> -----------------------------------------------------------------
>
> Key: RF-13518
> URL: https://issues.jboss.org/browse/RF-13518
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 5.0.0.Alpha3
> Environment: WildFly 8.0.0.Final-SNAPSHOT
> Reporter: Juraj Húska
> Assignee: Lukáš Fryč
> Priority: Critical
> Labels: jsf22
> Fix For: 5.0.0.Alpha3
>
>
> Invoking Action Listener from composite component does not work. Please see the steps to reproduce the issue.
> Note that it works with JSF 2.1.x. It is similar to issue RF-10585, but that one is for MyFaces.
--
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, 4 months
[JBoss JIRA] (RF-13518) Action Listener - invoking from composite component does not work
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13518?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13518:
---------------------------------
The problem here (and in MyFaces as well) is that in our ActionListenerHandler we use [TagHandlerUtils that hard-code a constant for accessing context|https://github.com/richfaces/richfaces/blob/master/framework/src/...] of attached handlers for Composite Component.
As you can guess (and as it is commented in the code ;-) - *it is implementation dependent*).
Mojarra changed the constant from [{{"javax.faces.RetargetableHandlers"}}|https://github.com/jboss/mojarra/blob/2.1.27-jbossorg-1/jsf-ri/src/main/java/com/sun/faces/facelets/tag/jsf/CompositeComponentTagHandler.java#L327] to [{{"javax.faces.view.AttachedObjectHandlers}}|https://github.com/jboss/mojarr...].
On the other hand, MyFaces approach is little bit different with their [{{FaceletCompositionContext#getAttachedObjectHandlers(UIComponent)|http://svn.apache.org/repos/asf/myfaces/core/tags/myfaces-core-module-2.2.0/impl/src/main/java/org/apache/myfaces/view/facelets/FaceletCompositionContext.java].
> Action Listener - invoking from composite component does not work
> -----------------------------------------------------------------
>
> Key: RF-13518
> URL: https://issues.jboss.org/browse/RF-13518
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 5.0.0.Alpha3
> Environment: WildFly 8.0.0.Final-SNAPSHOT
> Reporter: Juraj Húska
> Assignee: Lukáš Fryč
> Priority: Critical
> Labels: jsf22
> Fix For: 5.0.0.Alpha3
>
>
> Invoking Action Listener from composite component does not work. Please see the steps to reproduce the issue.
> Note that it works with JSF 2.1.x. It is similar to issue RF-10585, but that one is for MyFaces.
--
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, 4 months
[JBoss JIRA] (RF-12613) rich:select with enablemanualinput selects wrong items
by Eu Sèbe (JIRA)
[ https://issues.jboss.org/browse/RF-12613?page=com.atlassian.jira.plugin.s... ]
Eu Sèbe commented on RF-12613:
------------------------------
Hi,
I implemented the workaround, and here is how it works now:
if I type a few characters, then select an item using up and down arrows, it works perfectly.
If I type a few characters then select an item using the mouse, it selects no item.
Did that happen for anyone else ? Is there any solution ?
> rich:select with enablemanualinput selects wrong items
> ------------------------------------------------------
>
> Key: RF-12613
> URL: https://issues.jboss.org/browse/RF-12613
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.1.0.Final, 4.3.0.M2
> Reporter: geert olaerts
> Fix For: 4.5-Tracking
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> When using rich:select with enablemanualinput = "true", the wrong item might be selected. If the list of possible items is (in this order): "test test" and "test" and the user selects "test" richfaces will select "test test" as input. The same happens if the user types "test". If the list is "test" and "test test" and the user selects or types "test" the correct item is selected.
--
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, 4 months