Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Disabling R-OSGi"
| Line 12: | Line 12: | ||
'''eclipse.exe -vmargs -Dch.ethz.iks.r_osgi.registerDefaultChannel=false''' | '''eclipse.exe -vmargs -Dch.ethz.iks.r_osgi.registerDefaultChannel=false''' | ||
| + | |||
| + | See also [[R-OSGi Properties]] | ||
Latest revision as of 20:56, 14 June 2009
Sometimes, it's necessary or desirable to disable the automatic running of an R-OSGi instance and the attendant creation of a listener on R-OSGi's default port (9278).
- When attempting to run other R-OSGi instance(s) on the localhost (e.g. running the Getting Started with ECF's RFC119 Implementation).
- When running JUnit plugin tests on localhost that publish OSGi services using R-OSGi provider
- When concerned about security of opening default port 9278 (e.g. server scenarios).
To disable R-OSGi in a given instance, provide the following on when starting (Eclipse or some other Equinox app where ECF is installed):
-Dch.ethz.iks.r_osgi.registerDefaultChannel=false
For example, to disable R-OSGi in Eclipse where ECF is installed:
eclipse.exe -vmargs -Dch.ethz.iks.r_osgi.registerDefaultChannel=false
See also R-OSGi Properties