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 "Virgo/Community/Migrating from dm Server"
(→Migrating from dm Server 2.0.x to Virgo 2.1.0.x) |
(→Service Properties) |
||
| Line 63: | Line 63: | ||
=== Service Properties === | === Service Properties === | ||
| − | The service property which is used to control the scope of publication of a service is renamed from com.springsource.service.scope to org.eclipse.virgo.service.scope. The name com.springsource.service.scope is tolerated as a synonym of org.eclipse.virgo.service.scope for the 2.1.0 release but this behaviour may be dropped in a future release. | + | The service property which is used to control the scope of publication of a service is renamed from com.springsource.service.scope to org.eclipse.virgo.service.scope. The name com.springsource.service.scope is tolerated as a synonym of org.eclipse.virgo.service.scope for the 2.1.0 release but this behaviour may be dropped in a future release and a warning event log message is issued. |
=== Shell === | === Shell === | ||
Revision as of 09:14, 21 September 2010
Migrating from dm Server 2.0.x to Virgo 2.1.0.x
The following changes in Virgo 2.1.0.x affect users migrating from dm Server 2.0.x:
Package Names
The Java package names of the code have been renamed from com.springsource or org.eclipse.
Some of these packages are more likely than others to be used by applications. For example, the following web configuration:
<context-param>
<param-name>contextClass</param-name>
<param-value>com.springsource.server.web.dm.ServerOsgiBundleXmlWebApplicationContext</param-value>
</context-param>
needs to be changed to:
<context-param>
<param-name>contextClass</param-name>
<param-value>org.eclipse.virgo.web.dm.ServerOsgiBundleXmlWebApplicationContext</param-value>
</context-param>
The main package changes are shown in the following table although very few of these are likely to impact applications. Users who have modified or extended dm Server are far more likely to be affected.
| dm Server 2.0.x | Virgo 2.1.0.x |
|---|---|
| com.springsource.osgi.teststubs.* | org.eclipse.virgo.teststubs.osgi.* |
| com.springsource.osgi.extensions.* | org.eclipse.virgo.osgi.extensions.* |
| com.springsource.osgi.launcher.* | org.eclipse.virgo.osgi.launcher.* |
| com.springsource.util.* | org.eclipse.virgo.util.* |
| com.springsource.osgi.test.* | org.eclipse.virgo.test.* |
| com.springsource.osgi.medic.* | org.eclipse.virgo.medic.* |
| com.springsource.repository.* | org.eclipse.virgo.repository.* |
| com.springsource.kernel.* | org.eclipse.virgo.kernel.* |
| com.springsource.osgi.webcontainer.* | org.eclipse.gemini.web.* |
| com.springsource.server.* | org.eclipse.virgo.* |
Service Properties
The service property which is used to control the scope of publication of a service is renamed from com.springsource.service.scope to org.eclipse.virgo.service.scope. The name com.springsource.service.scope is tolerated as a synonym of org.eclipse.virgo.service.scope for the 2.1.0 release but this behaviour may be dropped in a future release and a warning event log message is issued.
Shell
The kernel shell did not make it through the stringent Eclipse IP process and so Virgo extends the Equinox console instead.
The inline shell is no longer supported and the "-shell" switch on the startup script produces a warning.
The Equinox console is configured in the user region properties file via the osgi.console property with a default value of 2401.
The kernel properties shell.enabled and shell.port are no longer used and are ignored if specified. Remote access to the Equinox console is via telnet (whereas the kernel shell supported ssh).
Service Wrapper
The service wrapper did not make it through the stringent Eclipse IP process and so is no longer supported. Anyone needing this function will need to create their own service wrapper or take the one from dm Server 2.0.x and doctor it.