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

[Alexandre Lefebvre <alexandre.lefebvre@xxxxxxxxxxxxxxxxxxxx>]

Benjamin,

Please clarify one thing: four days ago (see below) you suggested  
several possibilities for new synergies.

Are you dropping ALL of them?
Will you at least backport eXo's enhancements to PETALS?
Will you at least continue to push ObjectWeb's projects?

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