OSGi DevCon Europe: Keynote

Keynote

Detailed description on what's going to be available in next releases (Core, Compendium and Enterprise).

Launching:

Need for a standardized launching system
Allows to embed easily the framework in your application
Using the service system of Java 5 (META-INF/services)

Service Hooks

Allows to listen service access events, therefore allowing interception for example.
FindHook, EventHook and ListenerHook.

Negative Permissions

Java 2 permissions: Very heavy to enumerate explicitely what is authorized and skip what is not.
Adding DENY and ALLOW. This is very nice! If it could just be implemented this way in Java 2 permissions...

Remote Services

RFC 119 (Formerly Distributed OSGi)
Remote access to OSGi services, protocol-independent.

Blueprint extender

RFC124
Provides Spring DM-like Functionality
Provides Service damping (wait until service is available) which is a very nice feature!
Defined through XML, a Blueprint container retrieves Metadata for Beans, Services, and References, and then creates corresponding elements from these metadatas.

Enterprise release

Transactions, JDBC, JMX, JNDI, JPA, Connectors

Experimental

TSL Tiny script language
Uses reflection but simplifies syntax (no new commands)
Sounds fun!

Nested frameworks

Application servers need an application model
in OSGi: Application==set of installed bundles
Compromise: frameworks should be nested

Java Modularity

module keyword would be nice for OSGi
The rest is over simplistic and will probably introduce more issues than it will solve... and BTW, it will only be available in Java 7 (why a language feature for that????)

BTW First time I hear a dog barking in a conference ;);)