Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Disabling R-OSGi"
| Line 5: | Line 5: | ||
# When concerned about security of opening default port 9278 (e.g. server scenarios). | # 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 | + | 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''' | '''-Dch.ethz.iks.r_osgi.registerDefaultChannel=false''' | ||
| − | For example, | + | For example, to disable R-OSGi in Eclipse where ECF is installed: |
| − | eclipse.exe -vmargs -Dch.ethz.iks.r_osgi.registerDefaultChannel=false | + | '''eclipse.exe -vmargs -Dch.ethz.iks.r_osgi.registerDefaultChannel=false''' |
Revision as of 16:54, 2 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