The @ManagedBean from EE6 was added in the last seconds before the EE6 umbrella spec got
finished. Long after all the other specs went final. There is just no use for it. No other
spec ever uses it. Plus the visibility and detection rules just clash with the rules of
the other specs.
When do some specs finally end up adding prospect functionality which is of no use?
*bangshisheadonthedesk*
EE @ManagedBean is just fu**** up s***t
LieGrue,
strub
----- Original Message -----
From: Hantsy Bai <hantsy(a)gmail.com>
To: cdi-dev(a)lists.jboss.org
Cc:
Sent: Tuesday, April 24, 2012 10:02 AM
Subject: [cdi-dev] How to process the @ManagedBean from JEE and CDI managed bean.
Hi,
In java EE 6, there is a ManagedBean spec in the core, but it is not a
standalone spec, @ManagedBean has basic lifecyle, @Predestroy
@Postconstrcut...
As a developer, I hope all Container managed beans(JSF managed bean,
EJB, MDB, WS etc) are refined from this ManagedBean, including CDI Bean.
Thus we it seems smooth to developer like like Spring framework
provided...
Regards
Hantsy
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev