Re: @FlowScoped, @Named and @ManagedBean
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 :
> 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.pe...@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.
>> |
>>
Re: @FlowScoped, @Named and @ManagedBean
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.pe...@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.
> |
>
Re: Does JSF 2.2 support window scope ?
JSF only provies the ClientWindow because it's used by the faces flow. I would migrate to DeltaSpike. 2014-02-19 16:48 GMT+01:00 Stephen More : > When using JSF 2.1 in order to utilze window scope ( like a session per > window ) I was required to utilize CODI. I now see that JSF 2.2 has some > support for ClientWindow. Can I stop using CODI and utilize the built in > features in 2.2 for session per window or I should I migrate to DeltaSpike > for my window scoping needs ? >
Does JSF 2.2 support window scope ?
When using JSF 2.1 in order to utilze window scope ( like a session per window ) I was required to utilize CODI. I now see that JSF 2.2 has some support for ClientWindow. Can I stop using CODI and utilize the built in features in 2.2 for session per window or I should I migrate to DeltaSpike for my window scoping needs ?
