Also, the thought of backward-compatibility came to mind. owb is said to work for/with Java EE 5 (as well as Java EE 6), so I can already see the backward-compatibility, there.
So, I guess, there should be not many issues/defects in TomEE 1.6.0 snapshot, since owb 1.2 was recently added to the stack. right? :) On Tue, Apr 30, 2013 at 8:30 AM, Howard W. Smith, Jr. < [email protected]> wrote: > Are there many more tomee refactorings required, since owb 1.2 is in the > house? :) > > I just thought about reading, News from OpenWebBeans-1.2.0 [1], and so far > it looks interesting. > > The Apache OpenWebBeans team has been quite busy with big refactorings. > Big improvements have been made to the proxying mechanism, the Bean > scanning and the AnnotatedType handling. We managed to improve the overall > performance again and now deliver almost native Java like performance for > our NormalScoping proxies. > > to read more, click URL below > > [1] http://blogs.apache.org/owb/ > > > On Mon, Apr 29, 2013 at 9:35 AM, Romain Manni-Bucau <[email protected] > > wrote: > >> Hi, >> >> shouldn't change anything for you (that's the goal and still in progress) >> >> *Romain Manni-Bucau* >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* >> *Blog: **http://rmannibucau.wordpress.com/*< >> http://rmannibucau.wordpress.com/> >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* >> *Github: https://github.com/rmannibucau* >> >> >> >> 2013/4/29 Howard W. Smith, Jr. <[email protected]> >> >> > Okay, owb 1.2 is in the house. Can you please clarify what is changing >> with >> > bean manager due to OpenWebBeans (owb) version 1.2 and/or TOMEE-916[1]? >> Any >> > risks, pros, cons, performance enhancements, etc...? >> > >> > I am using bean manager instead of CODI bean manager. that is why I'm >> > asking. :) >> > >> > thanks, >> > Howard >> > >> > [1] https://issues.apache.org/jira/browse/TOMEE-916 >> > >> > >
