[prev in list] [next in list] [prev in thread] [next in thread] 

List:       myfaces-user
Subject:    Re: @FlowScoped, @Named and @ManagedBean
From:       Ludovic_Pénet <l.penet () senat ! fr>
Date:       2014-02-20 8:33:23
Message-ID: c8a2ba1e-1609-4e92-8f75-ebfbd8fcee22 () email ! android ! com
[Download RAW message or body]


Thank you.

I guess many users would have the same problem, given that this is the case in Oracle \
JEE7 tutorial : http://docs.oracle.com/javaee/7/tutorial/doc/jsf-configure003.htm

Thanks again, lots of users of proprietary products will be jealous of such quick \
fixes. :)

Ludoviv

On 20 février 2014 03:01:17 UTC+01:00, Leonardo Uribe <lu4242@gmail.com> wrote:
> Hi
> 
> I also did some changes in the navigation to deal with the case when
> the nodeId has the same name as the flow in:
> 
> https://issues.apache.org/jira/browse/MYFACES-3859
> 
> Please note in a normal case click to enter into a flow twice (enter
> into a flow, navigate and try to enter into the same flow again) cause
> get out of the flow and enter into the flow again, which is expected.
> But in this case, the resulting flow will not have that behavior and
> instead the navigation goes to the node identified as start node
> without exit from the flow.
> 
> regards,
> 
> Leonardo Uribe
> 
> 2014-02-19 20:05 GMT-05:00 Leonardo Uribe <lu4242@gmail.com>:
> > Hi
> > 
> > I forgot to say what's wrong in the xml file is define the start
> node.
> > I have created and fixed this issue on:
> > 
> > https://issues.apache.org/jira/browse/MYFACES-3858
> > 
> > regards,
> > 
> > Leonardo Uribe
> > 
> > 
> > 2014-02-13 13:12 GMT-05:00 l.penet@senat.fr <l.penet@senat.fr>:
> > > On 13/02/2014 19:01, Leonardo Uribe wrote:
> > > > 
> > > > Hi
> > > > 
> > > > Thanks for the example. It helps to clarify the problem. The
> > > > definition of the flow has a problem:
> > > > 
> > > > @Produces
> > > > @FlowDefinition
> > > > public Flow defineFlow(@FlowBuilderParameter FlowBuilder
> flowBuilder)
> > > > {
> > > > String flowId = "flux";
> > > > flowBuilder.id("", flowId);
> > > > flowBuilder.viewNode(flowId,
> > > > "/" + flowId + "/" + flowId + ".xhtml").
> > > > markAsStartNode();
> > > > /*        flowBuilder.returnNode("returnFromFlux").
> > > > fromOutcome("#{flowScopedBean.return}");*/
> > > > 
> > > > return flowBuilder.getFlow();
> > > > }
> > > > 
> > > > In this part:
> > > > 
> > > > flowBuilder.viewNode(flowId,
> > > > "/" + flowId + "/" + flowId + ".xhtml").
> > > > markAsStartNode();
> > > > 
> > > > you are using the flow id as a viewNodeId. That confuses the
> > > > navigation algorithm because the spec says that an outcome can be a
> > > > flowId, and in that sense a flowId is a global identifier that
> cannot
> > > > be reused. The fix is just set another id:
> > > > 
> > > > flowBuilder.viewNode("start",
> > > > "/" + flowId + "/" + flowId + ".xhtml").
> > > > markAsStartNode();
> > > > 
> > > > The example only requires some small changes in FlowScopedBean and
> that's
> > > > it.
> > > 
> > > ok for this one, I will try it tomorrow. And can you tell me what
> was wrong
> > > with XML file (or the empty XML file) ?
> > > 
> > > Thank you,
> > > 
> > > 
> > > Ludovic
> > > > 
> > > > AVANT D'IMPRIMER, PENSEZ A L'ENVIRONNEMENT.
> > > > 
> > > 

-- 
Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.
> 
> AVANT D'IMPRIMER, PENSEZ A L'ENVIRONNEMENT.
> 



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic