null injected values

[andreigh.ts]

I am inside a long running conversation and I have a search page with a search button that triggers myBean.search().
myBean has several conversation scoped variables, injected with @In.

While the search page is rendered in the browser, before the render finishes, I click the search button that calls method myBean.search() on server.
The problem is that injected values are null.

Is this a bug? Or is there a configuration to avoid it?

[chrismalan]

These conversation scoped variables you are injecting should have non null objects backing them. They should be outjected from one of your action beans (session beans). Create a @Factory method in the relevant bean where you outject them to make sure they don't have null values. When you then inject them somewhere else they won't have null values.

[andreigh.ts]

I am outjecting them alright, on the conversation scope. Normally they have not null values when injecting them.

The problem only occurs when I call bean method(by clicking a button), BEFORE the page that contains that button finishes to render in the browser.

I guess it is a sort of multithreaded/synchronization bug in seam...

[andreigh.ts]

I cannot find a JIRA issue about this?
Should I raise one? Can anybody confirm is a bug?

[andreigh.ts]

JIRA issue raised:
http://jira.jboss.com/jira/browse/JBSEAM-2242

[andreigh.ts]

Hi, can you recommend a workaround, someting...

We cannot go live with this bug!

Please give some advice. Thanks.

[kukeltje]

Maybe you could disable the buttons by default and use some javascript to enable them at the 'onLoad' event