Re: [virgo-dev] Virgo 3.6.0, Java 7 & Spring 3.2 - question

[Glyn Normington <gnormington@xxxxxxxxxx>]

The Spring developers have now made a public statement about OSGi metadata for Spring 3.2:

http://www.springsource.org/springframework-ebr

If there are any concerns, I suggest raising them in SPR-8903 ([1]).

Regards,

Glyn

---

From: "Glyn Normington" <gnormington@xxxxxxxxxx>
To: "Virgo Project" <virgo-dev@xxxxxxxxxxx>
Sent: Thursday, 27 September, 2012 10:58:53 AM
Subject: Re: [virgo-dev] Virgo 3.6.0, Java 7 & Spring 3.2 - question

Hi Charles

I don't have an immediate solution, but I hope one will emerge, at least for released versions of Spring 3.2.x. I'm afraid I can't say more presently.

Meanwhile, you (and anyone else with similar concerns) may care to make your views known to the Spring community. I raised a JIRA ([1]) last year to prompt discussion and a recent forum thread ([2]) has been discussing this topic and mentions another JIRA ([3]).

Regards,
Glyn

[1] https://jira.springsource.org/browse/SPR-8903

[2] http://forum.springsource.org/showthread.php?129344-Spring-3-2-Milestone-1-and-OSGi-meta-data

[3] https://jira.springsource.org/browse/SPR-9801

On 27 Sep 2012, at 08:48, Charles Vuijst wrote:

Hi All,

 

To prepare for the transfer to Java 7, I’ve been reading about the related issues on different forums. I noticed the following:

 

At: http://wiki.eclipse.org/Virgo/Community/Migrating_from_3.5.x_to_3.6.0

It says that Virgo 3.6.0 supports Java 7, but for the known performance problem with the Spring framework, an additional upgrade is proposed to Spring 3.2 when that one becomes available.

 

Reading about Spring 3.2, I noticed at: http://www.eclipse.org/forums/index.php/m/915433/

That “…“ Spring 3.2 and beyond will not ship by default with OSGi metadata anymore ”…”

 

To check that, I downloaded the current milestone of Spring: 3.2.0.M1 from http://www.springsource.org/download/community

 

I opened a couple of jars, and indeed, the Manifest.MF files are rather empty.

 

Anyone has more info if this is either going to be fixed by SpringSource or if some alternative will come up?

 

Best regards,

 

Charles Vuijst

_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev

_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev