Hi Cristiano, Aries is aware of the RFC 201 work proceeding in OSGi. It's difficult to give an overall assessment since the RFC is so eclectic. Some of the line items, such as 5.6 and 5.7, are quite easy. Some are medium like 5.5. Others would be quite hard, such as 5.8 and 5.9. A technical solution has yet to be offered for 3.9.
We can always discuss our own solutions for our own users separately, of course. If I understand your issue, you would like to be able to export one or more services from your subsystem. This can be done today using a composite, but I assume you do not wish to lose the convenience of the computed application headers. John > > RFC 201 - Subsystems Update ? > > Hello, > > Today I was passing by the OSGi github repository [1] just to be aware > of the next changes and saw something very interesting to me. > I passed some weeks playing with Aries Subsystem. I enjoy it a lot but > unfortunately in our current customer project I couldn't use it because > I couldn't expose a remote service to communicate two isolated applications. > > But the item 3.9 in this RFC 201 aims to deal with this and there are > others missing feature. It is not final, though. > > Would like to know if any of the Subsystem commiters took a look on this > update. > it is possible to imagine how hard would be to implement it ? > > thanks and regards, > > Cristiano > > > [1] - https://github.com/osgi/design/tree/master/rfcs/rfc0201 >
