springframework-developer — Spring Framework developers list

Re: [Springframework-developer] RE: About CGLIB2

[Colin S. <col...@ex...>]

Yes, getting rid of that bloated beast will clear up 500k!  
BCELAttributes and BCELAttributeWriter from the Sandbox can still be 
accessed from CVS history when we want to do the new versions...


Rod Johnson wrote:

>Would this also mean doing away with BCEL for good (a good idea)?
>
>----- Original Message ----- 
>From: "Colin Sampaleanu" <col...@ex...>
>To: <spr...@li...>
>Sent: Thursday, December 11, 2003 3:24 PM
>Subject: Re: [Springframework-developer] RE: About CGLIB2
>
>
>  
>
>>I vote for updating to cglib2 now. I do realize different people have
>>other criteria/priorities, but we've been using Hibenate 2.1betas with
>>Spring since August, with no issues, and ideally would want to move to
>>the final version.
>>
>>My feeling is that most Hibernate users have already switched to 2.1, or
>>will do so very soon, as there are no backwards compatibility issues
>>with doing so, and some strong advantages.
>>
>>
>>jürgen höller [werk3AT] wrote:
>>
>>    
>>
>>>Everybody,
>>>
>>>Hibernate 2.1 final with CGLIB2 underneath has just been released. This
>>>      
>>>
>poses the question whether we should still release our 1.0 M4 with CGLIB1
>support. Of course, our current codebase works nicely with Hibernate 2.1 as
>long as you don't use CGLIB-based AOP proxies (i.e. proxy full target
>objects instead of just interfaces), so we don't *have* to update
>immediately.
>  
>
>>>Migrating our AOP proxy generation to CGLIB2 should be straightforward.
>>>      
>>>
>Afterwards, it will be the other way round in terms of compatibility:
>Hibernate 2.0 will still work with a current Spring release as long as you
>don't use CGLIB-based AOP proxies. In any case, the most important rule is
>to just have the CGLIB version needed by your Hibernate version in the class
>path.
>  
>
>>>CGLIB2 is at RC1 in the meantime, so building on it now would be viable.
>>>      
>>>
>In the face of this situation, does everybody still prefer deferred CGLIB2
>support at the time of our RC1? I vote for migrating already in M4, to allow
>for CGLIB-based AOP proxies in combination with Hibernate 2.1 promptly.
>After all, typical Spring users will choose to work with the most current
>recommended Hibernate version.
>  
>
>>>Not that this was a really important criterion, but nevertheless: Chris,
>>>      
>>>
>when do you expect CGLIB2 final?
>  
>
>>>Juergen
>>>
>>>
>>>-----Original Message-----
>>>From: spr...@li...
>>>[mailto:spr...@li...]On Behalf
>>>Of Alef Arendsen (JTeam)
>>>Sent: Wednesday, December 03, 2003 11:20 PM
>>>To: spr...@li...
>>>Subject: About CGLIB2 (was: RE: [Springframework-developer] Release
>>>plan)
>>>
>>>
>>>Juergen (et al),
>>>
>>>So the current plan is:
>>>
>>>- M4  (CGLIB1): just before X-mas
>>>- RC1 (CGLIB2): 2nd week of January or something.
>>>
>>>Is there any idea on when CGLIB2 support is to be introduced (I heard
>>>supporting both of them at a time is a hassle or at least too much
>>>work). We've currently got a project (Spring + Hibernate 2.1) underway
>>>of which a initial release is targetted for the 12th of January.
>>>
>>>Are there going to be significant changes when moving from CGLIB1 to 2
>>>(which will force me to stick with M4 for that particular project) or is
>>>it going to be a smooth transition without much impact?
>>>
>>>Thanks!
>>>
>>>Alef
>>>
>>>
>>>
>>>      
>>>
>>>>-----Oorspronkelijk bericht-----
>>>>Van: spr...@li...
>>>>[mailto:spr...@li...]
>>>>Namens jürgen höller [werk3AT]
>>>>Verzonden: Tuesday, December 02, 2003 3:27 PM
>>>>Aan: spr...@li...
>>>>Onderwerp: [Springframework-developer] Release plan
>>>>
>>>>
>>>>Guys,
>>>>
>>>>We need to settle on a concrete roadmap.
>>>>
>>>>Despite our initial plans to go straight to RC1, I'm inclined
>>>>to vote for an M4 in two weeks' time, with the significant
>>>>reworkings that have been introduced in the meantime (in the
>>>>bean factory and AOP area), with the current state of the
>>>>docs, and still with CGLIB1. We can also introduce our
>>>>JPetStore version with that release.
>>>>
>>>>I suggest to target RC1 for early January then, with CGLIB2
>>>>and - most importantly - a proper reference manual. In the
>>>>ideal case, 1.0 final could be ready at the end of January.
>>>>M4 would correspond to a feature freeze, with full
>>>>concentration on bugfixes and docs afterwards. RC1 should
>>>>already be as good as it gets, a true "release candidate".
>>>>
>>>>Juergen
>>>>
>>>>
>>>>-----Original Message-----
>>>>From: spr...@li...
>>>>[mailto:spr...@li...]
>>>>On Behalf Of Matthew E. Porter
>>>>Sent: Monday, December 01, 2003 6:37 PM
>>>>To: spr...@li...
>>>>Subject: Re: [Springframework-developer] Hibernate 2.1 and CGLIB
>>>>
>>>>
>>>>This was a good answer since it provides a roadmap.  Can someone post
>>>>this on the wiki or the website for others who may have the same
>>>>question?
>>>>
>>>>
>>>>Cheers,
>>>>  matthew
>>>>
>>>>On Dec 1, 2003, at 11:04 AM, jürgen höller [werk3AT] wrote:
>>>>
>>>>
>>>>
>>>>        
>>>>
>>>>>Hi Matthew,
>>>>>
>>>>>We've been discussing that for a while. If Hibernate 2.1 gets final
>>>>>early enough (and it seems to, being already in RC1 stage), we will
>>>>>switch to it for our 1.0 RCs. If 2.1 would still be far
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>from final, we
>>>      
>>>
>>>>        
>>>>
>>>>>would probably have to support both CGLIB1 and CGLIB2 somehow.
>>>>>Fortunately, that seems not to be necessary anymore!
>>>>>
>>>>>For the time being, if you don't proxy full classes (but just
>>>>>interfaces) or don't use Spring AOP in the first place, you
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>should be
>>>>
>>>>
>>>>        
>>>>
>>>>>able to work with Hibernate 2.1 and its CGLIB2 without hassle. The
>>>>>same will apply to Hibernate 2.0 users after we've moved to CGLIB2:
>>>>>You don't need to worry if you don't use Spring AOP will
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>full proxies.
>>>>
>>>>
>>>>        
>>>>
>>>>>I think we can live with requiring an update to Hibernate 2.1 if a
>>>>>user wants full AOP proxies in combination. Actually, we probably
>>>>>*need* to move to CGLIB2 once Hibernate 2.1 final is
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>released: Power
>>>>
>>>>
>>>>        
>>>>
>>>>>users will want to combine full Spring AOP proxying with
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>the current
>>>>
>>>>
>>>>        
>>>>
>>>>>Hibernate version, not with a previous one.
>>>>>
>>>>>Now it would be really great if CGLIB2 were final too until
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>Spring 1.0
>>>>
>>>>
>>>>        
>>>>
>>>>>final! :-) It's no problem to ship a CGLIB2 beta with our upcoming
>>>>>Spring 1.0 RC1, but it worries me to include a CGLIB2 beta
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>in Spring
>>>>
>>>>
>>>>        
>>>>
>>>>>1.0 final. Haven't the Hibernate guys the same problem? Or are they
>>>>>fine with shipping a CGLIB2 beta with Hibernate 2.1 final?
>>>>>
>>>>>So I suggest to release our 1.0 RC1 shortly after Hibernate
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>2.1 final,
>>>>
>>>>
>>>>        
>>>>
>>>>>already with CGLIB2 support. As I said, we will just force
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>users with
>>>>
>>>>
>>>>        
>>>>
>>>>>full AOP proxies to upgrade to Hibernate 2.1 if using the two in
>>>>>combination. We could release a 1.0 M4 shortly before that though,
>>>>>still with CGLIB1 - to ease migration paths for Hibernate 2.0 users.
>>>>>
>>>>>Juergen
>>>>>
>>>>>
>>>>>-----Original Message-----
>>>>>From: spr...@li...
>>>>>[mailto:spr...@li...]On
>>>>>Behalf Of Matthew E. Porter
>>>>>Sent: Monday, December 01, 2003 5:06 PM
>>>>>To: spr...@li...
>>>>>Subject: [Springframework-developer] Hibernate 2.1 and CGLIB
>>>>>
>>>>>
>>>>>I have looked through the mailing list archives but was
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>unable to find
>>>>
>>>>
>>>>        
>>>>
>>>>>the answer to my question.  Will Spring move to support
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>Hibernate 2.1
>>>>
>>>>
>>>>        
>>>>
>>>>>(as it is the new *recommended* version) and, if so, when?
>>>>>
>>>>>Also, does anyone know if I can use it now with the cglib version
>>>>>change?
>>>>>
>>>>>
>>>>>
>>>>>Cheers,
>>>>>  matthew
>>>>>
>>>>>
>>>>>
>>>>>          
>>>>>
>>
>>
>>-------------------------------------------------------
>>This SF.net email is sponsored by: IBM Linux Tutorials.
>>Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
>>Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
>>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
>>_______________________________________________
>>Springframework-developer mailing list
>>Spr...@li...
>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>    
>>
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: IBM Linux Tutorials.
>Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
>Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
>Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>  
>

Re: [Springframework-developer] RE: About CGLIB2

[<tri...@tr...>]

