The IPreferenceStore API of Eclipse is based on OSGi's preferences service. Equinox implements several scope context for different preferences, such DefaultScope, InstanceScope and ConfigurationScope. The IPreferenceStore is the wrapper of instance scope for back-compatibility. It stored the data in …
Read More about Eclipse/OSGi preferenceEclipse platform register an OSGi service 'IProxyService' to manage network connection, which has capability to set proxy setting. There are three types of proxy working mode, Direct(no proxy), Manual(specified by user), Native(using OS's proxy setting, such as gnome-proxy, IE). There are three types of proxy supported …
Read More about The usage of Eclipse's Proxy APISet vm arguments 'osgi.framework.extensions' and 'osgi.frameworkClassPath' when vm starts. If those value are set, those jar or path would be added into the classloader when starting EclipseStarter. See org.eclipse.equinox.launcher.Main for more details in the source code of Eclipse 3.4. Best Regards Kane
Read More about [OSGi][Eclipse]Add custom jar or path into Equinox FrameworkThe answer is very simple, using the service 'org.eclipse.service.PackageAdmin'.
Read More about [OSGi]How to acquire the fragments of specified bundleEquinox uses the adaptor hooks to implement the class loader. See http://wiki.eclipse.org/Adaptor_Hooks for more detail BaseClassLoadingHook would search the native code on itself. If it find the file in that jar file, it would extract the native library into its storage folder. EclipseClassLoadingHook defines some …
Read More about [Eclipse]Equinox's classloader and its URL schemaOSGi Spec defines Bundle-NativeCode header to contain a specification of native code libraries contained in that bundle. All magic things are initialized by org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLibrary(String) and org.eclipse.osgi.framework.internal.core.BundleLoader.findLibrary(String). Then …
Read More about [OSGi][Equinox]the Bundle-NativeCode implementation in EquinoxYou must see the qualifier string property when exporting your features and plug-ins by Eclipse pde. But specified qualifier string won't appear after you export the features successfully. If you want to use the qualifier string, you must define your feature and plug-in version like below: 1.0.0.qualifier, …
Read More about [Eclipse]How to use qualifier string when exporting features and plug-insWhen you develop a rich client application base on eclipse framework, and your application require eclipse platform feature, you would find that your application has some menu items contributed by eclipse platform. Those menu items are defined by several plug-ins' implementation of actionSet extention point. In fact …
Read More about [Eclipse]get rid of the menus of eclipse platformThose days my work is focus on eclipse's update. Now I understand the general mechanism and meet some issues when using it in development work. The update mechanism includes four major types: install, enable, disable and uninstall. And all of those operations can be executed by command line, such as installing a …
Read More about [Eclipse]Eclipse update supportI met a defect that dynamically created menu items disappear after creating a new viewPart. It caused me overtime last Friday. Today I find the root cause. The scenario is: open first document, the items are shown well open another document, the items disappear The requirement is that showing the menu items while …
Read More about [Eclipse]The call sequence between partActivated and menu update