-
1. Re: a4j:ajax CDI render issue
rhanus Mar 29, 2013 7:56 AM (in response to jblbecarelli)you define conversation scope but you did'nt start that scope so that your statefull bean is not connected with http session in no way
your last scenario works because view scoped managed beans are available untill you navigate to another facelet
moreover using ejb statefull beans if you don't use transactions, persistence, caching, ... has no effect, they are usually used only in specific use cases, for instance jpa extended persistence context
last but no least don't mix jsf managed beans with cdi beans, see this great article for details
-
2. Re: a4j:ajax CDI render issue
jblbecarelli Mar 29, 2013 9:49 PM (in response to rhanus)Please give me the link to the article, i will read it with interest.
I have cdi beans because i try to work with CRUD application generated from forge UI scaffold (the bean that you see is a semplificated bean only for example) and @Stateful
@ConversationScoped CDI bean is the bean that forge create for manage an entity.
Please can you give me more detail of what you mean when you say "you define conversation scope but you did'nt start that scope so that your statefull bean is not connected with http session in no way"?
Thanks for all.
Luca
-
3. Re: a4j:ajax CDI render issue
rhanus Mar 30, 2013 6:37 PM (in response to jblbecarelli)1 of 1 people found this helpfulsorry the link is missing, the article is here
Please can you give me more detail of what you mean when you say "you define conversation scope but you did'nt start that scope so that your statefull bean is not connected with http session in no way"?
see weld reference guide chapter 5.3
note both conversation.begin() and conversation.end() calls in conversation demarcation sample