Question about Seam component properties and it's lifecycle

[bfo81]

We're in a Seam component (e.g. Stateful Session Bean) and it's got the following property:

@In @Out private Whatever property;

From RESTORE_VIEW(1) till the end of PROCESS_VALIDATIONS(3) the property is null.
Then it gets injected before UPDATE_MODEL_VALUES(4) and keeps its state till the end of RENDER_RESPONSE(6).
After that it becomes null again and the whole cycle repeats.

Is this assumption right? :)

I had problems with a method which generated SelectItems. After choosing an item (or items) in a selectMenu the selected values are compared to the SelectItems again in PROCESS_VALIDATION(3) phase. So my method got called twice (before and after selection by the user). But since that method uses an injected value (which was null in (3)) it failed ;).

[gavin.king]

This behavior depends upon the InterceptionType. By the way, this has caused so much problems for users that Seam 1.1 will default to @Intercept(ALWAYS).

[bfo81]

Thanks for the hint, Gavin.

I just read in the reference that the default interception type is INVOKE_APPLICATION. So by default injected components are null from (1) to (4) and thy have their correct value only from (5) to (6).

But it's good that you want to change the default behaviour. btw: any idea when 1.1 will be final? I don't want to know an exact date, but if it's not within the next month I don't have to worry about my current project to be outdated ;).

[gavin.king]

I would love to do a release in late September, but not sure if I can get everything I need to get done done by then. (1.1 was supposed to go out weeks ago.) We'll see.