|Re: [libra-dev] OSGi Enterprise 4.3 Specification Early Access Draft available|
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.
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.)
On 27 Jun 2011, at 09:57, Raev, Kaloyan wrote:
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.
RFC 152 has had input from Virgo's plan construct and I hope that Virgo will implement RFC 152 in due course.
On 27 Jun 2011, at 07:58, Raev, Kaloyan wrote:
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:
Kaloyan Raev | T +359 2 9157-416