+1

Thomas

Quoting Colin Sampaleanu <col...@ex...>:

> I vote for updating to cglib2 now. I do realize different people have 
> other criteria/priorities, but we've been using Hibenate 2.1betas with 
> Spring since August, with no issues, and ideally would want to move to 
> the final version.
> 
> My feeling is that most Hibernate users have already switched to 2.1, or 
> will do so very soon, as there are no backwards compatibility issues 
> with doing so, and some strong advantages.
> 
> 
> jürgen höller [werk3AT] wrote:
> 
> >Everybody,
> >
> >Hibernate 2.1 final with CGLIB2 underneath has just been released. This
> poses the question whether we should still release our 1.0 M4 with CGLIB1
> support. Of course, our current codebase works nicely with Hibernate 2.1 as
> long as you don't use CGLIB-based AOP proxies (i.e. proxy full target objects
> instead of just interfaces), so we don't *have* to update immediately.
> >
> >Migrating our AOP proxy generation to CGLIB2 should be straightforward.
> Afterwards, it will be the other way round in terms of compatibility:
> Hibernate 2.0 will still work with a current Spring release as long as you
> don't use CGLIB-based AOP proxies. In any case, the most important rule is to
> just have the CGLIB version needed by your Hibernate version in the class
> path.
> >
> >CGLIB2 is at RC1 in the meantime, so building on it now would be viable. In
> the face of this situation, does everybody still prefer deferred CGLIB2
> support at the time of our RC1? I vote for migrating already in M4, to allow
> for CGLIB-based AOP proxies in combination with Hibernate 2.1 promptly. After
> all, typical Spring users will choose to work with the most current
> recommended Hibernate version.
> >
> >Not that this was a really important criterion, but nevertheless: Chris,
> when do you expect CGLIB2 final?
> >
> >Juergen
> >
> >
> >-----Original Message-----
> >From: spr...@li...
> >[mailto:spr...@li...]On Behalf
> >Of Alef Arendsen (JTeam)
> >Sent: Wednesday, December 03, 2003 11:20 PM
> >To: spr...@li...
> >Subject: About CGLIB2 (was: RE: [Springframework-developer] Release
> >plan)
> >
> >
> >Juergen (et al),
> >
> >So the current plan is:
> >
> >- M4  (CGLIB1): just before X-mas
> >- RC1 (CGLIB2): 2nd week of January or something.
> >
> >Is there any idea on when CGLIB2 support is to be introduced (I heard
> >supporting both of them at a time is a hassle or at least too much
> >work). We've currently got a project (Spring + Hibernate 2.1) underway
> >of which a initial release is targetted for the 12th of January.
> >
> >Are there going to be significant changes when moving from CGLIB1 to 2
> >(which will force me to stick with M4 for that particular project) or is
> >it going to be a smooth transition without much impact?
> >
> >Thanks!
> >
> >Alef
> >
> >  
> >
> >>-----Oorspronkelijk bericht-----
> >>Van: spr...@li... 
> >>[mailto:spr...@li...]
> >> Namens jürgen höller [werk3AT]
> >>Verzonden: Tuesday, December 02, 2003 3:27 PM
> >>Aan: spr...@li...
> >>Onderwerp: [Springframework-developer] Release plan
> >>
> >>
> >>Guys,
> >>
> >>We need to settle on a concrete roadmap.
> >>
> >>Despite our initial plans to go straight to RC1, I'm inclined 
> >>to vote for an M4 in two weeks' time, with the significant 
> >>reworkings that have been introduced in the meantime (in the 
> >>bean factory and AOP area), with the current state of the 
> >>docs, and still with CGLIB1. We can also introduce our 
> >>JPetStore version with that release.
> >>
> >>I suggest to target RC1 for early January then, with CGLIB2 
> >>and - most importantly - a proper reference manual. In the 
> >>ideal case, 1.0 final could be ready at the end of January. 
> >>M4 would correspond to a feature freeze, with full 
> >>concentration on bugfixes and docs afterwards. RC1 should 
> >>already be as good as it gets, a true "release candidate".
> >>
> >>Juergen
> >>
> >>
> >>-----Original Message-----
> >>From: spr...@li...
> >>[mailto:spr...@li...]
> >>On Behalf Of Matthew E. Porter
> >>Sent: Monday, December 01, 2003 6:37 PM
> >>To: spr...@li...
> >>Subject: Re: [Springframework-developer] Hibernate 2.1 and CGLIB
> >>
> >>
> >>This was a good answer since it provides a roadmap.  Can someone post 
> >>this on the wiki or the website for others who may have the same 
> >>question?
> >>
> >>
> >>Cheers,
> >>   matthew
> >>
> >>On Dec 1, 2003, at 11:04 AM, jürgen höller [werk3AT] wrote:
> >>
> >>    
> >>
> >>>Hi Matthew,
> >>>
> >>>We've been discussing that for a while. If Hibernate 2.1 gets final
> >>>early enough (and it seems to, being already in RC1 stage), we will 
> >>>switch to it for our 1.0 RCs. If 2.1 would still be far 
> >>>      
> >>>
> >>from final, we 
> >>    
> >>
> >>>would probably have to support both CGLIB1 and CGLIB2 somehow. 
> >>>Fortunately, that seems not to be necessary anymore!
> >>>
> >>>For the time being, if you don't proxy full classes (but just
> >>>interfaces) or don't use Spring AOP in the first place, you 
> >>>      
> >>>
> >>should be 
> >>    
> >>
> >>>able to work with Hibernate 2.1 and its CGLIB2 without hassle. The 
> >>>same will apply to Hibernate 2.0 users after we've moved to CGLIB2: 
> >>>You don't need to worry if you don't use Spring AOP will 
> >>>      
> >>>
> >>full proxies.
> >>    
> >>
> >>>I think we can live with requiring an update to Hibernate 2.1 if a
> >>>user wants full AOP proxies in combination. Actually, we probably 
> >>>*need* to move to CGLIB2 once Hibernate 2.1 final is 
> >>>      
> >>>
> >>released: Power 
> >>    
> >>
> >>>users will want to combine full Spring AOP proxying with 
> >>>      
> >>>
> >>the current 
> >>    
> >>
> >>>Hibernate version, not with a previous one.
> >>>
> >>>Now it would be really great if CGLIB2 were final too until 
> >>>      
> >>>
> >>Spring 1.0
> >>    
> >>
> >>>final! :-) It's no problem to ship a CGLIB2 beta with our upcoming 
> >>>Spring 1.0 RC1, but it worries me to include a CGLIB2 beta 
> >>>      
> >>>
> >>in Spring 
> >>    
> >>
> >>>1.0 final. Haven't the Hibernate guys the same problem? Or are they 
> >>>fine with shipping a CGLIB2 beta with Hibernate 2.1 final?
> >>>
> >>>So I suggest to release our 1.0 RC1 shortly after Hibernate 
> >>>      
> >>>
> >>2.1 final,
> >>    
> >>
> >>>already with CGLIB2 support. As I said, we will just force 
> >>>      
> >>>
> >>users with 
> >>    
> >>
> >>>full AOP proxies to upgrade to Hibernate 2.1 if using the two in 
> >>>combination. We could release a 1.0 M4 shortly before that though, 
> >>>still with CGLIB1 - to ease migration paths for Hibernate 2.0 users.
> >>>
> >>>Juergen
> >>>
> >>>
> >>>-----Original Message-----
> >>>From: spr...@li...
> >>>[mailto:spr...@li...]On 
> >>>Behalf Of Matthew E. Porter
> >>>Sent: Monday, December 01, 2003 5:06 PM
> >>>To: spr...@li...
> >>>Subject: [Springframework-developer] Hibernate 2.1 and CGLIB
> >>>
> >>>
> >>>I have looked through the mailing list archives but was 
> >>>      
> >>>
> >>unable to find 
> >>    
> >>
> >>>the answer to my question.  Will Spring move to support 
> >>>      
> >>>
> >>Hibernate 2.1 
> >>    
> >>
> >>>(as it is the new *recommended* version) and, if so, when?
> >>>
> >>>Also, does anyone know if I can use it now with the cglib version 
> >>>change?
> >>>
> >>>
> >>>
> >>>Cheers,
> >>>   matthew
> >>>
> >>>      
> >>>
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
> 

Re: [Springframework-developer] RE: About CGLIB2

[Rod J. <rod...@in...>]

Would this also mean doing away with BCEL for good (a good idea)?

----- Original Message -----=20
From: "Colin Sampaleanu" <col...@ex...>
To: <spr...@li...>
Sent: Thursday, December 11, 2003 3:24 PM
Subject: Re: [Springframework-developer] RE: About CGLIB2


