Hi Gurkan! Should we still stick to our approach to split non javaSE parts into plugins? I'd prefer it, but not sure if it is still possible. So since now all 'heavy' parts are done, I could start working on getting the plugins finished.
Also: did you already remove all parts from the 'official' API which have been dropped from the Spec like Observers? Do we like to drop the functionality internally too? :( If not (which I prefer), we should start a new 'owb-internal-api' module. LieGrue, strub --- Gurkan Erdogdu <[email protected]> schrieb am Mo, 8.6.2009: > Von: Gurkan Erdogdu <[email protected]> > Betreff: Development Next Steps > An: [email protected] > Datum: Montag, 8. Juni 2009, 18:53 > Hi guys; > > As you already know, we have succesfully published our M2 > version. Altough a spec changes a lot from the last draft > version, I think we are on the good track. > > In the mean time I have sent June board report. In > this report I stated one point, from report: > > > NOT : Actually, last draft specification imposes on an > implementations > that it must be tightly integrated with a Java EE > Container's internals > , such that integration with an EJB 3.1 Container, Servlet > Container, > Managed Beans etc. So, we have to work closely on the > respective Apache > teams to push the implementation. > > > WDYT about the next items ? How could we proceed? > > Currently, I have been changing OWB API's for obeying to > the current draft specification. Moreover, there are > mainly the following points that have to be implemented as > next > > 1* EJBs > 2* Resources > 3* Bean Provider SPI > 4* Java Servlet, Managed Bean integration > > I will try to integrate OpenEJB with OWB. But this will be > on a collapsed ear level (ejbs can be placed on the war > deployment, ejb3.1 stuff). To real integration with EJBs, we > have to work closely with OpenEJB teams. > > > Thanks; > > --Gurkan > > > >
