|
Re: Patching deployed plugin [message #1600820 is a reply to message #1600803] |
Wed, 04 February 2015 14:11 |
|
I'd say you don't want to patch your own bundle:
Quote:Fragment-Host: host.plugin.ui;bundle-version="1.0.0"
The 'host' bundle is the one where you'd like to change one of the classes. In your case the host is very likely one of the RAP bundles, e.g. org.eclipse.rap.rwt.
(Another pitfall could be that the RAP bundles are signed... and since your fragment isn't signed, or signed with another certificate, this could be the next problem when your classloader detects classes from with different certificates in a single Java package namespace. In that case my guess is that your only option is to remove the signing info from the RAP bundle(s).)
Regards,
Markus
--
Twitter: @mknauer23 and @EclipseRAP
Blog: http://eclipsesource.com/blogs/
Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
|
|
|
|
|
|
Re: Patching deployed plugin [message #1600884 is a reply to message #1600859] |
Wed, 04 February 2015 15:06 |
|
Aleksander wrote on Wed, 04 February 2015 15:46Ok we were afraid of this. No our plug-in wasn't prepared for this. There is no other way?
Thank you for your support.
No, unfortunately I don't know of any other way to circumvent this. Sorry.
If you have access to the OSGi console you could try to install an updated version of your bundle and uninstall the old one. But that's something that I would try on a stand-by system first...
Regards,
Markus
--
Twitter: @mknauer23 and @EclipseRAP
Blog: http://eclipsesource.com/blogs/
Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
|
|
|
Powered by
FUDForum. Page generated in 0.02063 seconds