[cdi-dev] Would @PostActivate, @PrePassivate and @Remove make sense in JSR 250 ?
antonio.goncalves at gmail.com
Sun Dec 28 07:38:37 EST 2014
I was playing with @SessionScoped beans... and wondered if @PostActivate,
@PrePassivate and @Remove would make sense in JSR 250 ?
At the moment these annotations belong to the javax.ejb package and are
only used in @Stateful EJBs. With CDI scopes, we end up with a few
"stateful" scopes (@SessionScoped, but also @ConversationScoped,
@ViewScoped...) so why not having the same functionality in CDI ?
@PreDestroy and @PostConstruct are already part of JSR 250. So why not
having @PostActivate and @PrePassivate as well so they could be used in
every bean ?
BTW, while I was playing with @SessionScoped beans, I asked Antoine to show
me how to remove a bean from the session. It's only a few lines of code,
but again, why not having a @Remove annotation that does that (the exact
same one of javax.ejb.Remove) ?
To summarize, why not taking some of those stateful EJB concerns back to
JSR 250 so they could be used anywhere ?
Any thoughts ?
Software architect, Java Champion and Pluralsight author
Web site <http://www.antoniogoncalves.org> | Twitter
<http://twitter.com/agoncal> | LinkedIn <http://www.linkedin.com/in/agoncal> |
<http://pluralsight.com/training/Authors/Details/antonio-goncalves> | Paris
JUG <http://www.parisjug.org> | Devoxx France <http://www.devoxx.fr>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cdi-dev