> I vote for updating to cglib2 now. I do realize different people have
> other criteria/priorities, but we've been using Hibenate 2.1betas with
> Spring since August, with no issues, and ideally would want to move to
> the final version.
>
> My feeling is that most Hibernate users have already switched to 2.1, o=
r
> will do so very soon, as there are no backwards compatibility issues
> with doing so, and some strong advantages.
>
>
> j=FCrgen h=F6ller [werk3AT] wrote:
>
> >Everybody,
> >
> >Hibernate 2.1 final with CGLIB2 underneath has just been released. Thi=
s
poses the question whether we should still release our 1.0 M4 with CGLIB1
support. Of course, our current codebase works nicely with Hibernate 2.1 =
as
long as you don't use CGLIB-based AOP proxies (i.e. proxy full target
objects instead of just interfaces), so we don't *have* to update
immediately.
> >
> >Migrating our AOP proxy generation to CGLIB2 should be straightforward.
Afterwards, it will be the other way round in terms of compatibility:
Hibernate 2.0 will still work with a current Spring release as long as yo=
u
don't use CGLIB-based AOP proxies. In any case, the most important rule i=
s
to just have the CGLIB version needed by your Hibernate version in the cl=
ass
path.
> >
> >CGLIB2 is at RC1 in the meantime, so building on it now would be viabl=
e.
In the face of this situation, does everybody still prefer deferred CGLIB=
2
support at the time of our RC1? I vote for migrating already in M4, to al=
low
for CGLIB-based AOP proxies in combination with Hibernate 2.1 promptly.
After all, typical Spring users will choose to work with the most current
recommended Hibernate version.
> >
> >Not that this was a really important criterion, but nevertheless: Chri=
s,
when do you expect CGLIB2 final?
> >
> >Juergen
> >
> >
> >-----Original Message-----
> >From: spr...@li...
> >[mailto:spr...@li...]On Behal=
f
> >Of Alef Arendsen (JTeam)
> >Sent: Wednesday, December 03, 2003 11:20 PM
> >To: spr...@li...
> >Subject: About CGLIB2 (was: RE: [Springframework-developer] Release
> >plan)
> >
> >
> >Juergen (et al),
> >
> >So the current plan is:
> >
> >- M4  (CGLIB1): just before X-mas
> >- RC1 (CGLIB2): 2nd week of January or something.
> >
> >Is there any idea on when CGLIB2 support is to be introduced (I heard
> >supporting both of them at a time is a hassle or at least too much
> >work). We've currently got a project (Spring + Hibernate 2.1) underway
> >of which a initial release is targetted for the 12th of January.
> >
> >Are there going to be significant changes when moving from CGLIB1 to 2
> >(which will force me to stick with M4 for that particular project) or =
is
> >it going to be a smooth transition without much impact?
> >
> >Thanks!
> >
> >Alef
> >
> >
> >
> >>-----Oorspronkelijk bericht-----
> >>Van: spr...@li...
> >>[mailto:spr...@li...]
> >> Namens j=FCrgen h=F6ller [werk3AT]
> >>Verzonden: Tuesday, December 02, 2003 3:27 PM
> >>Aan: spr...@li...
> >>Onderwerp: [Springframework-developer] Release plan
> >>
> >>
> >>Guys,
> >>
> >>We need to settle on a concrete roadmap.
> >>
> >>Despite our initial plans to go straight to RC1, I'm inclined
> >>to vote for an M4 in two weeks' time, with the significant
> >>reworkings that have been introduced in the meantime (in the
> >>bean factory and AOP area), with the current state of the
> >>docs, and still with CGLIB1. We can also introduce our
> >>JPetStore version with that release.
> >>
> >>I suggest to target RC1 for early January then, with CGLIB2
> >>and - most importantly - a proper reference manual. In the
> >>ideal case, 1.0 final could be ready at the end of January.
> >>M4 would correspond to a feature freeze, with full
> >>concentration on bugfixes and docs afterwards. RC1 should
> >>already be as good as it gets, a true "release candidate".
> >>
> >>Juergen
> >>
> >>
> >>-----Original Message-----
> >>From: spr...@li...
> >>[mailto:spr...@li...]
> >>On Behalf Of Matthew E. Porter
> >>Sent: Monday, December 01, 2003 6:37 PM
> >>To: spr...@li...
> >>Subject: Re: [Springframework-developer] Hibernate 2.1 and CGLIB
> >>
> >>
> >>This was a good answer since it provides a roadmap.  Can someone post
> >>this on the wiki or the website for others who may have the same
> >>question?
> >>
> >>
> >>Cheers,
> >>   matthew
> >>
> >>On Dec 1, 2003, at 11:04 AM, j=FCrgen h=F6ller [werk3AT] wrote:
> >>
> >>
> >>
> >>>Hi Matthew,
> >>>
> >>>We've been discussing that for a while. If Hibernate 2.1 gets final
> >>>early enough (and it seems to, being already in RC1 stage), we will
> >>>switch to it for our 1.0 RCs. If 2.1 would still be far
> >>>
> >>>
> >>from final, we
> >>
> >>
> >>>would probably have to support both CGLIB1 and CGLIB2 somehow.
> >>>Fortunately, that seems not to be necessary anymore!
> >>>
> >>>For the time being, if you don't proxy full classes (but just
> >>>interfaces) or don't use Spring AOP in the first place, you
> >>>
> >>>
> >>should be
> >>
> >>
> >>>able to work with Hibernate 2.1 and its CGLIB2 without hassle. The
> >>>same will apply to Hibernate 2.0 users after we've moved to CGLIB2:
> >>>You don't need to worry if you don't use Spring AOP will
> >>>
> >>>
> >>full proxies.
> >>
> >>
> >>>I think we can live with requiring an update to Hibernate 2.1 if a
> >>>user wants full AOP proxies in combination. Actually, we probably
> >>>*need* to move to CGLIB2 once Hibernate 2.1 final is
> >>>
> >>>
> >>released: Power
> >>
> >>
> >>>users will want to combine full Spring AOP proxying with
> >>>
> >>>
> >>the current
> >>
> >>
> >>>Hibernate version, not with a previous one.
> >>>
> >>>Now it would be really great if CGLIB2 were final too until
> >>>
> >>>
> >>Spring 1.0
> >>
> >>
> >>>final! :-) It's no problem to ship a CGLIB2 beta with our upcoming
> >>>Spring 1.0 RC1, but it worries me to include a CGLIB2 beta
> >>>
> >>>
> >>in Spring
> >>
> >>
> >>>1.0 final. Haven't the Hibernate guys the same problem? Or are they
> >>>fine with shipping a CGLIB2 beta with Hibernate 2.1 final?
> >>>
> >>>So I suggest to release our 1.0 RC1 shortly after Hibernate
> >>>
> >>>
> >>2.1 final,
> >>
> >>
> >>>already with CGLIB2 support. As I said, we will just force
> >>>
> >>>
> >>users with
> >>
> >>
> >>>full AOP proxies to upgrade to Hibernate 2.1 if using the two in
> >>>combination. We could release a 1.0 M4 shortly before that though,
> >>>still with CGLIB1 - to ease migration paths for Hibernate 2.0 users.
> >>>
> >>>Juergen
> >>>
> >>>
> >>>-----Original Message-----
> >>>From: spr...@li...
> >>>[mailto:spr...@li...]On
> >>>Behalf Of Matthew E. Porter
> >>>Sent: Monday, December 01, 2003 5:06 PM
> >>>To: spr...@li...
> >>>Subject: [Springframework-developer] Hibernate 2.1 and CGLIB
> >>>
> >>>
> >>>I have looked through the mailing list archives but was
> >>>
> >>>
> >>unable to find
> >>
> >>
> >>>the answer to my question.  Will Spring move to support
> >>>
> >>>
> >>Hibernate 2.1
> >>
> >>
> >>>(as it is the new *recommended* version) and, if so, when?
> >>>
> >>>Also, does anyone know if I can use it now with the cglib version
> >>>change?
> >>>
> >>>
> >>>
> >>>Cheers,
> >>>   matthew
> >>>
> >>>
> >>>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM=
's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admi=
n.
> Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] RE: About CGLIB2

[Rod J. <rod...@in...>]

I think upgrading before M4 is probably best too. So I will have to modif=
y
the AOP proxy...not that it's particularly hard.

Chris, I guess I'd better take another look at your examples of how we co=
uld
do away with CGLIB "optimization" in favour of CGLIB2 lazy interceptors o=
r
whatever they're called. Is there any documentation on the changes in CGL=
IB
and how to take best advantage of them, besides your excellent emails her=
e
:-)

Regards,
Rod

----- Original Message -----=20
From: "Colin Sampaleanu" <col...@ex...>
To: <spr...@li...>
Sent: Thursday, December 11, 2003 3:24 PM
Subject: Re: [Springframework-developer] RE: About CGLIB2


