Yup. it is good idea to have separate project for jsf related codes. In the mean time, we have to work on to create M2 release :)
Requirements for next steps M3, M4, M5 release ------------------------------------------- We have to implement all of the specs with exception * XML definition * Interceptor and Decorator definition * EJB definition Because these topics are uncertain and that they can be carried to the other specifications. M2 Content ------------------------------------------ I will send a detailed information about the M2 release content and dates in a couple of days. Please you also think about what can be go inside into the M2 release. Thanks; Gurkan ________________________________ From: Mark Struberg <[email protected]> To: [email protected]; [email protected] Sent: Saturday, April 18, 2009 1:40:50 AM Subject: AW: OWB modularisation I now also fixed a few issues in the guess sample: .) workaround for OWB-90 .) add dependency to openwebbeans-jsf .) improved logging in the PluginLoader LieGrue, strub --- [email protected] <[email protected]> schrieb am Fr, 17.4.2009: > Von: [email protected] <[email protected]> > Betreff: OWB modularisation > An: [email protected] > Datum: Freitag, 17. April 2009, 22:56 > > Hi folks! > > Today ran very well - I finally got enough power to > introduce a plugin mechanism for OpenWebBeans. > > So webbeans-impl doesn't contain any JSF specific code > anymore! > All this has been moved over a special webbeans-jsf module. > > The mechanism uses the java.util.ServiceLoader > functionality. So adding a now plugin is easy: simply drop > the JAR into the classpath ;) > > Please take a glimpse at > > http://ns1.backwork.net/git/openwebbeans.git > > > If there re no objections on how I implemented it, then > I'll check this into SVN tomorrow morning! > > LieGrue, > strub > > > > >
