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 "Virgo/Community/Migrating from 3.5.x to 3.6.0"
(→Fragments May Attach to Multiple Hosts) |
|||
| Line 5: | Line 5: | ||
Virgo 3.6.0 added the following property to configuration/config.ini: | Virgo 3.6.0 added the following property to configuration/config.ini: | ||
| − | osgi.support.multipleHosts=true | + | osgi.support.multipleHosts=true |
This enables fragments to attach to multiple hosts, in line with the OSGi Core specification. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=393848 bug 393848] for details. If this behaviour causes an issue, users may delete the property from config.ini. | This enables fragments to attach to multiple hosts, in line with the OSGi Core specification. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=393848 bug 393848] for details. If this behaviour causes an issue, users may delete the property from config.ini. | ||
Revision as of 11:09, 8 November 2012
Support for Java 7 with a Limitation
Virgo 3.6.0 supports Java 7 (see bug 382710), but there is a known performance problem with the Spring framework on JDK 1.7.0_06 or newer (see SPR-9781). This will be fixed in Spring 3.2 and, given that Virgo 3.6.0 supports Spring 3.1 (bug 357102), it should be possible for users to upgrade to Spring 3.2 as described in the FAQ.
Fragments May Attach to Multiple Hosts
Virgo 3.6.0 added the following property to configuration/config.ini:
osgi.support.multipleHosts=true
This enables fragments to attach to multiple hosts, in line with the OSGi Core specification. See bug 393848 for details. If this behaviour causes an issue, users may delete the property from config.ini.