> I vote for updating to cglib2 now. I do realize different people have
> other criteria/priorities, but we've been using Hibenate 2.1betas with
> Spring since August, with no issues, and ideally would want to move to
> the final version.
>
> My feeling is that most Hibernate users have already switched to 2.1, o=
r
> will do so very soon, as there are no backwards compatibility issues
> with doing so, and some strong advantages.
>
>
> j=FCrgen h=F6ller [werk3AT] wrote:
>
> >Everybody,
> >
> >Hibernate 2.1 final with CGLIB2 underneath has just been released. Thi=
s
poses the question whether we should still release our 1.0 M4 with CGLIB1
support. Of course, our current codebase works nicely with Hibernate 2.1 =
as
long as you don't use CGLIB-based AOP proxies (i.e. proxy full target
objects instead of just interfaces), so we don't *have* to update
immediately.
> >
> >Migrating our AOP proxy generation to CGLIB2 should be straightforward.
Afterwards, it will be the other way round in terms of compatibility:
Hibernate 2.0 will still work with a current Spring release as long as yo=
u
don't use CGLIB-based AOP proxies. In any case, the most important rule i=
s
to just have the CGLIB version needed by your Hibernate version in the cl=
ass
path.
> >
> >CGLIB2 is at RC1 in the meantime, so building on it now would be viabl=
e.
In the face of this situation, does everybody still prefer deferred CGLIB=
2
support at the time of our RC1? I vote for migrating already in M4, to al=
low
for CGLIB-based AOP proxies in combination with Hibernate 2.1 promptly.
After all, typical Spring users will choose to work with the most current
recommended Hibernate version.
> >
> >Not that this was a really important criterion, but nevertheless: Chri=
s,
when do you expect CGLIB2 final?
> >
> >Juergen
> >
> >
> >-----Original Message-----
> >From: spr...@li...
> >[mailto:spr...@li...]On Behal=
f
> >Of Alef Arendsen (JTeam)
> >Sent: Wednesday, December 03, 2003 11:20 PM
> >To: spr...@li...
> >Subject: About CGLIB2 (was: RE: [Springframework-developer] Release
> >plan)
> >
> >
> >Juergen (et al),
> >
> >So the current plan is:
> >
> >- M4  (CGLIB1): just before X-mas
> >- RC1 (CGLIB2): 2nd week of January or something.
> >
> >Is there any idea on when CGLIB2 support is to be introduced (I heard
> >supporting both of them at a time is a hassle or at least too much
> >work). We've currently got a project (Spring + Hibernate 2.1) underway
> >of which a initial release is targetted for the 12th of January.
> >
> >Are there going to be significant changes when moving from CGLIB1 to 2
> >(which will force me to stick with M4 for that particular project) or =
is
> >it going to be a smooth transition without much impact?
> >
> >Thanks!
> >
> >Alef
> >
> >
> >
> >>-----Oorspronkelijk bericht-----
> >>Van: spr...@li...
> >>[mailto:spr...@li...]
> >> Namens j=FCrgen h=F6ller [werk3AT]
> >>Verzonden: Tuesday, December 02, 2003 3:27 PM
> >>Aan: spr...@li...
> >>Onderwerp: [Springframework-developer] Release plan
> >>
> >>
> >>Guys,
> >>
> >>We need to settle on a concrete roadmap.
> >>
> >>Despite our initial plans to go straight to RC1, I'm inclined
> >>to vote for an M4 in two weeks' time, with the significant
> >>reworkings that have been introduced in the meantime (in the
> >>bean factory and AOP area), with the current state of the
> >>docs, and still with CGLIB1. We can also introduce our
> >>JPetStore version with that release.
> >>
> >>I suggest to target RC1 for early January then, with CGLIB2
> >>and - most importantly - a proper reference manual. In the
> >>ideal case, 1.0 final could be ready at the end of January.
> >>M4 would correspond to a feature freeze, with full
> >>concentration on bugfixes and docs afterwards. RC1 should
> >>already be as good as it gets, a true "release candidate".
> >>
> >>Juergen
> >>
> >>
> >>-----Original Message-----
> >>From: spr...@li...
> >>[mailto:spr...@li...]
> >>On Behalf Of Matthew E. Porter
> >>Sent: Monday, December 01, 2003 6:37 PM
> >>To: spr...@li...
> >>Subject: Re: [Springframework-developer] Hibernate 2.1 and CGLIB
> >>
> >>
> >>This was a good answer since it provides a roadmap.  Can someone post
> >>this on the wiki or the website for others who may have the same
> >>question?
> >>
> >>
> >>Cheers,
> >>   matthew
> >>
> >>On Dec 1, 2003, at 11:04 AM, j=FCrgen h=F6ller [werk3AT] wrote:
> >>
> >>
> >>
> >>>Hi Matthew,
> >>>
> >>>We've been discussing that for a while. If Hibernate 2.1 gets final
> >>>early enough (and it seems to, being already in RC1 stage), we will
> >>>switch to it for our 1.0 RCs. If 2.1 would still be far
> >>>
> >>>
> >>from final, we
> >>
> >>
> >>>would probably have to support both CGLIB1 and CGLIB2 somehow.
> >>>Fortunately, that seems not to be necessary anymore!
> >>>
> >>>For the time being, if you don't proxy full classes (but just
> >>>interfaces) or don't use Spring AOP in the first place, you
> >>>
> >>>
> >>should be
> >>
> >>
> >>>able to work with Hibernate 2.1 and its CGLIB2 without hassle. The
> >>>same will apply to Hibernate 2.0 users after we've moved to CGLIB2:
> >>>You don't need to worry if you don't use Spring AOP will
> >>>
> >>>
> >>full proxies.
> >>
> >>
> >>>I think we can live with requiring an update to Hibernate 2.1 if a
> >>>user wants full AOP proxies in combination. Actually, we probably
> >>>*need* to move to CGLIB2 once Hibernate 2.1 final is
> >>>
> >>>
> >>released: Power
> >>
> >>
> >>>users will want to combine full Spring AOP proxying with
> >>>
> >>>
> >>the current
> >>
> >>
> >>>Hibernate version, not with a previous one.
> >>>
> >>>Now it would be really great if CGLIB2 were final too until
> >>>
> >>>
> >>Spring 1.0
> >>
> >>
> >>>final! :-) It's no problem to ship a CGLIB2 beta with our upcoming
> >>>Spring 1.0 RC1, but it worries me to include a CGLIB2 beta
> >>>
> >>>
> >>in Spring
> >>
> >>
> >>>1.0 final. Haven't the Hibernate guys the same problem? Or are they
> >>>fine with shipping a CGLIB2 beta with Hibernate 2.1 final?
> >>>
> >>>So I suggest to release our 1.0 RC1 shortly after Hibernate
> >>>
> >>>
> >>2.1 final,
> >>
> >>
> >>>already with CGLIB2 support. As I said, we will just force
> >>>
> >>>
> >>users with
> >>
> >>
> >>>full AOP proxies to upgrade to Hibernate 2.1 if using the two in
> >>>combination. We could release a 1.0 M4 shortly before that though,
> >>>still with CGLIB1 - to ease migration paths for Hibernate 2.0 users.
> >>>
> >>>Juergen
> >>>
> >>>
> >>>-----Original Message-----
> >>>From: spr...@li...
> >>>[mailto:spr...@li...]On
> >>>Behalf Of Matthew E. Porter
> >>>Sent: Monday, December 01, 2003 5:06 PM
> >>>To: spr...@li...
> >>>Subject: [Springframework-developer] Hibernate 2.1 and CGLIB
> >>>
> >>>
> >>>I have looked through the mailing list archives but was
> >>>
> >>>
> >>unable to find
> >>
> >>
> >>>the answer to my question.  Will Spring move to support
> >>>
> >>>
> >>Hibernate 2.1
> >>
> >>
> >>>(as it is the new *recommended* version) and, if so, when?
> >>>
> >>>Also, does anyone know if I can use it now with the cglib version
> >>>change?
> >>>
> >>>
> >>>
> >>>Cheers,
> >>>   matthew
> >>>
> >>>
> >>>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM=
's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admi=
n.
> Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] RE: About CGLIB2

[Colin S. <col...@ex...>]

I vote for updating to cglib2 now. I do realize different people have 
other criteria/priorities, but we've been using Hibenate 2.1betas with 
Spring since August, with no issues, and ideally would want to move to 
the final version.

My feeling is that most Hibernate users have already switched to 2.1, or 
will do so very soon, as there are no backwards compatibility issues 
with doing so, and some strong advantages.


jürgen höller [werk3AT] wrote:

