Re: [college] Re: Two JBI implementations in ObjectWeb - open discussion

[Benjamin Mestrallet <benjamin.mestrallet@xxxxxxx>]

Hi Alex let me answer point by point

> Please clarify one thing: four days ago (see below) you suggested  
> several possibilities for new synergies.
> Are you dropping ALL of them?

We are not leaving the JBI/ESB scope that we just entered and will  
leverage our expertise (from FossilEC) in that scope but with a  
different strategy that also fit OW goals in coordination with the  
ESBi initiative.

We will not allocate any resource on the JBI implementation but we  
will reallocate those on the JBI monitoring and admin space that is  
what what we call eXo ESB will become: a bundle with a JBI container,  
an ESB and many admin and monitoring portlets. Ideally that would be  
with PETALS and Celtix, hoping that those will work together too (or  
at least one will bundle the other).

> Will you at least backport eXo's enhancements to PETALS?

We will not, but the code is available if EBM wants it it can be  
taken and distributed under LGPL, but as there are now some 5 people  
dedicated and some commits to come I am not sure those enhancements  
are still enhancements :)

> Will you at least continue to push ObjectWeb's projects?

We will be pragmatic and faithful to OW project as we always did but  
if we see that Petals developments are not fast enough we will have  
no choice than using ServiceMix, but understand me well, that would  
be the option we would prefer not to take!

In january, we took the decision to have our own implementation  
because we though the JBI impl was not fast enough at that time and  
we wanted to leverage our on architecture (not Fractal based) to  
quickly come with a JBI/ESB admin and monitoring portal (thanks to  
the auto-wiring of our components in the portal that could be done  
quite quickly).

Now I am pleased that Petals will get more commits and will be  
pleased to bundle it with the monitoring portal. If it goes that way  
then we don't need to have a JBI container with our own architecture  
as we don't need to allocate resources to develop it (...and to  
purchase the TCK which is quite expensive btw...) and we can now  
focus on JBI Portlets which was our main target...

Of course when interacting with petals code (as well as servicemix  
and celtix when we test them from the monitoring portal) we will have  
resources to test and we will submit bugs and probably patches to the  
respective communities.

HTH

Benjamin


> Thanks,
>
>     alex, confused
>
> On 14 Apr 2006, at 17:58, Benjamin Mestrallet wrote:
> > Hi all
> >
> > After listening to the people opinions and position of ObjectWeb  
> > college and board, we have decided not to continue our efforts to  
> > implement a JBI container and to focus our activity in the JBI/ESB  
> > monitoring space thanks to portal advanced functionalities to  
> > leverage both our Portal and JBI expertise.
> >
> > We will now develop only portlets in our exo-esb/ module in exo  
> > SVN source code and will leverage existing JBI containers as well  
> > as ESB. We will test those on several implementations like Petals  
> > and ServiceMix. We will continue the development of those portlet  
> > based on our current JBI container implementation until we have  
> > reached the limit of it from a monitoring perspective. We will  
> > then move to another implementation hoping that at that time  
> > Petals will be ready.
> >
> > Kind regards
> >
> > Benjamin Mestrallet
>
>
> On 10 Apr 2006, at 18:02, Benjamin Mestrallet wrote:
>
> > Hi
>
> > ...
>
> > So here is my suggestion to try to find new synergies:
> >
> > - eXo backport its enhancements to PETALS code which means that  
> > the exo-platform in JVM service container is used as the basis for  
> > the new JBI works (note that the code of the core platform of eXo  
> > is licensed as LGP which would not break the current licensing of  
> > petals).
> > - eXo replaces FossilEC as co lead of PETALS with Rafael Marins as  
> > project admin
> > - eXo will provide its APS-EAI layer based on PETALS and code like  
> > monitoring/managing portlets will remain in eXo SVN
> > - eXo continues to push OW members/projects to use in priority or  
> > at least test on the OW JBI container