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 3.5.x to 3.6.0"
(→Support for Java 7 with a Limitation) |
(→Support for Java 7 with a Limitation) |
||
| Line 1: | Line 1: | ||
= Support for Java 7 with a Limitation = | = Support for Java 7 with a Limitation = | ||
| − | Virgo 3.6.0 supports Java 7 (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=382710 bug 382710]), but there is a known performance problem with the Spring framework on JDK 1.7.0_06 or newer (see [https://jira.springsource.org/browse/SPR-9781 SPR-9781]). | + | Virgo 3.6.0 supports Java 7 (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=382710 bug 382710]), but there is a known performance problem with the Spring framework on JDK 1.7.0_06 or newer (see [https://jira.springsource.org/browse/SPR-9781 SPR-9781]). Since Virgo 3.6.0 supports Spring framework 3.2 (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=394800 bug 394800]), users can upgrade to Spring framework 3.2 as described in the [http://wiki.eclipse.org/Virgo/FAQ#How_can_I_change_the_version_of_Spring_framework_in_the_user_region.3F FAQ]. |
= Fragments May Attach to Multiple Hosts = | = Fragments May Attach to Multiple Hosts = | ||
Revision as of 12:00, 26 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). Since Virgo 3.6.0 supports Spring framework 3.2 (see bug 394800), users can upgrade to Spring framework 3.2 as described in the FAQ.
Fragments May Attach to Multiple Hosts
Virgo 3.6.0 adds 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.