> If iPojo and Blueprint are not compatible. What can we do !
> This kind of situation is always frustrating for developers/designers and
> architects because choice must be done between competitors (Spring DM,
> Blueprint, iPojo, SCA, ...).
> Our time is precious. This is why having standards in OSG is really
> important like it is in Java World for J2EE specifications. I'm pretty sure
> that this kind of situation will not help to promote OSGI as alternative to
> classical development done on J2EE application servers like Websphere, ...
>
> Regards,
>
> Charles Moulliard
> Senior Enterprise Architect
> Apache Camel Committer
>
> *****************************
> blog :
http://cmoulliard.blogspot.com>
>
> On Thu, Jul 2, 2009 at 11:59 AM, Guillaume Nodet <
gnodet@...> wrote:
>
>
>> When I first started the blueprint implementation, the idea was to use
>> iPojo and implement blueprint on top of it.
>> Unfortunately, iPojo and blueprint have very different ways of solving
>> the same problems, and it seems quite impossible to easily reconcile
>> those.
>> So, I don't think there will be any relationship between iPojo and
>> blueprint.
>>
>> On Thu, Jul 2, 2009 at 11:19, Charles Moulliard<
cmoulliard@...>
>> wrote:
>>
>>> Hi,
>>>
>>> What are the future plans of iPojo regarding to OSGI specification (= RFC
>>> 124 ) called Blueprint ? Will iPojo be migrated to be used as blueprint
>>> services or iPojo will continue to live without integration with
>>>
>> blueprint ?
>>
>>> Regards,
>>>
>>>
>>> Charles Moulliard
>>> Senior Enterprise Architect
>>> Apache Camel Committer
>>>
>>> *****************************
>>> blog :
http://cmoulliard.blogspot.com>>>
>>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog:
http://gnodet.blogspot.com/>> ------------------------
>> Open Source SOA
>>
http://fusesource.com>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
users-unsubscribe@...
>> For additional commands, e-mail:
users-help@...
>>
>>
>>
>
>