Hi Gang,
I am currently testing the our implementation against the JSR-299 TCK.
Currently, our implementation is passed 210 tests of the total 381 TCK
standalone tests :) I am hardly working on the TCK compatibility. I really want
that in the end of this month, we are able to release our M2 release with
passing all TCK tests.
Belows are the remaining parts of the specification that we did not touch or
implement partly.
1* EJB Beans support --> Not implemented
2* XML implementation --> we have implemented partly, but needs more work!
3* Context passivation/activation --> Not implemented, and how we decide to
passivate or activate beans ? (Maybe requires Java EE container support)
4* Resource injections (Common annotations resources, JMS resources, JPA
resources etc.) --> Mark is working on the JPA injections
5* Asynhronous JMS event support --> Not implemented
Lastly we talked with the Mark, we decided to implement the Java EE parts (EJB
and JMS) as seperate maven modules from the implementation. So anyone is able
to use our implementation without owning a Java EE container,( Use in Tomcat,
Jetty or other web container). Also I really like to support the OpenWebBeans
in Java SE environment. To this happen, I have changed discovery mechanism of
the project. Now, anyone can add its own discovery mechanism. I have
implemented Java SE and WAR deployment mechanisms so far. Default is the WAR
deployment. (Currently this depends on the javassist!)
Mark, what are you working on currently? As I remembered from last
conversations, you created the ejb maven module to integrate JPA stuffs. Can
you commit this? Or it needs more work. I also want to integrate EJB and JMS
stuff this week. So if you have created the EJB maven modules, please commit it
and I am able to start on working on the Java EE stuffs.
WDYT guys about our current situation? Any advice, comment ? All of them are
welcome :)
Thanks;
/Gurkan