>Everybody,
>
>Hibernate 2.1 final with CGLIB2 underneath has just been released. This poses the question whether we should still release our 1.0 M4 with CGLIB1 support. Of course, our current codebase works nicely with Hibernate 2.1 as long as you don't use CGLIB-based AOP proxies (i.e. proxy full target objects instead of just interfaces), so we don't *have* to update immediately.
>
>Migrating our AOP proxy generation to CGLIB2 should be straightforward. Afterwards, it will be the other way round in terms of compatibility: Hibernate 2.0 will still work with a current Spring release as long as you don't use CGLIB-based AOP proxies. In any case, the most important rule is to just have the CGLIB version needed by your Hibernate version in the class path.
>
>CGLIB2 is at RC1 in the meantime, so building on it now would be viable. In the face of this situation, does everybody still prefer deferred CGLIB2 support at the time of our RC1? I vote for migrating already in M4, to allow for CGLIB-based AOP proxies in combination with Hibernate 2.1 promptly. After all, typical Spring users will choose to work with the most current recommended Hibernate version.
>
>Not that this was a really important criterion, but nevertheless: Chris, when do you expect CGLIB2 final?
>
>Juergen
>
>
>-----Original Message-----
>From: spr...@li...
>[mailto:spr...@li...]On Behalf
>Of Alef Arendsen (JTeam)
>Sent: Wednesday, December 03, 2003 11:20 PM
>To: spr...@li...
>Subject: About CGLIB2 (was: RE: [Springframework-developer] Release
>plan)
>
>
>Juergen (et al),
>
>So the current plan is:
>
>- M4  (CGLIB1): just before X-mas
>- RC1 (CGLIB2): 2nd week of January or something.
>
>Is there any idea on when CGLIB2 support is to be introduced (I heard
>supporting both of them at a time is a hassle or at least too much
>work). We've currently got a project (Spring + Hibernate 2.1) underway
>of which a initial release is targetted for the 12th of January.
>
>Are there going to be significant changes when moving from CGLIB1 to 2
>(which will force me to stick with M4 for that particular project) or is
>it going to be a smooth transition without much impact?
>
>Thanks!
>
>Alef
>
>  
>
>>-----Oorspronkelijk bericht-----
>>Van: spr...@li... 
>>[mailto:spr...@li...]
>> Namens jürgen höller [werk3AT]
>>Verzonden: Tuesday, December 02, 2003 3:27 PM
>>Aan: spr...@li...
>>Onderwerp: [Springframework-developer] Release plan
>>
>>
>>Guys,
>>
>>We need to settle on a concrete roadmap.
>>
>>Despite our initial plans to go straight to RC1, I'm inclined 
>>to vote for an M4 in two weeks' time, with the significant 
>>reworkings that have been introduced in the meantime (in the 
>>bean factory and AOP area), with the current state of the 
>>docs, and still with CGLIB1. We can also introduce our 
>>JPetStore version with that release.
>>
>>I suggest to target RC1 for early January then, with CGLIB2 
>>and - most importantly - a proper reference manual. In the 
>>ideal case, 1.0 final could be ready at the end of January. 
>>M4 would correspond to a feature freeze, with full 
>>concentration on bugfixes and docs afterwards. RC1 should 
>>already be as good as it gets, a true "release candidate".
>>
>>Juergen
>>
>>
>>-----Original Message-----
>>From: spr...@li...
>>[mailto:spr...@li...]
>>On Behalf Of Matthew E. Porter
>>Sent: Monday, December 01, 2003 6:37 PM
>>To: spr...@li...
>>Subject: Re: [Springframework-developer] Hibernate 2.1 and CGLIB
>>
>>
>>This was a good answer since it provides a roadmap.  Can someone post 
>>this on the wiki or the website for others who may have the same 
>>question?
>>
>>
>>Cheers,
>>   matthew
>>
>>On Dec 1, 2003, at 11:04 AM, jürgen höller [werk3AT] wrote:
>>
>>    
>>
>>>Hi Matthew,
>>>
>>>We've been discussing that for a while. If Hibernate 2.1 gets final
>>>early enough (and it seems to, being already in RC1 stage), we will 
>>>switch to it for our 1.0 RCs. If 2.1 would still be far 
>>>      
>>>
>>from final, we 
>>    
>>
>>>would probably have to support both CGLIB1 and CGLIB2 somehow. 
>>>Fortunately, that seems not to be necessary anymore!
>>>
>>>For the time being, if you don't proxy full classes (but just
>>>interfaces) or don't use Spring AOP in the first place, you 
>>>      
>>>
>>should be 
>>    
>>
>>>able to work with Hibernate 2.1 and its CGLIB2 without hassle. The 
>>>same will apply to Hibernate 2.0 users after we've moved to CGLIB2: 
>>>You don't need to worry if you don't use Spring AOP will 
>>>      
>>>
>>full proxies.
>>    
>>
>>>I think we can live with requiring an update to Hibernate 2.1 if a
>>>user wants full AOP proxies in combination. Actually, we probably 
>>>*need* to move to CGLIB2 once Hibernate 2.1 final is 
>>>      
>>>
>>released: Power 
>>    
>>
>>>users will want to combine full Spring AOP proxying with 
>>>      
>>>
>>the current 
>>    
>>
>>>Hibernate version, not with a previous one.
>>>
>>>Now it would be really great if CGLIB2 were final too until 
>>>      
>>>
>>Spring 1.0
>>    
>>
>>>final! :-) It's no problem to ship a CGLIB2 beta with our upcoming 
>>>Spring 1.0 RC1, but it worries me to include a CGLIB2 beta 
>>>      
>>>
>>in Spring 
>>    
>>
>>>1.0 final. Haven't the Hibernate guys the same problem? Or are they 
>>>fine with shipping a CGLIB2 beta with Hibernate 2.1 final?
>>>
>>>So I suggest to release our 1.0 RC1 shortly after Hibernate 
>>>      
>>>
>>2.1 final,
>>    
>>
>>>already with CGLIB2 support. As I said, we will just force 
>>>      
>>>
>>users with 
>>    
>>
>>>full AOP proxies to upgrade to Hibernate 2.1 if using the two in 
>>>combination. We could release a 1.0 M4 shortly before that though, 
>>>still with CGLIB1 - to ease migration paths for Hibernate 2.0 users.
>>>
>>>Juergen
>>>
>>>
>>>-----Original Message-----
>>>From: spr...@li...
>>>[mailto:spr...@li...]On 
>>>Behalf Of Matthew E. Porter
>>>Sent: Monday, December 01, 2003 5:06 PM
>>>To: spr...@li...
>>>Subject: [Springframework-developer] Hibernate 2.1 and CGLIB
>>>
>>>
>>>I have looked through the mailing list archives but was 
>>>      
>>>
>>unable to find 
>>    
>>
>>>the answer to my question.  Will Spring move to support 
>>>      
>>>
>>Hibernate 2.1 
>>    
>>
>>>(as it is the new *recommended* version) and, if so, when?
>>>
>>>Also, does anyone know if I can use it now with the cglib version 
>>>change?
>>>
>>>
>>>
>>>Cheers,
>>>   matthew
>>>
>>>      
>>>

[Springframework-developer] RE: About CGLIB2

[<jue...@we...>]

Everybody,

Hibernate 2.1 final with CGLIB2 underneath has just been released. This =
poses the question whether we should still release our 1.0 M4 with =
CGLIB1 support. Of course, our current codebase works nicely with =
Hibernate 2.1 as long as you don't use CGLIB-based AOP proxies (i.e. =
proxy full target objects instead of just interfaces), so we don't =
*have* to update immediately.

Migrating our AOP proxy generation to CGLIB2 should be straightforward. =
Afterwards, it will be the other way round in terms of compatibility: =
Hibernate 2.0 will still work with a current Spring release as long as =
you don't use CGLIB-based AOP proxies. In any case, the most important =
rule is to just have the CGLIB version needed by your Hibernate version =
in the class path.

CGLIB2 is at RC1 in the meantime, so building on it now would be viable. =
In the face of this situation, does everybody still prefer deferred =
CGLIB2 support at the time of our RC1? I vote for migrating already in =
M4, to allow for CGLIB-based AOP proxies in combination with Hibernate =
2.1 promptly. After all, typical Spring users will choose to work with =
the most current recommended Hibernate version.

Not that this was a really important criterion, but nevertheless: Chris, =
when do you expect CGLIB2 final?

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Alef Arendsen (JTeam)
Sent: Wednesday, December 03, 2003 11:20 PM
To: spr...@li...
Subject: About CGLIB2 (was: RE: [Springframework-developer] Release
plan)


Juergen (et al),

So the current plan is:

- M4  (CGLIB1): just before X-mas
- RC1 (CGLIB2): 2nd week of January or something.

Is there any idea on when CGLIB2 support is to be introduced (I heard
supporting both of them at a time is a hassle or at least too much
work). We've currently got a project (Spring + Hibernate 2.1) underway
of which a initial release is targetted for the 12th of January.

Are there going to be significant changes when moving from CGLIB1 to 2
(which will force me to stick with M4 for that particular project) or is
it going to be a smooth transition without much impact?

Thanks!

Alef

> -----Oorspronkelijk bericht-----
> Van: spr...@li...=20
> [mailto:spr...@li...]
>  Namens j=FCrgen h=F6ller [werk3AT]
> Verzonden: Tuesday, December 02, 2003 3:27 PM
> Aan: spr...@li...
> Onderwerp: [Springframework-developer] Release plan
>=20
>=20
> Guys,
>=20
> We need to settle on a concrete roadmap.
>=20
> Despite our initial plans to go straight to RC1, I'm inclined=20
> to vote for an M4 in two weeks' time, with the significant=20
> reworkings that have been introduced in the meantime (in the=20
> bean factory and AOP area), with the current state of the=20
> docs, and still with CGLIB1. We can also introduce our=20
> JPetStore version with that release.
>=20
> I suggest to target RC1 for early January then, with CGLIB2=20
> and - most importantly - a proper reference manual. In the=20
> ideal case, 1.0 final could be ready at the end of January.=20
> M4 would correspond to a feature freeze, with full=20
> concentration on bugfixes and docs afterwards. RC1 should=20
> already be as good as it gets, a true "release candidate".
>=20
> Juergen
>=20
>=20
> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...]
> On Behalf Of Matthew E. Porter
> Sent: Monday, December 01, 2003 6:37 PM
> To: spr...@li...
> Subject: Re: [Springframework-developer] Hibernate 2.1 and CGLIB
>=20
>=20
> This was a good answer since it provides a roadmap.  Can someone post=20
> this on the wiki or the website for others who may have the same=20
> question?
>=20
>=20
> Cheers,
>    matthew
>=20
> On Dec 1, 2003, at 11:04 AM, j=FCrgen h=F6ller [werk3AT] wrote:
>=20
> > Hi Matthew,
> >
> > We've been discussing that for a while. If Hibernate 2.1 gets final
> > early enough (and it seems to, being already in RC1 stage), we will=20
> > switch to it for our 1.0 RCs. If 2.1 would still be far=20
> from final, we=20
> > would probably have to support both CGLIB1 and CGLIB2 somehow.=20
> > Fortunately, that seems not to be necessary anymore!
> >
> > For the time being, if you don't proxy full classes (but just
> > interfaces) or don't use Spring AOP in the first place, you=20
> should be=20
> > able to work with Hibernate 2.1 and its CGLIB2 without hassle. The=20
> > same will apply to Hibernate 2.0 users after we've moved to CGLIB2:=20
> > You don't need to worry if you don't use Spring AOP will=20
> full proxies.
> >
> > I think we can live with requiring an update to Hibernate 2.1 if a
> > user wants full AOP proxies in combination. Actually, we probably=20
> > *need* to move to CGLIB2 once Hibernate 2.1 final is=20
> released: Power=20
> > users will want to combine full Spring AOP proxying with=20
> the current=20
> > Hibernate version, not with a previous one.
> >
> > Now it would be really great if CGLIB2 were final too until=20
> Spring 1.0
> > final! :-) It's no problem to ship a CGLIB2 beta with our upcoming=20
> > Spring 1.0 RC1, but it worries me to include a CGLIB2 beta=20
> in Spring=20
> > 1.0 final. Haven't the Hibernate guys the same problem? Or are they=20
> > fine with shipping a CGLIB2 beta with Hibernate 2.1 final?
> >
> > So I suggest to release our 1.0 RC1 shortly after Hibernate=20
> 2.1 final,
> > already with CGLIB2 support. As I said, we will just force=20
> users with=20
> > full AOP proxies to upgrade to Hibernate 2.1 if using the two in=20
> > combination. We could release a 1.0 M4 shortly before that though,=20
> > still with CGLIB1 - to ease migration paths for Hibernate 2.0 users.
> >
> > Juergen
> >
> >
> > -----Original Message-----
> > From: spr...@li...
> > [mailto:spr...@li...]On=20
> > Behalf Of Matthew E. Porter
> > Sent: Monday, December 01, 2003 5:06 PM
> > To: spr...@li...
> > Subject: [Springframework-developer] Hibernate 2.1 and CGLIB
> >
> >
> > I have looked through the mailing list archives but was=20
> unable to find=20
> > the answer to my question.  Will Spring move to support=20
> Hibernate 2.1=20
> > (as it is the new *recommended* version) and, if so, when?
> >
> > Also, does anyone know if I can use it now with the cglib version=20
> > change?
> >
> >
> >
> > Cheers,
> >    matthew
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: SF.net Giveback Program. Does=20
> > SourceForge.net help you be more productive?  Does it help=20
> you create=20
> > better code?  SHARE THE LOVE, and help us help YOU!  Click Here:=20
> > http://sourceforge.net/donate/=20
> > _______________________________________________
> > Springframework-developer mailing list=20
> > Spr...@li...
> >=20
> https://lists.sourceforge.net/lists/listinfo/s>
pringframework-developer
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: SF.net Giveback Program. Does=20
> > SourceForge.net help you be more productive?  Does it help=20
> you create=20
> > better code?  SHARE THE LOVE, and help us help YOU!  Click Here:=20
> > http://sourceforge.net/donate/=20
> > _______________________________________________
> > Springframework-developer mailing list=20
> > Spr...@li...
> >=20
> https://lists.sourceforge.net/lists/listinfo/s>
pringframework-developer
>=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
>=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



