[ 
https://issues.jboss.org/browse/RF-12907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771610#comment-12771610
 ] 

Jean ANDRE edited comment on RF-12907 at 5/2/13 9:44 AM:
---------------------------------------------------------

Hello Brian,

What we observed, is replacing our Ids by @form or @all requires to click twice 
to fire the action. Then there is a refresh problem. Using JSF tags like @form 
or @all should work at anytime as the documentation does not tell any 
limitation or constraint in using them. It is simply not normal that those tags 
do not perform well under RF components. And what we expected is to click only 
once to fire an action on button or on link.

Moreover, it is not normal that in such case, we do not have any message error 
from JSF or RF. Because the request hits the server but no action is done... IF 
we restore our ids, it works, so what is wrong ? What is missing ?

As we said since the beginning, since we starting using RF 2 years ago, while 
you're refactoring it and us suffering a lot, the complexity is a part of the 
problem. We did the ITBH as the simplest application implementing the SPA 
concept, highly dynamic, based on RF tab panel. We think that a too much 
trivial project might not give you the problem.

Did you have at least install it, begin using it ? The report is only one 
issue, about @form or @all but we different scenarios or paths to reproduce the 
bug.

We do not need debugging the application for us because ITBH is not the real 
application. It is just a basic project to validate the stack technology. The 
real project is much bigger, much more complex at the UI level. ITBH is just a 
starting point, a baseline for us. ITBH is a communication tool between third 
parties and us.

We did this report, only for RF, not really for us as using our id, it is 
working. But we think that it is very interesting case for you  and the 
community as we are not alone in such situation where clicking on button or 
link does not trigger the expected action and I do not talk about the classical 
reason like:
         - bad name of the method controller
         - forgot the immediate = true
         - forgot the h:messages
         - Model change at the server side
         - and so on.

We start from a running well application, we change our ids by @all or @form 
and the application does not work anymore.

All the story since 2 years rise a simple question: Does RF can really coexist 
with JSF 2 smoothly ? Can we have a stable and robust version on which we can 
construct our business software ?


Best regards,

JA

                
      was (Author: jorelia64):
    Hello Brian,

What we observed, is replacing our Ids by @form or @all requires to click twice 
to fire the action. Then there is a refresh problem. Using JSF tags like @form 
or @all should work at anytime as the documentation does not tell any 
limitation or constraint in using them. It is simply not normal that those tags 
do not perform well under RF components. And what we expected is to click only 
once to fire an action on button or on link.

Moreover, it is not normal that in such case, we do not have any message error 
from JSF or RF. Because the request hits the server but no action is done... IF 
we restore our ids, it works, so what is wrong ? What is missing ?

As we said since the beginning, since we starting using RF 2 years ago, while 
you're refactoring it and us suffering a lot, the complexity is a part of the 
problem. We did the ITBH as the simplest application implementing the SPA 
concept, highly dynamic, based on RF tab panel. We think that a too much 
trivial project might not give you the problem.

Did you have at least install it, begin using it ? The report is only one 
issue, about @form or @all but we different scenarios or paths to reproduce the 
bug.

We do not need debugging the application for us because ITBH is not the real 
application. It is just a basic project to validate the stack technology. The 
real project is much bigger, much more complex at the UI level. ITBH is just a 
starting point, a baseline for us. ITBH is a communication tool between third 
parties and us.

We did this report, only for RF, not really for us as using our id, it is 
working. But we think that it is very interesting case for you  and the 
community as we are not alone in such situation where clicking on button or 
link does not trigger the expected action and I do not talk about the classical 
reason like:
         - bad name of the method controller
         - forgot the immediate = true
         - forgot the h:messages
         - Model change at the server side
         - and so on.

We start from a running well application, we change our ids by @all or @form 
and the application does not work anymore.

All the story since 2 years rise a simple question: Does RF can really coexist 
with JSF 2 smoothly ? Can we have a stable and robust version on which we can 
construct our business software ? We heard that using PrimesFaces is more 
advanced project, probably we will test this framework on and with ITBH.


Best regards,

JA

                  
> render="@form" problem with a4jCommand Button / Link / @all
> -----------------------------------------------------------
>
>                 Key: RF-12907
>                 URL: https://issues.jboss.org/browse/RF-12907
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.2.3.Final, 4.3.1
>         Environment: JSF Mojarra 2.1.21 or 2.1.20 - Glassfish or WAS 8.0.0.x 
> Servlet 3.0 or 2.5
>            Reporter: Jean ANDRE
>              Labels: waiting_on_user
>         Attachments: Nested-2.1.Finale.zip, Nested-Spring-3.2.2.zip, 
> NestedEar-CDI.zip
>
>
> Please see the report at: http://java.net/jira/browse/JAVASERVERFACES-2016
> It seems that that there is a problem with a4j button and the value of 
> @form/render attribute.
> The symptom we got is after refreshing the panel for building a list. Click 
> on link form the result lisk does not trigger the action.

--
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
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues

Reply via email to