I had some thoughts on that Osgi serialization issue.
If Osgi would disallow to place one and the same class name in different
bundles (even just by convention) it would be always possible to find
the proper bundle for an input data stream.
Class name + version (or serialId) would uniquely identify the class to
be loaded. To add the bundle name to the stream does work but is somehow
strange to me.
Having the same interface placed in different bundles seem to me quite
mysterious. For the osgi framework interface package you could use for
instance:
the felix bundle:
<groupId>org.apache.felix</groupId>
<artifactId>org.osgi.core</artifactId>
<version>1.4.0</version>
or
the osgi bundle:
<groupId>org.osgi</groupId>
<artifactId>org.osgi.core</artifactId>
<version>4.2.0</version>
What for is this good? In my opinion there should be only one
distribution bundle of an interface. This possibly would make also
serialization easier?
Since in Osgi you imports bundles not modules you wouldn't know how many
redistributions of one and the same interface you have in your environment.
Bye,
Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
