On Nov 8, 2011, at 5:53 AM, Romain Manni-Bucau wrote: > there are already several classes we could want to extract > > what i don't like with this ejb is it will be exposed to user since it is > loggued and not usable by him
Maybe we need to write in some sort of "hidden" flag and corresponding @Hidden annotation for some of the EJBs we produce. Other ones that come to mind are: - the managedbean we create for testcases - the managedbean we create for the class that bootstrapped the EJBContainer - the "Comp" managedbean we use to hold shared "java:comp/env" names Seems like the real pattern is that we're finding it more and more useful to create EJBs ourselves. Some way to do that without bugging users could be nice. -David
