| Re: [jakartaee-spec-project-leads] osgi.contract Capabilities |
|
We have worked on OSGi issues in Jakarta Transactions before but I don't think we did OSGi contract (at least unless maybe a review was done of something that someone proposed to us maybe). I appreciate you raising the wider topic here, James, because if we
can agree to support OSGi or not at the platform level it could help our project to know what we must do, vs could do (maybe also must not do).
From: jakartaee-spec-project-leads <jakartaee-spec-project-leads-bounces@xxxxxxxxxxx> on behalf of James Perkins via jakartaee-spec-project-leads
<jakartaee-spec-project-leads@xxxxxxxxxxx>
Sent: 27 August 2026 18:31 To: jakartaee-spec-project-leads@xxxxxxxxxxx <jakartaee-spec-project-leads@xxxxxxxxxxx> Cc: James Perkins <jperkins@xxxxxxx> Subject: [EXTERNAL] [jakartaee-spec-project-leads] osgi.contract Capabilities
Hello All,
In the Jakarta REST specification we had an issue filed [1], with corresponding PR's [2][3], about adding better OSGi Contract Capabilities. I'm far from an OSGi expert, but I think for the most part this makes sense to do. Are there any other specifications
that already do something similar?
One question I did have on these specific PR's was with the version list. I'm not sure I understand why that is needed.
James R. Perkins
Software Developer
IBM
Unless otherwise stated above:
IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: Building C, IBM Hursley Office, Hursley Park Road, Winchester, Hampshire SO21 2JN |