-------------------------------------------------------
This SF.net email is sponsored by OSDN's Audience Survey.
Help shape OSDN's sites and tell us what you think. Take this
five minute survey and you could win a $250 Gift Certificate.
http://www.wrgsurveys.com/2003/osdntech03.php?site=3D
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] Releasing Tests?

[Ken K. <kk...@kk...>]

+1

Ou, Rong wrote:

>Hi all,
>
>First time poster here. I've had Rod's book for a while, just haven't fi=
nished reading it yet. :) Which I plan to do during the holidays.
>
>I was a bit disappointed when I pulled down the m3 release and didn't fi=
nd any tests in it. Since we are all doing XP, agile, TDD now, isn't it h=
igh time that tests are released together with production code? It would =
be so much easier for newcomers to come up to speed with the framework ("=
Tests are documentation") and contribute new tests and patches (dealing w=
ith cvs is a lot of hassle from behind firewalls).
>
>Any thoughts?
>
>Rong
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: IBM Linux Tutorials.
>Become an expert in LINUX or just sharpen your skills.  Sign up for IBM'=
s
>Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=CCk
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
> =20
>

Re: [Springframework-developer] petclinic html

[Ken K. <kk...@kk...>]

+1

Darren Davison wrote:

>is anyone currently relying on the html that petclinic outputs for tests, or 
>parsing in some way?  I'd like to change a few pages structurally and 
>generally tidy the output so it's more test-friendly for httpunit.  None of 
>the functionality or URL's etc. will change.
>
>Cheers,
>  
>

Re: [Springframework-developer] Releasing Tests?

[Colin S. <col...@ex...>]

This is the solution I like. Somebody who is already using Spring and 
just wants to do a point upgrade or have an install image for use 
somewhere could pull down the light version. Somebody who really wants 
to learn Spring and get going with it would pull down the heavy version...

jürgen höller [werk3AT] wrote:

>I think that the difference isn't big enough to warrant separate releases just because of the tests. A more convincing option would be to ship a distribution that contains everything (even including tests) but just the minimum set of libraries (i.e. aop-alliance and commons-logging). No working samples, no compiling of framework sources.
> 
>That would result in a 7.5 MB "light edition", as opposed to >14 MB for the "full edition" with all libraries. I guess that many users would consider the "light edition" sufficient in that case: After all, it includes everything as sources plus pre-built framework libraries - just without the option to build samples, framework, or tests!
> 
>We could pursue that after M4 if we feel the need to, starting to offer two such distributions as of RC1. For the time being, a single 14 MB distribution should be fine, IMO.
> 
>Juergen
> 
>
>________________________________
>
>Von: spr...@li... im Auftrag von Alef Arendsen
>Gesendet: Do 11.12.2003 10:47
>An: spr...@li...
>Betreff: RE: [Springframework-developer] Releasing Tests?
>
>
>
>I think it's good to have the tests distributed as well, but maybe we
>could have two releases? One including the tests, one not including the
>tests (or does this result in too much work)...
>
>
>-----Original Message-----
>From: spr...@li...
>[mailto:spr...@li...] On Behalf
>Of jürgen höller [werk3AT]
>Sent: Thursday, December 11, 2003 10:41 AM
>To: spr...@li...
>Subject: Re: [Springframework-developer] Releasing Tests?
>
>
>I'm inclined to agree, but this implies a further issue: To be able to
>compile all the tests and the framework sources in the first place, we
>need to ship all the libraries that we depend on. We're talking about
>additional 1.6 MB of libs here (excluding Xerces and Clover). The test
>sources amount to 1.3 MB themselves (400 KB zipped). So in total, around
>2 MB increase in distribution size: from 12.1 MB (M3 + JPetStore) to
>14.1 MB. If we agree to accept that, I'll be happy to include the tests
>in the upcoming release.
>
>Juergen
>
>
>________________________________
>
>Von: spr...@li... im Auftrag
>von Rod Johnson
>Gesendet: Do 11.12.2003 10:06
>An: spr...@li...
>Betreff: Re: [Springframework-developer] Releasing Tests?
>
>
>
>I agree with Rong. I think we should include tests in M4.
>
>Regards,
>Rod
>
>----- Original Message -----
>From: "Ou, Rong" <Ro...@sa...>
>To: <spr...@li...>
>Sent: Wednesday, December 10, 2003 9:43 PM
>Subject: [Springframework-developer] Releasing Tests?
>
>
>Hi all,
>
>First time poster here. I've had Rod's book for a while, just haven't
>finished reading it yet. :) Which I plan to do during the holidays.
>
>I was a bit disappointed when I pulled down the m3 release and didn't
>find any tests in it. Since we are all doing XP, agile, TDD now, isn't
>it high time that tests are released together with production code? It
>would be so much easier for newcomers to come up to speed with the
>framework ("Tests are
>documentation") and contribute new tests and patches (dealing with cvs
>is a lot of hassle from behind firewalls).
>
>Any thoughts?
>
>Rong
>  
>

Re: [Springframework-developer] Releasing Tests?

[Rod J. <rod...@in...>]

Of course publishing the tests means we'll have to ensure they're
intelligible to users. But of course that's no bad thing.

----- Original Message ----- 
From: "Darren Davison" <dda...@kg...>
To: <spr...@li...>
Sent: Thursday, December 11, 2003 12:40 PM
Subject: Re: [Springframework-developer] Releasing Tests?


>
> > Furthermore, I believe that the samples are important particularly
> > for "just want to use it" people. After all, polished examples are a
> > good companion to proper framework documentation, easing the entry
> > into the framework rather than making it more complex, IMO.
>
> sorry if I wasn't clear originally - I was certainly advocating that the
> samples *should* form a part of all release versions.
>
> Regards,
>
>
> --
> Darren Davison
> Public Key: http://www.davison.uk.net/key.jsp
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>

Re: [Springframework-developer] Releasing Tests?

[Darren D. <dda...@kg...>]

> Furthermore, I believe that the samples are important particularly 
> for "just want to use it" people. After all, polished examples are a 
> good companion to proper framework documentation, easing the entry 
> into the framework rather than making it more complex, IMO.

sorry if I wasn't clear originally - I was certainly advocating that the
samples *should* form a part of all release versions.

Regards,


--
Darren Davison
Public Key: http://www.davison.uk.net/key.jsp

Re: [Springframework-developer] Releasing Tests?

[Janek B. <ya...@st...>]

On Thu, 2003-12-11 at 05:40, j=C3=BCrgen h=C3=B6ller [werk3AT] wrote:
> Darren,
> =20
> I'm not sure if the samples add any complexity, but I think you're right =
about the test tree. So I suggest to refine the "light edition" from my las=
t mail to a 7.1 MB one with pre-built binaries, docs, framework sources, sa=
mple sources, but without tests and just the minimum set of third-party lib=
raries.
> =20
> I think that it's very helpful to include framework sources in your IDE, =
to get better argument naming when overriding methods, quick navigation to =
sources of framework base classes, etc. I do that all the time with the JDK=
 and Hibernate; so do my werk3AT colleagues. And after all, Sun is shipping=
 the JDK with sources included - you just need to download the docs separat=
ely there. Hibernate and Log4J ship with out-of-the-box sources too.
> =20
> Furthermore, I believe that the samples are important particularly for "j=
ust want to use it" people. After all, polished examples are a good compani=
on to proper framework documentation, easing the entry into the framework r=
ather than making it more complex, IMO.
> =20
> Juergen
> =20

As a new user of the framework I am finding it very useful to have the
sources available within the IDE. It is often easier to search the=20
sources to establish facts about the framework than to use the external
documentation.

On the size issue, as a 28.8k modem user (at one location) the size of
downloads (JBoss, JDKs) is an issue I normally solve by burning CD-Rs or
using USB drives at another location. So an few extra megabytes won't
affect me and shouldn't really be a consideration as I would guess other
users in a similar situation use a similar tactic with large downloads.=20

-Janek

Re: [Springframework-developer] Releasing Tests?

[<jue...@we...>]

