Outject variable in conversation scope not being set in the context

[gjeudy]

Hi,

I have a very specific example where I use 2 instances of the same SFSB in the same conversation. The bean is declared as follows:

@Stateful(mappedName="RefDomRelateInstancesAction")

@Scope(ScopeType.CONVERSATION)

@Name("domRelateInstancesAction")

@Conversational

@Local(RefDomRelateInstancesAction.class)

@Role(name="domRelateInstancesAction2")

variable myvar is injected/outjected in the following manner:

@In(required=false, create=true)

     @Out(required=false)

     private List<DomainInstanceVO> myvar;

my facelets page refer to the bean using name domRelateInstancesAction and set/outject myvar to Conversation context with a certain value. This works normally.

Later on, another facelets page refer to the bean using name domRelateInstancesAction2 (this instantiates a new SFSB), the existing myvar is injected to that new SFSB instance since it participates in the same conversation. That new SFSB instance modified myvar and outjected to the conversation successfully, I can tell by debugging in the BijectionInterceptor. However, if I refer to

#{myvariable}

in my facelets page I still see the old values set by the initial SFSB instance. Triggering the Seam debug page at this point confirms this.

I can provide more details about my usecase if needed. I don't understand why the old values somehow overwrote the ones set by the new instance. Anyone got tips on how I could troubleshoot this issue ?

From my understanding injection/outjection occurs on every method invocation of a seam component, once instance 2 set the new myvar I can't see how the old values would popup again because it would require a subsequent call to instance1 to trigger bijection but then instance1 should get the modified myvar that was outjected previously by instance 2. Therefore I don't believe it is possible.

Is there anything specific to the bijection algorithm that could make what I've seen happen ?

Thanks,

[barbacena]

I couldn't understand.
Post your full code and facelets page.

[meetoblivion]

I think the biggest question is, what exactly is #{myvariable} ?  Is it a factory tied to the first instance? or something else?

[gjeudy]

Apologies the original post was unclear:

#{myvariable} is in fact #{myvar}

Which means it is bijected as specified in the code sample above. myvar should not be tied to any instance, it doesn't have an explicit scope so should be tied to the Conversation context as specified in the bean declaration. myvar is not populated by a factory method, its first populated when an action method is called on the bean.

[pmuir]

You are correct in how you think it should work - use your debugger to try to find out what is going on.

[gjeudy]

I decided to abandon this issue as I found a better way of reusing an SLSB simply by creating concurrent nested conversations. I think that is probably the cleanest way to proceed in my case as I cannot say the role is semantically different from 1 use to the other of this SLSB.

I would use @Role if really the usage purpose was different. This shows if you can easily come up with a different meaningful name for your role which I could not in this example.