Community
Participate
Working Groups
This bug captures the changes in Virgo 2.1.0 which will affect users migrating from dm Server 2.0.x.
The Java package names of the code have been renamed from com.springsource or org.eclipse. Some of these packages are more likely 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 service wrapper did not make it through the 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.
The kernel shell did not make it through the Eclipse IP process and so Virgo extends the Equinox console instead. The inline shell is no longer supported and the "-shell" script on the startup script produces a warning. The Equinox console is configured in the user region properties file via the osgi.console property. 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).
This information has been captured in the wiki.