Hi Martin,
great to hear from you again after quite some time of silence :-)
Some month ago Werner, Bruce, Gregory and myself had a discussion on IRC
about futur direction of CastorJDO. We all agreed that we first need to
resolve some of the known bugs and limitations as well as add some
frequently requested features like polymorphism. As we have added the
most important features we are now working toward 1.0 release. But still
there are quite some more issues to resolve where you could help us with
;-) .
As our long term target for CastorJDO Bruce voted to work on getting
compliant to JDO standard, while Werner, Gregory and myself were in
favour of EJB 3.0 compliance. Still nothing is decided yet and need to
be discussed once again.
At the moment we are still trying to resolve more bugs and add more
features. In addition we improve our codebase with lots of refactorings,
by checkstyle our code and by adding more test cases. With this targets
we hope to be able to prepare a 1.0 release until end of the year.
Regards
Ralf
Martin Fuchs schrieb:
Hello,
this may not be closely related to Castor, but let's see what your
opinion is on this topic: Recently there has been released the EJB 3.0
specification draft.
I didn't yet look deeper at the proposed specification.
But reading for example the section "EJB QL" at
http://www.javaworld.com/javaworld/jw-08-2004/jw-0809-ejb_p.html
one can ask himself, whether this won't supersede Castor OQL.
Will there be some co-existence of Castor and this newer, reading
easier than ever
method for object persistence using Java 1.5 annotations?
May be Castor XML might be made compatible to EJB, so Castor OQL can
be replaced, while still providing the "XML <-> Java Object <-> SQL"
connection, which is currently the thing, which makes Castor unique
above other persistence libraries?
Regards,
Martin
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
