[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [libra-dev] OSGi Enterprise 4.3 Specification Early Access Draft available

Shame, but thanks for the clarification!

Regards,
Glyn

On 27 Jun 2011, at 10:20, Raev, Kaloyan wrote:

Well, Libra will rely on WTP Server Adapter framework for deploying artifacts to OSGi application servers. So, it is up to the Virgo server adapter if will support deployment of OSGi Enterprise artifacts as defined by Libra.
 
We plan to implement a Generic OSGi Server Adapter that will demonstrate how server adapters can deploy Libra artifacts. Hopefully, the Virgo tools will be able to directly use or extend parts of this generic server adapter.
 
Greetings,
Kaloyan
 
From: libra-dev-bounces@xxxxxxxxxxx [mailto:libra-dev-bounces@xxxxxxxxxxx] On Behalf Of Glyn Normington
Sent: 27 юни 2011 г. 12:10 ч.
To: Libra developers list
Subject: Re: [libra-dev] OSGi Enterprise 4.3 Specification Early Access Draft available
 
Right.
 
Will Libra eventually be able to launch Virgo and deploy/redeploy artefacts to it? One use case is to use Virgo to develop OSGi standard artifacts and in this use case one wouldn't really need the Virgo tooling.
 
Regards,
Glyn
 
On 27 Jun 2011, at 10:09, Raev, Kaloyan wrote:


OK, I see. I did not know that Virgo PARs are not exactly the same as the subsystems described in RFC 152 (to be honest, I am just about to start reading the RFC).
In this case, it really makes sense to first implement the RFC 152 tooling in Libra and then Virgo Tools to adopt them and extend.
 
Greetings,
Kaloyan
 
From: libra-dev-bounces@xxxxxxxxxxx [mailto:libra-dev-bounces@xxxxxxxxxxx] On Behalf Of Glyn Normington
Sent: 27 юни 2011 г. 12:04 ч.
To: Libra developers list
Subject: Re: [libra-dev] OSGi Enterprise 4.3 Specification Early Access Draft available
 
I agree, except that the Virgo tooling does not yet support RFC 152 artefacts (although these are similar to plans and PARs) so you have to look quite deeply to see the generic parts.
 
(In time, Libra should have all the OSGi standard tooling and the Virgo tooling should just add the Virgo specifics to Libra. This will take quite a bit of work to achieve however.)
 
Regards,
Glyn
 
On 27 Jun 2011, at 09:57, Raev, Kaloyan wrote:



Hi Glyn,
 
This is great news. Then I think it would make sense to take the generic part of the Virgo Tools that fit in RFC 152 and move it to Libra. This would be a great contribution.
 
Greetings,
Kaloyan
 
From: libra-dev-bounces@xxxxxxxxxxx [mailto:libra-dev-bounces@xxxxxxxxxxx] On Behalf Of Glyn Normington
Sent: 27 юни 2011 г. 11:53 ч.
To: Libra developers list
Subject: Re: [libra-dev] OSGi Enterprise 4.3 Specification Early Access Draft available
 
RFC 152 has had input from Virgo's plan construct and I hope that Virgo will implement RFC 152 in due course.
 
Regards,
Glyn
 
On 27 Jun 2011, at 07:58, Raev, Kaloyan wrote:




Hi,
 
A draft for the OSGi Enterprise 4.3 specification was released a few weeks ago. It’s targeted for final release for first half of 2012 – sounds like aligned with Juno J.
I am most excited of RFC 152, which will define OSGi Applications.
 
There is a very short overview available on this blog:
 
Link to the draft document:
 
Greetings,
Kaloyan Raev | T +359 2 9157-416
SAP Labs Bulgaria | PO OnDemand Platform Convergence
 
_______________________________________________
libra-dev mailing list
libra-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/libra-dev
 
_______________________________________________
libra-dev mailing list
libra-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/libra-dev
 
_______________________________________________
libra-dev mailing list
libra-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/libra-dev
 
_______________________________________________
libra-dev mailing list
libra-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/libra-dev