Accessing a different conversation context

[fabboco]

Hi,

I urgently need your help.

Suppose that I have two different conversation:

Conv1 & Conv2

in which contexts there are two variables (let say v1) that can have different values.

I am in a statefull bean method binded to Conv2 and I would read the v1 variable into Conv1.

I have tried the following code:

Manager.instance().switchConversation(Conv1Id);

System.out.println("Current conversation id "+Manager.instance().getCurrentConversationId());

V1 v1 = Contexts.getConversationContext().get("v1");

Manager.instance().switchConversation(Conv2Id);

but v1 is always the value into Conv2 even thought the current conversation id seams has been switched.

Where I am wrong ?

Please help me

Thank you very much indeed.

Regards

Fab.

[pmuir]

I've never done this so don't quite know how it would work, but it looks like it should do. Grab a copy of the Seam source and step through and check that the conversation context is referencing the right conversation entry.

[fabboco]

Pete,

thank you for your advice.

I have two different scenarios (I have not been able to understand what is the difference yet) one works and the other doesn't.

Following the seam code I was able to show that the difference is the get(String) behavior of ServerConversationContext.

When I am able to get the right value, result is null for

Object result = additions.get(name);

when I am not, result is not null.

What's happening ?

Can you give me any advice since my code causes this different behavior ?

Thank you again.

Fab.

[fabboco]

Sorry,

I forgot: SEAM CR3.

Fab.

[pmuir]

Post the two different scenarios.

[fabboco]

Pete,

scenarios belongs to a real application and they are too complex for the purpose.

As soon as I have time I have to build two simpler test case,

Meanwhile can you tell me what additions are, so that I can try to figure which is the problem ?

Thanks

Fab.

[pmuir]

Additions is a map of objects added to the conversation context in this request.

[pmuir]

Flush the conversation before switching it - Contexts.getConversationContext().flush();

[fabboco]

Pete,

thank you very much.

Flushing seams to be the solution in all my scenarios.

Regards

Fab.