Darren,
=20
I'm not sure if the samples add any complexity, but I think you're right =
about the test tree. So I suggest to refine the "light edition" from my =
last mail to a 7.1 MB one with pre-built binaries, docs, framework =
sources, sample sources, but without tests and just the minimum set of =
third-party libraries.
=20
I think that it's very helpful to include framework sources in your IDE, =
to get better argument naming when overriding methods, quick navigation =
to sources of framework base classes, etc. I do that all the time with =
the JDK and Hibernate; so do my werk3AT colleagues. And after all, Sun =
is shipping the JDK with sources included - you just need to download =
the docs separately there. Hibernate and Log4J ship with out-of-the-box =
sources too.
=20
Furthermore, I believe that the samples are important particularly for =
"just want to use it" people. After all, polished examples are a good =
companion to proper framework documentation, easing the entry into the =
framework rather than making it more complex, IMO.
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von Rod Johnson
Gesendet: Do 11.12.2003 11:28
An: spr...@li...
Betreff: Re: [Springframework-developer] Releasing Tests?



I think we need a binary release also when we release 1.0 final.

----- Original Message -----
From: "Darren Davison" <dda...@kg...>
To: <spr...@li...>
Sent: Thursday, December 11, 2003 10:25 AM
Subject: Re: [Springframework-developer] Releasing Tests?


> > Or the second release could just be the binaries. But I'm inclined
> > to agree with Mike that people don't much care about size of
> > download. Does anyone really download Spring over a modem? So I
> > would just stick with the single 14Mb download: it's a modest =
increase.
>
> I don't think it's so much the file size as the perceived complexity.
Opening
> the zip and seeing an enormous test tree along side the main source =
tree
and
> all the samples could make you think "boy, I don't have time to learn =
all
this
> stuff".
>
> A smaller download with just the vitals and some good doco can be a =
big
aide
> in promoting takeup among those who "just want to use it".  It's =
purely a
> mindset thing - I'm not suggesting that the additional increase in the =
zip
> really does add any complexity.  The argument perhaps makes a stronger
case
> too for a binary only file release which I'd also like to see.
>
> We could always give it a go and if the SF d/l stats show there's =
really
no
> need for the cut down versions, we can stop building them.
>
> --
> Darren Davison
> Public Key: http://www.davison.uk.net/key.jsp
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for =
IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys =
admin.
> Click now! =
http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for =
IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys =
admin.
Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] Releasing Tests?

[<jue...@we...>]

I think that the difference isn't big enough to warrant separate =
releases just because of the tests. A more convincing option would be to =
ship a distribution that contains everything (even including tests) but =
just the minimum set of libraries (i.e. aop-alliance and =
commons-logging). No working samples, no compiling of framework sources.
=20
That would result in a 7.5 MB "light edition", as opposed to >14 MB for =
the "full edition" with all libraries. I guess that many users would =
consider the "light edition" sufficient in that case: After all, it =
includes everything as sources plus pre-built framework libraries - just =
without the option to build samples, framework, or tests!
=20
We could pursue that after M4 if we feel the need to, starting to offer =
two such distributions as of RC1. For the time being, a single 14 MB =
distribution should be fine, IMO.
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von Alef Arendsen
Gesendet: Do 11.12.2003 10:47
An: spr...@li...
Betreff: RE: [Springframework-developer] Releasing Tests?



I think it's good to have the tests distributed as well, but maybe we
could have two releases? One including the tests, one not including the
tests (or does this result in too much work)...


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf
Of j=FCrgen h=F6ller [werk3AT]
Sent: Thursday, December 11, 2003 10:41 AM
To: spr...@li...
Subject: Re: [Springframework-developer] Releasing Tests?


I'm inclined to agree, but this implies a further issue: To be able to
compile all the tests and the framework sources in the first place, we
need to ship all the libraries that we depend on. We're talking about
additional 1.6 MB of libs here (excluding Xerces and Clover). The test
sources amount to 1.3 MB themselves (400 KB zipped). So in total, around
2 MB increase in distribution size: from 12.1 MB (M3 + JPetStore) to
14.1 MB. If we agree to accept that, I'll be happy to include the tests
in the upcoming release.

Juergen


________________________________

Von: spr...@li... im Auftrag
von Rod Johnson
Gesendet: Do 11.12.2003 10:06
An: spr...@li...
Betreff: Re: [Springframework-developer] Releasing Tests?



I agree with Rong. I think we should include tests in M4.

Regards,
Rod

----- Original Message -----
From: "Ou, Rong" <Ro...@sa...>
To: <spr...@li...>
Sent: Wednesday, December 10, 2003 9:43 PM
Subject: [Springframework-developer] Releasing Tests?


Hi all,

First time poster here. I've had Rod's book for a while, just haven't
finished reading it yet. :) Which I plan to do during the holidays.

I was a bit disappointed when I pulled down the m3 release and didn't
find any tests in it. Since we are all doing XP, agile, TDD now, isn't
it high time that tests are released together with production code? It
would be so much easier for newcomers to come up to speed with the
framework ("Tests are
documentation") and contribute new tests and patches (dealing with cvs
is a lot of hassle from behind firewalls).

Any thoughts?

Rong


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for
IBM's Free Linux Tutorials.  Learn everything from the bash shell to sys
admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for
IBM's Free Linux Tutorials.  Learn everything from the bash shell to sys
admin. Click now! =
http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for
IBM's Free Linux Tutorials.  Learn everything from the bash shell to sys
admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for =
IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys =
admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] Releasing Tests?

[Rod J. <rod...@in...>]

I think we need a binary release also when we release 1.0 final.

----- Original Message ----- 
From: "Darren Davison" <dda...@kg...>
To: <spr...@li...>
Sent: Thursday, December 11, 2003 10:25 AM
Subject: Re: [Springframework-developer] Releasing Tests?


> > Or the second release could just be the binaries. But I'm inclined
> > to agree with Mike that people don't much care about size of
> > download. Does anyone really download Spring over a modem? So I
> > would just stick with the single 14Mb download: it's a modest increase.
>
> I don't think it's so much the file size as the perceived complexity.
Opening
> the zip and seeing an enormous test tree along side the main source tree
and
> all the samples could make you think "boy, I don't have time to learn all
this
> stuff".
>
> A smaller download with just the vitals and some good doco can be a big
aide
> in promoting takeup among those who "just want to use it".  It's purely a
> mindset thing - I'm not suggesting that the additional increase in the zip
> really does add any complexity.  The argument perhaps makes a stronger
case
> too for a binary only file release which I'd also like to see.
>
> We could always give it a go and if the SF d/l stats show there's really
no
> need for the cut down versions, we can stop building them.
>
> --
> Darren Davison
> Public Key: http://www.davison.uk.net/key.jsp
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>

Re: [Springframework-developer] Releasing Tests?

[Darren D. <dda...@kg...>]

> Or the second release could just be the binaries. But I'm inclined 
> to agree with Mike that people don't much care about size of 
> download. Does anyone really download Spring over a modem? So I 
> would just stick with the single 14Mb download: it's a modest increase.

I don't think it's so much the file size as the perceived complexity.  Opening
the zip and seeing an enormous test tree along side the main source tree and
all the samples could make you think "boy, I don't have time to learn all this
stuff".

A smaller download with just the vitals and some good doco can be a big aide
in promoting takeup among those who "just want to use it".  It's purely a
mindset thing - I'm not suggesting that the additional increase in the zip
really does add any complexity.  The argument perhaps makes a stronger case
too for a binary only file release which I'd also like to see.

We could always give it a go and if the SF d/l stats show there's really no
need for the cut down versions, we can stop building them.

--
Darren Davison
Public Key: http://www.davison.uk.net/key.jsp

RE: [Springframework-developer] Releasing Tests?

[Darren D. <dda...@kg...>]

> I think it's good to have the tests distributed as well, but maybe we
> could have two releases? One including the tests, one not including the
> tests (or does this result in too much work)...

I agree - I suggested this a while back too.  My impression is that the
majority of people want a usable but minimal release (with samples) and online
documentation.  Those who want the tests and any extra stuff can grab a
different release.  As we pass 1.0 final, the group wanting the former type of
release will become significantly larger.

There's no issue with SF's storage limits is there? - at least not judging by
the amount the jboss project uses there isn't - so it should only require a
change to the main build.xml to create the additional zip(s).

Regards,
--
Darren Davison
Public Key: http://www.davison.uk.net/key.jsp

Re: [Springframework-developer] Releasing Tests?

[Rod J. <rod...@in...>]

Or the second release could just be the binaries. But I'm inclined to agr=
ee
with Mike that people don't much care about size of download. Does anyone
really download Spring over a modem? So I would just stick with the singl=
e
14Mb download: it's a modest increase.

Rod

----- Original Message -----=20
From: "Alef Arendsen" <al...@jt...>
To: <spr...@li...>
Sent: Thursday, December 11, 2003 9:47 AM
Subject: RE: [Springframework-developer] Releasing Tests?


I think it's good to have the tests distributed as well, but maybe we
could have two releases? One including the tests, one not including the
tests (or does this result in too much work)...


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf
Of j=FCrgen h=F6ller [werk3AT]
Sent: Thursday, December 11, 2003 10:41 AM
To: spr...@li...
Subject: Re: [Springframework-developer] Releasing Tests?


I'm inclined to agree, but this implies a further issue: To be able to
compile all the tests and the framework sources in the first place, we
need to ship all the libraries that we depend on. We're talking about
additional 1.6 MB of libs here (excluding Xerces and Clover). The test
sources amount to 1.3 MB themselves (400 KB zipped). So in total, around
2 MB increase in distribution size: from 12.1 MB (M3 + JPetStore) to
14.1 MB. If we agree to accept that, I'll be happy to include the tests
in the upcoming release.

Juergen


________________________________

