Menu
▾
▴
springframework-developer
|
From: <jue...@we...> - 2003-11-25 11:51:58
|
Thomas, can you please update the website accordingly? =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von j=FCrgen h=F6ller [werk3AT] Gesendet: Di 25.11.2003 12:47 An: spr...@li...; = spr...@li... Betreff: [Springframework-developer] Spring Framework 1.0 M3 released Hello everybody, I'm pleased to announce the release of Spring Framework 1.0 M3. This is = the fifth public release towards 1.0 final. As you can see in the = changelog, there have been lots of changes in this iteration. The next = release will be 1.0 RC1; we do not plan any further milestone releases. M3 introduces significant new features and enhancements, among them: - Type 3 IoC support in the bean factory (constructor resolution) - bean factory SPI interfaces (package bean.factory.config) - redesigned AOP API (more flexible pointcut handling etc) - reworked and optimized transaction manager implementations - fine-grained JDBC exception handling in the Hibernate support - reworked JDO support with a new JdoDialect strategy - reworked exception handling in the web framework - working Tiles example application included Some of the changes will need migration of existing code, most notably: - Controllers are now allowed to throw Exception (affecting = BaseCommandController and AbstractFormController) - some of BeanCommandController's methods have been renamed - ServletRequestDataBinder contains a BindException now instead of = deriving from it Typical application code should not be affected as we have kept = deprecated methods. We recommend to migrate promptly though, as we = intend to drop the deprecated methods before 1.0 final. See = changes-M2-M3.txt for details. Regards, Juergen ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: <jue...@we...> - 2003-11-25 13:26:27
|
Shouldn't we also link to Rod's TSS article = (http://www.theserverside.com/resources/article.jsp?l=3DSpringFramework) = from the documentation section? =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von j=FCrgen h=F6ller [werk3AT] Gesendet: Di 25.11.2003 12:49 An: spr...@li... Betreff: Re: [Springframework-developer] Spring Framework 1.0 M3 = released Thomas, can you please update the website accordingly? Juergen ________________________________ Von: spr...@li... im Auftrag = von j=FCrgen h=F6ller [werk3AT] Gesendet: Di 25.11.2003 12:47 An: spr...@li...; = spr...@li... Betreff: [Springframework-developer] Spring Framework 1.0 M3 released Hello everybody, I'm pleased to announce the release of Spring Framework 1.0 M3. This is = the fifth public release towards 1.0 final. As you can see in the = changelog, there have been lots of changes in this iteration. The next = release will be 1.0 RC1; we do not plan any further milestone releases. M3 introduces significant new features and enhancements, among them: - Type 3 IoC support in the bean factory (constructor resolution) - bean factory SPI interfaces (package bean.factory.config) - redesigned AOP API (more flexible pointcut handling etc) - reworked and optimized transaction manager implementations - fine-grained JDBC exception handling in the Hibernate support - reworked JDO support with a new JdoDialect strategy - reworked exception handling in the web framework - working Tiles example application included Some of the changes will need migration of existing code, most notably: - Controllers are now allowed to throw Exception (affecting = BaseCommandController and AbstractFormController) - some of BeanCommandController's methods have been renamed - ServletRequestDataBinder contains a BindException now instead of = deriving from it Typical application code should not be affected as we have kept = deprecated methods. We recommend to migrate promptly though, as we = intend to drop the deprecated methods before 1.0 final. See = changes-M2-M3.txt for details. Regards, Juergen ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Neill R. <nei...@ph...> - 2003-11-25 13:44:49
|
As a user, yes please. I was reading this doco when I first started = spring, wanting to findsome examples, and then lost the URL, and then = had to search theserverside look for it... -----Original Message----- From: j=FCrgen h=F6ller [werk3AT] [mailto:jue...@we...]=20 Sent: 25 November 2003 13:24 To: spr...@li... Subject: Re: [Springframework-developer] Spring Framework 1.0 M3 = released Importance: Low Shouldn't we also link to Rod's TSS article = (http://www.theserverside.com/resources/article.jsp?l=3DSpringFramework) = from the documentation section? =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von j=FCrgen h=F6ller [werk3AT] Gesendet: Di 25.11.2003 12:49 An: spr...@li... Betreff: Re: [Springframework-developer] Spring Framework 1.0 M3 = released Thomas, can you please update the website accordingly? Juergen ________________________________ Von: spr...@li... im Auftrag = von j=FCrgen h=F6ller [werk3AT] Gesendet: Di 25.11.2003 12:47 An: spr...@li...; = spr...@li... Betreff: [Springframework-developer] Spring Framework 1.0 M3 released Hello everybody, I'm pleased to announce the release of Spring Framework 1.0 M3. This is = the fifth public release towards 1.0 final. As you can see in the = changelog, there have been lots of changes in this iteration. The next = release will be 1.0 RC1; we do not plan any further milestone releases. M3 introduces significant new features and enhancements, among them: - Type 3 IoC support in the bean factory (constructor resolution) - bean factory SPI interfaces (package bean.factory.config) - redesigned AOP API (more flexible pointcut handling etc) - reworked and optimized transaction manager implementations - fine-grained JDBC exception handling in the Hibernate support - reworked JDO support with a new JdoDialect strategy - reworked exception handling in the web framework - working Tiles example application included Some of the changes will need migration of existing code, most notably: - Controllers are now allowed to throw Exception (affecting = BaseCommandController and AbstractFormController) - some of BeanCommandController's methods have been renamed - ServletRequestDataBinder contains a BindException now instead of = deriving from it Typical application code should not be affected as we have kept = deprecated methods. We recommend to migrate promptly though, as we = intend to drop the deprecated methods before 1.0 final. See = changes-M2-M3.txt for details. Regards, Juergen ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does = SourceForge.net help you be more productive? Does it help you create = better code? SHARE THE LOVE, and help us help YOU! Click Here: = http://sourceforge.net/donate/ = _______________________________________________ Springframework-developer mailing list = Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does = SourceForge.net help you be more productive? Does it help you create = better code? SHARE THE LOVE, and help us help YOU! Click Here: = http://sourceforge.net/donate/ = _______________________________________________ Springframework-developer mailing list = Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does = SourceForge.net help you be more productive? Does it help you create = better code? SHARE THE LOVE, and help us help YOU! Click Here: = http://sourceforge.net/donate/ = _______________________________________________ Springframework-developer mailing list = Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: <jue...@we...> - 2003-11-25 20:37:02
|
Looking forward, I'm keen on getting out RC1 in December, right before = Christmas if necessary - the goal as I see it is "this year". Our main = concern will be documentation, I guess, as everything else should just = be about bug-fixing and refining. If anyone wants to add a major new = feature, feel free to go ahead but please tell the group and hurry up = ;-) =20 One point to get right for RC1 is correct packaging of third-party = libraries. Like Hibernate, we should include the licenses of all = packages that we ship. And we should update to the current versions of = all libs. In particular, we need to pay attention to Hibernate 2.1: = IIRC, they switched to CGLIB2 in the 2.1 tree, so we should check if our = AOP framework can work with that too. After all, we have numerous users = combining Hibernate and Spring's declarative transaction management. =20 Agreement? Wishes? Complaints? =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von j=FCrgen h=F6ller [werk3AT] Gesendet: Di 25.11.2003 12:47 An: spr...@li...; = spr...@li... Betreff: [Springframework-developer] Spring Framework 1.0 M3 released Hello everybody, I'm pleased to announce the release of Spring Framework 1.0 M3. This is = the fifth public release towards 1.0 final. As you can see in the = changelog, there have been lots of changes in this iteration. The next = release will be 1.0 RC1; we do not plan any further milestone releases. M3 introduces significant new features and enhancements, among them: - Type 3 IoC support in the bean factory (constructor resolution) - bean factory SPI interfaces (package bean.factory.config) - redesigned AOP API (more flexible pointcut handling etc) - reworked and optimized transaction manager implementations - fine-grained JDBC exception handling in the Hibernate support - reworked JDO support with a new JdoDialect strategy - reworked exception handling in the web framework - working Tiles example application included Some of the changes will need migration of existing code, most notably: - Controllers are now allowed to throw Exception (affecting = BaseCommandController and AbstractFormController) - some of BeanCommandController's methods have been renamed - ServletRequestDataBinder contains a BindException now instead of = deriving from it Typical application code should not be affected as we have kept = deprecated methods. We recommend to migrate promptly though, as we = intend to drop the deprecated methods before 1.0 final. See = changes-M2-M3.txt for details. Regards, Juergen ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Colin S. <col...@ex...> - 2003-11-25 21:09:57
|
The issue is that Hibernate 2.1 is still in beta. So while it's hopefully ok for them to go to cglib 2 in their beta, the same thing does not necessarilly apply to us in our 1.0 RC and final releases. That is, I don't personally know what state cglib 2 is right now. We have to look at it ourselves. Even if we do go to cglib2, I think that may kill our ability to work with Hibernate 2.0, if cglib2 is not totally upwards compatible with cglib1. This is important to figure out... I'm actually unclear on why cglib embeds ASM themselves. It's a little bit annoying, as I use AMS outside of cglib, and that fact that it's in the cglib jar means I am tied to that version unless I want to do some surgery. jürgen höller [werk3AT] wrote: >Looking forward, I'm keen on getting out RC1 in December, right before Christmas if necessary - the goal as I see it is "this year". Our main concern will be documentation, I guess, as everything else should just be about bug-fixing and refining. If anyone wants to add a major new feature, feel free to go ahead but please tell the group and hurry up ;-) > >One point to get right for RC1 is correct packaging of third-party libraries. Like Hibernate, we should include the licenses of all packages that we ship. And we should update to the current versions of all libs. In particular, we need to pay attention to Hibernate 2.1: IIRC, they switched to CGLIB2 in the 2.1 tree, so we should check if our AOP framework can work with that too. After all, we have numerous users combining Hibernate and Spring's declarative transaction management. > >Agreement? Wishes? Complaints? > >Juergen > > >________________________________ > >Von: spr...@li... im Auftrag von jürgen höller [werk3AT] >Gesendet: Di 25.11.2003 12:47 >An: spr...@li...; spr...@li... >Betreff: [Springframework-developer] Spring Framework 1.0 M3 released > > > >Hello everybody, > >I'm pleased to announce the release of Spring Framework 1.0 M3. This is the fifth public release towards 1.0 final. As you can see in the changelog, there have been lots of changes in this iteration. The next release will be 1.0 RC1; we do not plan any further milestone releases. > >M3 introduces significant new features and enhancements, among them: >- Type 3 IoC support in the bean factory (constructor resolution) >- bean factory SPI interfaces (package bean.factory.config) >- redesigned AOP API (more flexible pointcut handling etc) >- reworked and optimized transaction manager implementations >- fine-grained JDBC exception handling in the Hibernate support >- reworked JDO support with a new JdoDialect strategy >- reworked exception handling in the web framework >- working Tiles example application included > >Some of the changes will need migration of existing code, most notably: >- Controllers are now allowed to throw Exception (affecting BaseCommandController and AbstractFormController) >- some of BeanCommandController's methods have been renamed >- ServletRequestDataBinder contains a BindException now instead of deriving from it > >Typical application code should not be affected as we have kept deprecated methods. We recommend to migrate promptly though, as we intend to drop the deprecated methods before 1.0 final. See changes-M2-M3.txt for details. > >Regards, >Juergen > > |
|
From: Colin S. <col...@ex...> - 2003-11-25 21:52:41
|
According to this email: http://sourceforge.net/mailarchive/forum.php?thread_id=3471802&forum_id=7517 the Hibernate team is aiming for a Hibernate 2.1 release before Dec. 14th. Assuming that does go through, that makes the decision process a bit simpler for us; we just have to decide if we are targetting the released Hibernate 2.1 and its cglib, or if we want to stick with Hibernate 2.0 for a bit longer. Personally I favour the former, in that I'm already using Hibernate 2.1beta6 with Spring right now, but other people may have other opinions... Regards, Colin Colin Sampaleanu wrote: > The issue is that Hibernate 2.1 is still in beta. So while it's > hopefully ok for them to go to cglib 2 in their beta, the same thing > does not necessarilly apply to us in our 1.0 RC and final releases. > That is, I don't personally know what state cglib 2 is right now. We > have to look at it ourselves. Even if we do go to cglib2, I think that > may kill our ability to work with Hibernate 2.0, if cglib2 is not > totally upwards compatible with cglib1. This is important to figure > out... > > I'm actually unclear on why cglib embeds ASM themselves. It's a little > bit annoying, as I use AMS outside of cglib, and that fact that it's > in the cglib jar means I am tied to that version unless I want to do > some surgery. > > > jürgen höller [werk3AT] wrote: > >> Looking forward, I'm keen on getting out RC1 in December, right >> before Christmas if necessary - the goal as I see it is "this year". >> Our main concern will be documentation, I guess, as everything else >> should just be about bug-fixing and refining. If anyone wants to add >> a major new feature, feel free to go ahead but please tell the group >> and hurry up ;-) >> >> One point to get right for RC1 is correct packaging of third-party >> libraries. Like Hibernate, we should include the licenses of all >> packages that we ship. And we should update to the current versions >> of all libs. In particular, we need to pay attention to Hibernate >> 2.1: IIRC, they switched to CGLIB2 in the 2.1 tree, so we should >> check if our AOP framework can work with that too. After all, we have >> numerous users combining Hibernate and Spring's declarative >> transaction management. >> >> Agreement? Wishes? Complaints? >> >> Juergen >> >> >> ________________________________ >> >> Von: spr...@li... im Auftrag >> von jürgen höller [werk3AT] >> Gesendet: Di 25.11.2003 12:47 >> An: spr...@li...; >> spr...@li... >> Betreff: [Springframework-developer] Spring Framework 1.0 M3 released >> >> >> >> Hello everybody, >> >> I'm pleased to announce the release of Spring Framework 1.0 M3. This >> is the fifth public release towards 1.0 final. As you can see in the >> changelog, there have been lots of changes in this iteration. The >> next release will be 1.0 RC1; we do not plan any further milestone >> releases. >> >> M3 introduces significant new features and enhancements, among them: >> - Type 3 IoC support in the bean factory (constructor resolution) >> - bean factory SPI interfaces (package bean.factory.config) >> - redesigned AOP API (more flexible pointcut handling etc) >> - reworked and optimized transaction manager implementations >> - fine-grained JDBC exception handling in the Hibernate support >> - reworked JDO support with a new JdoDialect strategy >> - reworked exception handling in the web framework >> - working Tiles example application included >> >> Some of the changes will need migration of existing code, most notably: >> - Controllers are now allowed to throw Exception (affecting >> BaseCommandController and AbstractFormController) >> - some of BeanCommandController's methods have been renamed >> - ServletRequestDataBinder contains a BindException now instead of >> deriving from it >> >> Typical application code should not be affected as we have kept >> deprecated methods. We recommend to migrate promptly though, as we >> intend to drop the deprecated methods before 1.0 final. See >> changes-M2-M3.txt for details. >> >> Regards, >> Juergen >> > |
|
From: Alef A. \(JTeam\) <al...@jt...> - 2003-11-25 22:16:51
|
> or if we want to stick with=20 > Hibernate 2.0=20 > for a bit longer. I don't know. Personally I don't think we will have much problem with the transition to 2.1, but I don't know about other people. Are there any significant differences between Hibernate 2.1 and 2.0 that would convince us to switch, besides the CGLIB stuff? If there aren't any major compatibility-issues I would prefer checking both CGLIB1 and 2 (thus supporting both Hib 2.0 and 2.1), but that might generatea lot of work... It would however allow people having Spring mX in production already to change to Spring 1.0 without changing Hibernate version... Just some thougts... > Regards, > Colin >=20 > Colin Sampaleanu wrote: >=20 > > The issue is that Hibernate 2.1 is still in beta. So while it's > > hopefully ok for them to go to cglib 2 in their beta, the=20 > same thing=20 > > does not necessarilly apply to us in our 1.0 RC and final releases.=20 > > That is, I don't personally know what state cglib 2 is=20 > right now. We=20 > > have to look at it ourselves. Even if we do go to cglib2, I=20 > think that=20 > > may kill our ability to work with Hibernate 2.0, if cglib2 is not=20 > > totally upwards compatible with cglib1. This is important to figure=20 > > out... > > > > I'm actually unclear on why cglib embeds ASM themselves.=20 > It's a little > > bit annoying, as I use AMS outside of cglib, and that fact=20 > that it's=20 > > in the cglib jar means I am tied to that version unless I=20 > want to do=20 > > some surgery. > > > > > > j=FCrgen h=F6ller [werk3AT] wrote: > > > >> Looking forward, I'm keen on getting out RC1 in December, right > >> before Christmas if necessary - the goal as I see it is=20 > "this year".=20 > >> Our main concern will be documentation, I guess, as=20 > everything else=20 > >> should just be about bug-fixing and refining. If anyone=20 > wants to add=20 > >> a major new feature, feel free to go ahead but please tell=20 > the group=20 > >> and hurry up ;-) > >> > >> One point to get right for RC1 is correct packaging of third-party > >> libraries. Like Hibernate, we should include the licenses of all=20 > >> packages that we ship. And we should update to the current=20 > versions=20 > >> of all libs. In particular, we need to pay attention to Hibernate=20 > >> 2.1: IIRC, they switched to CGLIB2 in the 2.1 tree, so we should=20 > >> check if our AOP framework can work with that too. After=20 > all, we have=20 > >> numerous users combining Hibernate and Spring's declarative=20 > >> transaction management. > >> > >> Agreement? Wishes? Complaints? > >> > >> Juergen > >> > >> > >> ________________________________ > >> > >> Von: spr...@li...=20 > im Auftrag > >> von j=FCrgen h=F6ller [werk3AT] > >> Gesendet: Di 25.11.2003 12:47 > >> An: spr...@li...;=20 > >> spr...@li... > >> Betreff: [Springframework-developer] Spring Framework 1.0=20 > M3 released > >> > >> > >> > >> Hello everybody, > >> > >> I'm pleased to announce the release of Spring Framework=20 > 1.0 M3. This > >> is the fifth public release towards 1.0 final. As you can=20 > see in the=20 > >> changelog, there have been lots of changes in this iteration. The=20 > >> next release will be 1.0 RC1; we do not plan any further milestone=20 > >> releases. > >> > >> M3 introduces significant new features and enhancements,=20 > among them: > >> - Type 3 IoC support in the bean factory (constructor resolution) > >> - bean factory SPI interfaces (package bean.factory.config) > >> - redesigned AOP API (more flexible pointcut handling etc) > >> - reworked and optimized transaction manager implementations > >> - fine-grained JDBC exception handling in the Hibernate support > >> - reworked JDO support with a new JdoDialect strategy > >> - reworked exception handling in the web framework > >> - working Tiles example application included > >> > >> Some of the changes will need migration of existing code, most=20 > >> notably: > >> - Controllers are now allowed to throw Exception (affecting=20 > >> BaseCommandController and AbstractFormController) > >> - some of BeanCommandController's methods have been renamed > >> - ServletRequestDataBinder contains a BindException now instead of=20 > >> deriving from it > >> > >> Typical application code should not be affected as we have kept > >> deprecated methods. We recommend to migrate promptly though, as we=20 > >> intend to drop the deprecated methods before 1.0 final. See=20 > >> changes-M2-M3.txt for details. > >> > >> Regards, > >> Juergen > >> =20 > > >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program.=20 > Does SourceForge.net help you be more productive? Does it=20 > help you create better code? SHARE THE LOVE, and help us=20 > help YOU! Click Here: http://sourceforge.net/donate/=20 > _______________________________________________ > Springframework-developer mailing list=20 > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 |
|
From: Chris N. <ch...@si...> - 2003-11-25 21:59:41
|
Colin Sampaleanu wrote: > The issue is that Hibernate 2.1 is still in beta. So while it's > hopefully ok for them to go to cglib 2 in their beta, the same thing > does not necessarilly apply to us in our 1.0 RC and final releases. That > is, I don't personally know what state cglib 2 is right now. We have to > look at it ourselves. Even if we do go to cglib2, I think that may kill > our ability to work with Hibernate 2.0, if cglib2 is not totally upwards > compatible with cglib1. This is important to figure out... I'm happy to answer any questions, but here is the current state of things. CGLIB 2.0 is currently released as beta1. Beta2 will be released "any day now". I don't anticipate many changes between beta2 and final. Hibernate 2.1 beta 6 (the latest release) still uses CGLIB 1.0. Hibernate 2.1 CVS uses CGLIB from CVS (equivalent to upcoming beta2 code). I imagine that Hibernate 2.1 final will use whatever release of CGLIB is available at the time. It may be possible for us to release 2.0 final in tandem with Hibernate 2.1, but I'm not positive. The original plan was for CGLIB 1.0 and 2.0 to be able to coexist peacefully. This was enabled by moving all of the net.sf.cglib.* classes into a new package (net.sf.cglib.proxy). However, we recently switched CGLIB 2.0 to use ASM 1.4, which is *not* binary compatible with ASM 1.3 (which CGLIB 1.0 uses). This means that you can no longer use CGLIB 1.0 and 2.0 in the same environment. Practically, this means that you must upgrade to CGLIB 2.0 when you switch to supporting Hibernate 2.1. I really don't see a way around this. However, I've looked at your use of CGLIB and the changes are trivial, just renaming a few import statements. I can supply you with a patch when the time comes. I would not worry about stability--your use of CGLIB is very simple, and in any case will be heavily tested by inclusion with Hibernate 2.1. > I'm actually unclear on why cglib embeds ASM themselves. It's a little > bit annoying, as I use AMS outside of cglib, and that fact that it's in > the cglib jar means I am tied to that version unless I want to do some > surgery. Our build.xml creates two jar files, one that includes the ASM classes (the "full" version) and one that doesn't. Both versions are also available for download. Feel free to use the separate one. FYI at times CGLIB has depended on a CVS version of ASM but currently it is in sync with ASM 1.4. Chris |
|
From: Colin S. <col...@ex...> - 2003-11-25 22:23:33
|
Chris Nokleberg wrote: >Colin Sampaleanu wrote: > > >>The issue is that Hibernate 2.1 is still in beta. So while it's >>hopefully ok for them to go to cglib 2 in their beta, the same thing >>does not necessarilly apply to us in our 1.0 RC and final releases. That >>is, I don't personally know what state cglib 2 is right now. We have to >>look at it ourselves. Even if we do go to cglib2, I think that may kill >>our ability to work with Hibernate 2.0, if cglib2 is not totally upwards >>compatible with cglib1. This is important to figure out... >> >> > >I'm happy to answer any questions, but here is the current state of things. > >CGLIB 2.0 is currently released as beta1. Beta2 will be released "any day >now". I don't anticipate many changes between beta2 and final. > >Hibernate 2.1 beta 6 (the latest release) still uses CGLIB 1.0. Hibernate >2.1 CVS uses CGLIB from CVS (equivalent to upcoming beta2 code). > >I imagine that Hibernate 2.1 final will use whatever release of CGLIB is >available at the time. It may be possible for us to release 2.0 final in >tandem with Hibernate 2.1, but I'm not positive. > >The original plan was for CGLIB 1.0 and 2.0 to be able to coexist >peacefully. This was enabled by moving all of the net.sf.cglib.* classes >into a new package (net.sf.cglib.proxy). However, we recently switched >CGLIB 2.0 to use ASM 1.4, which is *not* binary compatible with ASM 1.3 >(which CGLIB 1.0 uses). This means that you can no longer use CGLIB 1.0 and >2.0 in the same environment. > >Practically, this means that you must upgrade to CGLIB 2.0 when you switch >to supporting Hibernate 2.1. I really don't see a way around this. However, >I've looked at your use of CGLIB and the changes are trivial, just renaming >a few import statements. I can supply you with a patch when the time comes. >I would not worry about stability--your use of CGLIB is very simple, and in >any case will be heavily tested by inclusion with Hibernate 2.1. > > > >>I'm actually unclear on why cglib embeds ASM themselves. It's a little >>bit annoying, as I use AMS outside of cglib, and that fact that it's in >>the cglib jar means I am tied to that version unless I want to do some >>surgery. >> >> > >Our build.xml creates two jar files, one that includes the ASM classes (the >"full" version) and one that doesn't. Both versions are also available for >download. Feel free to use the separate one. FYI at times CGLIB has >depended on a CVS version of ASM but currently it is in sync with ASM 1.4. > >Chris > > > Thanks Chris. That clarifies things. So at this point it looks like as of the next release of Hibernate 2.1 (beta or final, whatever it is), we have no choice but to target either Hibernate 2.0 (with cglib1), or Hibernate 2.1 (with cglib2), without some extra effort. We don't do an incredible amount with cglib, so we could possibly support both Hibernate versions by accessing cglib through some sort of wrapper. I'm not incredibly fond of this idea, especially as cglib2 and the newer asm look to offer some really nice capabilities, but it's an option... Now taking a second look at your statements more carefully. Colin |
|
From: Alef A. \(JTeam\) <al...@jt...> - 2003-11-25 22:29:49
|
> So at this point it looks like as of the next release of > Hibernate 2.1 > (beta or final, whatever it is), we have no choice but to > target either > Hibernate 2.0 (with cglib1), or Hibernate 2.1 (with cglib2), without > some extra effort. I think I have to consider my last email as _not sent_ after reading Chris' mail :)) |
|
From: Chris N. <ch...@si...> - 2003-11-25 22:28:00
|
Chris Nokleberg wrote: > The original plan was for CGLIB 1.0 and 2.0 to be able to coexist > peacefully. This was enabled by moving all of the net.sf.cglib.* classes > into a new package (net.sf.cglib.proxy). However, we recently switched > CGLIB 2.0 to use ASM 1.4, which is *not* binary compatible with ASM 1.3 > (which CGLIB 1.0 uses). This means that you can no longer use CGLIB 1.0 > and 2.0 in the same environment. Actually there are two possibilities, if you need to support Hibernate 2.0 and 2.1 simultaneously, or just want to use CGLIB 1.0 for AOP but CGLIB 2.0 for Hib2.1: a) Use the BCEL version of CGLIB 1.0. This adds an extra 350K, is slower to generate classes, and has some thread safety issues. Also, many other projects use BCEL so you are bound to run into some version conflicts here anyway. b) Fork the CGLIB 1.0 and ASM 1.3 sources, repackage ASM (e.g. "org.springframework.asm") and change the CGLIB source to use the forked package. It's easier than it sounds, but I'd still avoid it if possible. Chris |
|
From: <jue...@we...> - 2003-11-25 21:41:00
|
I rather meant that we should check whether CGLIB2 is compatible with = our current AOP framework. CGLIB2 is still in beta, so we shouldn't rely = on it, I agree. But we need to figure out a way to work with both = Hibernate 2.1 and our AOP framework in the same application, as this = will be a common combo at the time of our 1.0 final. =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von Colin Sampaleanu Gesendet: Di 25.11.2003 22:09 An: spr...@li... Betreff: Re: [Springframework-developer] Spring Framework 1.0 M3 = released The issue is that Hibernate 2.1 is still in beta. So while it's hopefully ok for them to go to cglib 2 in their beta, the same thing does not necessarilly apply to us in our 1.0 RC and final releases. That is, I don't personally know what state cglib 2 is right now. We have to look at it ourselves. Even if we do go to cglib2, I think that may kill our ability to work with Hibernate 2.0, if cglib2 is not totally upwards compatible with cglib1. This is important to figure out... I'm actually unclear on why cglib embeds ASM themselves. It's a little bit annoying, as I use AMS outside of cglib, and that fact that it's in the cglib jar means I am tied to that version unless I want to do some surgery. j=FCrgen h=F6ller [werk3AT] wrote: >Looking forward, I'm keen on getting out RC1 in December, right before = Christmas if necessary - the goal as I see it is "this year". Our main = concern will be documentation, I guess, as everything else should just = be about bug-fixing and refining. If anyone wants to add a major new = feature, feel free to go ahead but please tell the group and hurry up = ;-) > >One point to get right for RC1 is correct packaging of third-party = libraries. Like Hibernate, we should include the licenses of all = packages that we ship. And we should update to the current versions of = all libs. In particular, we need to pay attention to Hibernate 2.1: = IIRC, they switched to CGLIB2 in the 2.1 tree, so we should check if our = AOP framework can work with that too. After all, we have numerous users = combining Hibernate and Spring's declarative transaction management. > >Agreement? Wishes? Complaints? > >Juergen > > >________________________________ > >Von: spr...@li... im Auftrag = von j=FCrgen h=F6ller [werk3AT] >Gesendet: Di 25.11.2003 12:47 >An: spr...@li...; = spr...@li... >Betreff: [Springframework-developer] Spring Framework 1.0 M3 released > > > >Hello everybody, > >I'm pleased to announce the release of Spring Framework 1.0 M3. This is = the fifth public release towards 1.0 final. As you can see in the = changelog, there have been lots of changes in this iteration. The next = release will be 1.0 RC1; we do not plan any further milestone releases. > >M3 introduces significant new features and enhancements, among them: >- Type 3 IoC support in the bean factory (constructor resolution) >- bean factory SPI interfaces (package bean.factory.config) >- redesigned AOP API (more flexible pointcut handling etc) >- reworked and optimized transaction manager implementations >- fine-grained JDBC exception handling in the Hibernate support >- reworked JDO support with a new JdoDialect strategy >- reworked exception handling in the web framework >- working Tiles example application included > >Some of the changes will need migration of existing code, most notably: >- Controllers are now allowed to throw Exception (affecting = BaseCommandController and AbstractFormController) >- some of BeanCommandController's methods have been renamed >- ServletRequestDataBinder contains a BindException now instead of = deriving from it > >Typical application code should not be affected as we have kept = deprecated methods. We recommend to migrate promptly though, as we = intend to drop the deprecated methods before 1.0 final. See = changes-M2-M3.txt for details. > >Regards, >Juergen >=20 > ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: <tri...@tr...> - 2003-11-25 16:44:57
|
Juerge, Website is now updated. Thomas Quoting "jürgen höller [werk3AT]" <jue...@we...>: > Thomas, can you please update the website accordingly? > > Juergen > > > ________________________________ > > Von: spr...@li... im Auftrag von > jürgen höller [werk3AT] > Gesendet: Di 25.11.2003 12:47 > An: spr...@li...; > spr...@li... > Betreff: [Springframework-developer] Spring Framework 1.0 M3 released > > > > Hello everybody, > > I'm pleased to announce the release of Spring Framework 1.0 M3. This is the > fifth public release towards 1.0 final. As you can see in the changelog, > there have been lots of changes in this iteration. The next release will be > 1.0 RC1; we do not plan any further milestone releases. > > M3 introduces significant new features and enhancements, among them: > - Type 3 IoC support in the bean factory (constructor resolution) > - bean factory SPI interfaces (package bean.factory.config) > - redesigned AOP API (more flexible pointcut handling etc) > - reworked and optimized transaction manager implementations > - fine-grained JDBC exception handling in the Hibernate support > - reworked JDO support with a new JdoDialect strategy > - reworked exception handling in the web framework > - working Tiles example application included > > Some of the changes will need migration of existing code, most notably: > - Controllers are now allowed to throw Exception (affecting > BaseCommandController and AbstractFormController) > - some of BeanCommandController's methods have been renamed > - ServletRequestDataBinder contains a BindException now instead of deriving > from it > > Typical application code should not be affected as we have kept deprecated > methods. We recommend to migrate promptly though, as we intend to drop the > deprecated methods before 1.0 final. See changes-M2-M3.txt for details. > > Regards, > Juergen > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
