[cdi-dev] [VOTE] Name the class that can start/stop contexts

[Matej Novotny]

+1 for ManageableContext

Personally I would still have UnmanagedContext, but since that seems ambiguous (as does ManagedContext),
I chose ManageableContext.

Matej

----- Original Message -----
> From: "John D. Ament" <john.d.ament at gmail.com>
> To: cdi-dev at lists.jboss.org
> Sent: Monday, July 11, 2016 2:50:23 AM
> Subject: [cdi-dev] [VOTE] Name the class that can start/stop contexts
> 
> All,
> 
> It seems like one of the remaining issues with CDI-30 is the name for the
> class for the context management. This name isn't permanent, we can change
> after EDR2, but not after final.
> 
> Here's the proposed renames for "UnmanagedContext":
> 
> - ManagedContext
> - ManageableContext
> - ProgrammaticContext
> - ExternallyManagedContext
> - UserManagedContext
> 
> Please respond back with your vote, I'll leave this open for 3 days ( I
> believe its Monday morning in central Europe), so I'll close it Thursday
> morning.
> 
> Reference:
> http://transcripts.jboss.org/meeting/irc.freenode.org/cdi-dev/2016/cdi-dev.2016-07-07-16.03.log.html
> 
> - John
> 
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
> 
> Note that for all code provided on this list, the provider licenses the code
> under the Apache License, Version 2
> (http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas
> provided on this list, the provider waives all patent and other intellectual
> property rights inherent in such information.