Von: spr...@li... im Auftrag
von Rod Johnson
Gesendet: Do 11.12.2003 10:06
An: spr...@li...
Betreff: Re: [Springframework-developer] Releasing Tests?



I agree with Rong. I think we should include tests in M4.

Regards,
Rod

----- Original Message -----
From: "Ou, Rong" <Ro...@sa...>
To: <spr...@li...>
Sent: Wednesday, December 10, 2003 9:43 PM
Subject: [Springframework-developer] Releasing Tests?


Hi all,

First time poster here. I've had Rod's book for a while, just haven't
finished reading it yet. :) Which I plan to do during the holidays.

I was a bit disappointed when I pulled down the m3 release and didn't
find any tests in it. Since we are all doing XP, agile, TDD now, isn't
it high time that tests are released together with production code? It
would be so much easier for newcomers to come up to speed with the
framework ("Tests are
documentation") and contribute new tests and patches (dealing with cvs
is a lot of hassle from behind firewalls).

Any thoughts?

Rong


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for
IBM's Free Linux Tutorials.  Learn everything from the bash shell to sys
admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for
IBM's Free Linux Tutorials.  Learn everything from the bash shell to sys
admin. Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3D=
click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for
IBM's Free Linux Tutorials.  Learn everything from the bash shell to sys
admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

RE: [Springframework-developer] Releasing Tests?

[Alef A. <al...@jt...>]

I think it's good to have the tests distributed as well, but maybe we
could have two releases? One including the tests, one not including the
tests (or does this result in too much work)...


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf
Of j=FCrgen h=F6ller [werk3AT]
Sent: Thursday, December 11, 2003 10:41 AM
To: spr...@li...
Subject: Re: [Springframework-developer] Releasing Tests?


I'm inclined to agree, but this implies a further issue: To be able to
compile all the tests and the framework sources in the first place, we
need to ship all the libraries that we depend on. We're talking about
additional 1.6 MB of libs here (excluding Xerces and Clover). The test
sources amount to 1.3 MB themselves (400 KB zipped). So in total, around
2 MB increase in distribution size: from 12.1 MB (M3 + JPetStore) to
14.1 MB. If we agree to accept that, I'll be happy to include the tests
in the upcoming release.
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag
von Rod Johnson
Gesendet: Do 11.12.2003 10:06
An: spr...@li...
Betreff: Re: [Springframework-developer] Releasing Tests?



I agree with Rong. I think we should include tests in M4.

Regards,
Rod

----- Original Message -----
From: "Ou, Rong" <Ro...@sa...>
To: <spr...@li...>
Sent: Wednesday, December 10, 2003 9:43 PM
Subject: [Springframework-developer] Releasing Tests?


Hi all,

First time poster here. I've had Rod's book for a while, just haven't
finished reading it yet. :) Which I plan to do during the holidays.

I was a bit disappointed when I pulled down the m3 release and didn't
find any tests in it. Since we are all doing XP, agile, TDD now, isn't
it high time that tests are released together with production code? It
would be so much easier for newcomers to come up to speed with the
framework ("Tests are
documentation") and contribute new tests and patches (dealing with cvs
is a lot of hassle from behind firewalls).

Any thoughts?

Rong


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for
IBM's Free Linux Tutorials.  Learn everything from the bash shell to sys
admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for
IBM's Free Linux Tutorials.  Learn everything from the bash shell to sys
admin. Click now! =
http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for
IBM's Free Linux Tutorials.  Learn everything from the bash shell to sys
admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] Releasing Tests?

[<jue...@we...>]

I'm inclined to agree, but this implies a further issue: To be able to =
compile all the tests and the framework sources in the first place, we =
need to ship all the libraries that we depend on. We're talking about =
additional 1.6 MB of libs here (excluding Xerces and Clover). The test =
sources amount to 1.3 MB themselves (400 KB zipped). So in total, around =
2 MB increase in distribution size: from 12.1 MB (M3 + JPetStore) to =
14.1 MB. If we agree to accept that, I'll be happy to include the tests =
in the upcoming release.
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von Rod Johnson
Gesendet: Do 11.12.2003 10:06
An: spr...@li...
Betreff: Re: [Springframework-developer] Releasing Tests?



I agree with Rong. I think we should include tests in M4.

Regards,
Rod

----- Original Message -----
From: "Ou, Rong" <Ro...@sa...>
To: <spr...@li...>
Sent: Wednesday, December 10, 2003 9:43 PM
Subject: [Springframework-developer] Releasing Tests?


Hi all,

First time poster here. I've had Rod's book for a while, just haven't
finished reading it yet. :) Which I plan to do during the holidays.

I was a bit disappointed when I pulled down the m3 release and didn't =
find
any tests in it. Since we are all doing XP, agile, TDD now, isn't it =
high
time that tests are released together with production code? It would be =
so
much easier for newcomers to come up to speed with the framework ("Tests =
are
documentation") and contribute new tests and patches (dealing with cvs =
is a
lot of hassle from behind firewalls).

Any thoughts?

Rong


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for =
IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys =
admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for =
IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys =
admin.
Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] Releasing Tests?

[Rod J. <rod...@in...>]

I agree with Rong. I think we should include tests in M4.

Regards,
Rod

----- Original Message ----- 
From: "Ou, Rong" <Ro...@sa...>
To: <spr...@li...>
Sent: Wednesday, December 10, 2003 9:43 PM
Subject: [Springframework-developer] Releasing Tests?


Hi all,

First time poster here. I've had Rod's book for a while, just haven't
finished reading it yet. :) Which I plan to do during the holidays.

I was a bit disappointed when I pulled down the m3 release and didn't find
any tests in it. Since we are all doing XP, agile, TDD now, isn't it high
time that tests are released together with production code? It would be so
much easier for newcomers to come up to speed with the framework ("Tests are
documentation") and contribute new tests and patches (dealing with cvs is a
lot of hassle from behind firewalls).

Any thoughts?

Rong


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=ick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] petclinic html

[<jue...@we...>]

+1

________________________________

Von: spr...@li... im Auftrag =
von Darren Davison
Gesendet: Mi 10.12.2003 23:57
An: spr...@li...
Betreff: [Springframework-developer] petclinic html




is anyone currently relying on the html that petclinic outputs for =
tests, or
parsing in some way?  I'd like to change a few pages structurally and
generally tidy the output so it's more test-friendly for httpunit.  None =
of
the functionality or URL's etc. will change.

Cheers,
--

Darren Davison
Public Key: http://www.davison.uk.net/key.jsp



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for =
IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys =
admin.
Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

[Springframework-developer] petclinic html

[Darren D. <da...@da...>]

is anyone currently relying on the html that petclinic outputs for tests, or 
parsing in some way?  I'd like to change a few pages structurally and 
generally tidy the output so it's more test-friendly for httpunit.  None of 
the functionality or URL's etc. will change.

Cheers,
-- 

Darren Davison
Public Key: http://www.davison.uk.net/key.jsp

Re: [Springframework-developer] InvokerInterceptor --> ??

[Rod J. <rod...@in...>]

Alef

I'd really need to see the code (maybe send it to me directly). I'm not
quite sure what this code is trying to do, but I'm almost positive there's a
better way :-)

It looks as though it's trying to invent its own pointcut model, instead of
using the framework's. Is it putting custom behaviour in the
InvokerInterceptor?

The replacement would be to set the target to the target object (you don't
normally need to use a TargetSource unless you want to do something fancy,
so this is just standard framework usage) and put the interception behaviour
in an interceptor that's distinct from the invocation of the target.

If some invocations need to go to an object other than the ultimate target,
any interceptor can do that. It just returns the result of reflective method
invocation on _its_ target, rather than invoking proceed().

Regards,
Rod

----- Original Message ----- 
From: "Alef Arendsen" <al...@jt...>
To: <spr...@li...>
Sent: Wednesday, December 10, 2003 9:42 PM
Subject: [Springframework-developer] InvokerInterceptor --> ??


> Rod,
>
> I saw the InvokerInterceptor has been removed about two weeks ago. We
> used to use that to do method interceptions. I saw it was replaced by
> the TargetSource. My colleague asked me what replaced it. Since I am
> supposed to be the Spring expert here, but actually don't know anything
> about the AOP stuff :), you give me a hint how to do the method
> interceptions right now? We used to have something like this:
>
>     <bean id="WorkflowInterceptor"
>           class="icatch.workflow.interceptor.WorkflowInterceptor" //
> extending InvokerInterceptor
>           init-method="init">
>         <!-- set the workflow manager to handle all method interceptions
> -->
>         <property name="workflowManager">
>             <ref bean="WorkflowManager"/>
>         </property>
>         <!-- the definition of all methods that should be intercepted
> -->
>         <property name="interceptedMethods">
>             <props>
>                 <prop key="load"></prop>
>                 <prop key="create"></prop>
>                 <prop key="update"></prop>
>                 <prop key="remove"></prop>
>                 <prop key="findAll"></prop>
>                 <prop key="findBy"></prop>
>                 <prop key="isUnique"></prop>
>                 <prop key="executeBusinessLogic"></prop>
>             </props>
>         </property>
>     </bean>
>
> Thanx,
>
> Alef
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>

[Springframework-developer] Releasing Tests?

[Ou, R. <Ro...@sa...>]

Hi all,

First time poster here. I've had Rod's book for a while, just haven't =
finished reading it yet. :) Which I plan to do during the holidays.

I was a bit disappointed when I pulled down the m3 release and didn't =
find any tests in it. Since we are all doing XP, agile, TDD now, isn't =
it high time that tests are released together with production code? It =
would be so much easier for newcomers to come up to speed with the =
framework ("Tests are documentation") and contribute new tests and =
patches (dealing with cvs is a lot of hassle from behind firewalls).

Any thoughts?

Rong