We do this in a few cases by adding a "patch.jar" entry *first* on
the classpath of the bundle that has the problem. Then you can add a
fragment of that bundle where the fragment has patch.jar in it. This
way, the contents of patch.jar are added first on the classpath of the
host and override the classes in the host. Of course, this only works
if you can change the host bundle's classpath.
There has been discussion several times about formalizing the notion
of a patch fragment but it has not happened to date AFAIK.
Jeff
On 14-Jul-09, at 2:10 AM, Keith Garry Boyce wrote:
Hi.. I was wondering if you have any insite into following: In
development I sometimes find 3rd party jars which have bugs that I
need fixed in order to continue with development. What I have been
doing is putting those classes in WEB-INF/classes of web app so
these classes come first before the classpath of the jar in WEB-INF/
lib.. This is quite messy. Is that something handled out of the box
by OSGI? From my reading I can see you can version a package but not
override a class in a package in a straightforward manageable way....
Thanks,
Garry
Hotmail® has ever-growing storage! Don’t worry about storage limits.
Check it out._______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
