Tracking bug for all work required to implement module system interoperability as defined by the JSR 277 specification.
Posted Date : 2008-01-15 02:50:24.0

N/A

The current JSR 277 spec does not yet specify the details of module system interoperability.
Posted Date : 2008-01-15 02:50:24.0

Draft Specification for Supporting OSGi Bundles in the Java Module System
   http://openjdk.java.net/projects/modules/osgi-support-draft.html

See more information about OSGi repository prototype at
   http://weblogs.java.net/blog/mandychung/archive/2008/07/osgi_repository.html
Posted Date : 2008-07-24 23:24:55.0

Critical to the success of JSR 277 is its ability to interoperate fully with JSR 291 (OSGi). This interoperation must be supported explicitly in the JSR 277 specification and demonstrated to work in the OpenJDK modules project. Full interoperation with JSR 291 should be taken into account in future ballots of JSR 277.

This is not only important, it is urgent.  OSGi is spreading like wildfire (e.g., Eclipse, IBM, BEA).  Lack of formal, explicit interoperation, if not adoption, is an oversight at best, and neglect at worst.

Interoperability makes it easy for OSGi users and there is a very good user base for OSGi already.

I have been using OSGi for 8 years. I would be disappointed if the new JDK is not complaint with it and redefine it our mechanism.

Interoperability with JSR 291 is very important to prevent the further fragmentation of Java. Only interoperability can guarantee a sufficiently large user base.

OSGi helps solve multiple typical problems for myself especially in a deployment and bundle model, as well as present solutions in its framework service and additional compendium services. Integration should be a foremost effort. 

OSGi has been used in many projects and it is crucial to interoperate with OSGi to support these projects. 

+1

Since JSR 291 has passed it's critical that any potentially overlapping module spec should guarantee interoperability *explicitly* in the spec.  In fact - since JSR 291 passed I would hope 277 explicitly avoids overlap with 291.

This is a must have, OSGi is the future gentlemen, there must be interoperability.

Please move the Java Community forward by specify OSGi interoperability for JSR 277. 

+1

Loads of reasons to drop JSR 277 and revive JSR 291 (OSGI)  are already listed below. The most important for me: I'm doing develpment with OSGI.

+1

I just think it would make sense to provide interoperability

+1. Please include interoperability with JSR -291 as one of the defining characteristics for JSR-277 given that OSGi is being so rapidly gaining ground. I think it would a big win for the Java community. 

OSGi means also 10 years experiences of module based systems. We´re heavily using OSGi and it´s time that JSR 277 will interoperate with something which is already there.

+1. I hope that Sun will think about this bug:) and will stop neglecting OSGi. The interoperability between JSR277 and JSR291 (OSGi) should be one of the key benefits of coming Java7. 
..

Don't even bother if it doesn't interoperate fully with JSR 291 (OSGi).

include osgi

Critical to the success of JSR 277

Please clean up the jumble of module solutions so that we can all start using one and getting work done.

277 has an opportunity to improve on 291, but if in fact it takes us backwards from 291 by not supporting out-of-the-box the many OSGi bundles already in existence, then 277 is pointless.

+1

OSGi is used by all major JEE vendors as a module system, and projects are already building OSGi bundles (like Spring). Without interoperability, JSR277 is going to be a second class citizen and unused.

OSGi is a highly capable module system. Lack of interoperability will severely limit the usefulness of JSR 277.

Pls include OSGI interoperability as part of JSR 277. It seems very promising for the desktop app. as well

since JSR 291 passed I would hope 277 explicitly avoids overlap with 291 

Clean up JSR 291 so that it does not use an incompatible module system.

+1

I view this as extremely important.

+1 for interoperability with JSR 291 (OSGi)

OSGI is getting more and more popular. Now not only in Java ME and SE, but also EE: see Spring Application Platform. That means, OSGI/JSR-291 is already live and successful - there is no point in fighting with it. So 277/294 can be either cancelled completely, or made fully compatible with 291. There is no other choice now.