[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.technology.ejb-orm] Re: arent there now 2 official EJB3 Projects?

Hi Christian,

As the lead for the other project, I thought it might be good to get my
perspective ;-)

The projects are very much the same with regard to the JSR220 specification.

Further, yes, we are already SWT based.  Yes, we are integrated with the
Eclipse code base making use of  WTP, EMF/RDB, GEF, RCP, RDB, etc.  In fact,
some of our project committers are also committers for the WTP project.
Yes, we are vendor neutral in our implementation.  Yes, we are fully
supporting JSR220 both in J2EE and J2SE environment.   Yes, we do have a
community of other companies involved in the work.  We have a milestone
release due out the week of Aug 8th.

Where we are different is perhaps in the internals of the implementation. We
are implementing the tooling as a framework that will allow vendor JSR220
runtime plug-in with customized extensions for their runtimes and with
extension points for other input and output artifacts in the future like
XML, SDO, etc.  The members of the JSR220-ORM project development team are
not working on those other types of artifacts, but anyone who is so inclined
may easily extend what we are doing.

This question of overlap and working together also came up in the JSR220-ORM
projects Creation Review.  I will tell you the same answer I gave the review
committee.  I think it would be best to have a single project.  We attempted
to participate in an open forum discussion moderated by other companies to
see where we could work together .  I laid out the entire scope of what we
were doing publicaly and suggested ways we could collaborate and to my
disappointment never received even a single response in the open forum or
otherwise.   Not even a response that said, "thank you for your offer, but
we respectfully decline any involvement together".  Instead, we got
absolutely zero response.   Hard to work as a single community towards a
single solution with that level of communication.   So, we continued forward
building our own community and tooling which will be released shortly.

Regards,

Robert Greene
JSR220-ORM Project Lead
rgreene@xxxxxxxxxxx


"Christian Sell" <christian.sell@xxxxxxxxxxxxx> wrote in message
news:08bd344afb788abaacb8c30016122973$1@xxxxxxxxxxxxxxxxxx
> Maybe this is the opportunity to explain what exactly is the difference
> between this project and the jsr220-orm project, which was also accepted
> recently? The only difference I can see is the already contributed code
> and the participants..
>
> thanks,
> Christian
>