Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368603 - Springframework 3.1.0 not working (user space) without patching Virgo bundles
Summary: Springframework 3.1.0 not working (user space) without patching Virgo bundles
Status: CLOSED DUPLICATE of bug 357273
Alias: None
Product: Virgo
Classification: RT
Component: runtime (show other bugs)
Version: 3.0.2.RELEASE   Edit
Hardware: All Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-14 07:46 EST by Roland Hauser CLA
Modified: 2012-01-16 04:08 EST (History)
1 user (show)

See Also:

Attachments
Manifest of org.eclipse.virgo.kernel.agent.dm-3.0.2.RELEASE.jar (1.75 KB, application/octet-stream)
2012-01-14 07:58 EST, Roland Hauser CLA 		no flags Details
Manifest of org.eclipse.virgo.kernel.deployer.dm-3.0.2.RELEASE.jar (1.32 KB, application/octet-stream)
2012-01-14 07:58 EST, Roland Hauser CLA 		no flags Details
Manifest of org.eclipse.virgo.kernel.dmfragment-3.0.2.RELEASE.jar (1.70 KB, application/octet-stream)
2012-01-14 07:59 EST, Roland Hauser CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Roland Hauser CLA 2012-01-14 07:46:36 EST 
Build Identifier: 3.0.2.RELEASE

Hi guys,

Following to thread http://www.eclipse.org/forums/index.php/m/723896/ and FAQ http://wiki.eclipse.org/Virgo/FAQ#How_can_I_change_the_version_of_Spring_framework_in_the_user_region.3F I tried to upgrade the Spring Framework in Virgos user space to version 3.1 and noticed the same problems as reported in Bug 357273. After modifying the version range of the spring dependencies in the manifest of following bundles Virgo works like a charm:
- org.eclipse.virgo.kernel.agent.dm-3.0.2.RELEASE
- org.eclipse.virgo.kernel.deployer.dm-3.0.2.RELEASE
- org.eclipse.virgo.kernel.dmfragment-3.0.2.RELEASE

I only patched the bundles in the ext repository and didn't touch any kernel space bundles or configurations.

Note: We use such a patched Virgo Tomcat instance in a production environment and we didn't encounter any problems.


Reproducible: Always

Steps to Reproduce:
1. Update the Spring Framework without patching any Virgo bundles.
Comment 1 Roland Hauser CLA 2012-01-14 07:58:10 EST 
Created attachment 209493 [details]
Manifest of org.eclipse.virgo.kernel.agent.dm-3.0.2.RELEASE.jar
Comment 2 Roland Hauser CLA 2012-01-14 07:58:57 EST 
Created attachment 209494 [details]
Manifest of org.eclipse.virgo.kernel.deployer.dm-3.0.2.RELEASE.jar
Comment 3 Roland Hauser CLA 2012-01-14 07:59:44 EST 
Created attachment 209495 [details]
Manifest of org.eclipse.virgo.kernel.dmfragment-3.0.2.RELEASE.jar
Comment 4 Glyn Normington CLA 2012-01-16 04:08:16 EST 
Thanks for bringing this up but this is already fixed for Virgo 3.5.0 in bug 357273. Our policy is not to backport enhancements (or for that matter non-critical bugs) to service releases. (That kind of support is only available commercially - see http://www.eclipse.org/virgo/support/.)

I have tweaked the FAQ to make the situation clear. Previously the FAQ said "Virgo 3.0.x can use 3.0.x versions of Spring framework." so I added "To use Spring framework 3.1.x requires Virgo 3.5.0 or later."

*** This bug has been marked as a duplicate of bug 357273 ***