-
1. Re: Seam Managed Persistence Context in WebBeans
pmuir Apr 6, 2009 3:18 PM (in response to hajdi)I haven't got detailed plans, but we will certainly implement the SMPC for Web Beans.
BTW the spec doesn't actually say that the conversation context must not be active during non-JSF invocations, just that it is not active by default then.
-
2. Re: Seam Managed Persistence Context in WebBeans
hajdi Apr 6, 2009 4:09 PM (in response to hajdi)So possible WebBeans based SMPC implementation has the potential to be unportable to different JEE6 servers then. That would be pity.
I am wondering whether SMPC is the right solution for non-JSF based invocation at all. What do you think? I like SMPCs in JSF driven conversational components and would like to keep using them everywhere else. Especially that such non-JSF invocated components are often also used by conversation components and should share same SMPC. In Seam this issue stops me from doing this and in WebBeans/JEE6 it has the potential to be not portable. Am I missing something here?
BTW. No body responded to this issue. Is it really a bug? It seems strange to me that such a major problem exists in Seam SMPC for so long time. Do you think that solution provided in thread can be considered a fix?
-
3. Re: Seam Managed Persistence Context in WebBeans
pmuir Apr 7, 2009 2:56 PM (in response to hajdi)
Rafal Hajdacki wrote on Apr 06, 2009 16:09:
So possible WebBeans based SMPC implementation has the potential to be unportable to different JEE6 servers then. That would be pity.Whilst it may have that potential, we will design it so this limitation doesn't exist.
I am wondering whether SMPC is the right solution for non-JSF based invocation at all. What do you think? I like SMPCs in JSF driven conversational components and would like to keep using them everywhere else. Especially that such non-JSF invocated components are often also used by conversation components and should share same SMPC. In Seam this issue stops me from doing this and in WebBeans/JEE6 it has the potential to be not portable. Am I missing something here?
I would still use an SMPC - the Seam 3 SMPC will be portable, despite your fears :-).
BTW. No body responded to this issue. Is it really a bug? It seems strange to me that such a major problem exists in Seam SMPC for so long time. Do you think that solution provided in thread can be considered a fix?
The issue is scheduled for Seam 2.2.0 - that seems like a response to me :-) File a patch, we can look sooner then.
-
4. Re: Seam Managed Persistence Context in WebBeans
gonorrhea Apr 14, 2009 1:06 AM (in response to hajdi)
Pete Muir wrote on Apr 06, 2009 15:18:
I haven't got detailed plans, but we will certainly implement the SMPC for Web Beans.would you rather call it WBMPC?
-
5. Re: Seam Managed Persistence Context in WebBeans
nickarls Apr 14, 2009 1:36 PM (in response to hajdi)JCDIMPC, better known as J5C ;-)