You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Gerhard Petracek (JIRA)" <de...@myfaces.apache.org> on 2011/07/04 10:34:22 UTC
[jira] [Commented] (EXTCDI-172) sub-groups for conversation groups
[ https://issues.apache.org/jira/browse/EXTCDI-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059357#comment-13059357 ]
Gerhard Petracek commented on EXTCDI-172:
-----------------------------------------
we could provide something like:
public class MyGroup{}
@ConversationScoped
@ConversationGroup(MyGroup.class)
public class BeanA {}
@ConversationScoped
@ConversationGroup(MyGroup.class)
public class BeanB {}
@ConversationScoped
@ConversationGroup(MyGroup.class)
public class BeanC {}
@ConversationSubGroup({BeanA.class, BeanB.class})
public class MySubGroup extends MyGroup {}
//...
this.windowContext.closeConversation(MySubGroup.class)
//...
-> only BeanA and BeanB will be un-scoped. the conversation as well as BeanC will continue to exist.
> sub-groups for conversation groups
> ----------------------------------
>
> Key: EXTCDI-172
> URL: https://issues.apache.org/jira/browse/EXTCDI-172
> Project: MyFaces CODI
> Issue Type: New Feature
> Components: JEE-JSF12-Module, JEE-JSF20-Module
> Affects Versions: 1.0.0
> Reporter: Gerhard Petracek
> Priority: Minor
> Fix For: 1.0.1
>
>
> it should be possible to use sub-groups of conversation groups to allow an even more fine grained control.
> since it's a completely new concept we have to design it from scratch and check it it makes sense to introduce the overhead.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Commented] (EXTCDI-172) sub-groups for conversation groups
Posted by Werner Punz <we...@gmail.com>.
Jepp makes a lot of sense
Am 04.07.11 10:34, schrieb Gerhard Petracek (JIRA):
>
> [ https://issues.apache.org/jira/browse/EXTCDI-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059357#comment-13059357 ]
>
> Gerhard Petracek commented on EXTCDI-172:
> -----------------------------------------
>
> we could provide something like:
>
> public class MyGroup{}
>
> @ConversationScoped
> @ConversationGroup(MyGroup.class)
> public class BeanA {}
>
> @ConversationScoped
> @ConversationGroup(MyGroup.class)
> public class BeanB {}
>
> @ConversationScoped
> @ConversationGroup(MyGroup.class)
> public class BeanC {}
>
> @ConversationSubGroup({BeanA.class, BeanB.class})
> public class MySubGroup extends MyGroup {}
>
> //...
> this.windowContext.closeConversation(MySubGroup.class)
> //...
>
> -> only BeanA and BeanB will be un-scoped. the conversation as well as BeanC will continue to exist.
>
>> sub-groups for conversation groups
>> ----------------------------------
>>
>> Key: EXTCDI-172
>> URL: https://issues.apache.org/jira/browse/EXTCDI-172
>> Project: MyFaces CODI
>> Issue Type: New Feature
>> Components: JEE-JSF12-Module, JEE-JSF20-Module
>> Affects Versions: 1.0.0
>> Reporter: Gerhard Petracek
>> Priority: Minor
>> Fix For: 1.0.1
>>
>>
>> it should be possible to use sub-groups of conversation groups to allow an even more fine grained control.
>> since it's a completely new concept we have to design it from scratch and check it it makes sense to introduce the overhead.
>
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>