You can subscribe to this list here.
| 2003 |
Jan
|
Feb
(55) |
Mar
(100) |
Apr
(203) |
May
(330) |
Jun
(190) |
Jul
(302) |
Aug
(323) |
Sep
(197) |
Oct
(245) |
Nov
(490) |
Dec
(330) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(194) |
Feb
(400) |
Mar
(416) |
Apr
(415) |
May
(359) |
Jun
(381) |
Jul
(491) |
Aug
(311) |
Sep
(291) |
Oct
(273) |
Nov
(355) |
Dec
(266) |
| 2005 |
Jan
(306) |
Feb
(303) |
Mar
(520) |
Apr
(346) |
May
(255) |
Jun
(221) |
Jul
(171) |
Aug
(247) |
Sep
(147) |
Oct
(125) |
Nov
(165) |
Dec
(65) |
| 2006 |
Jan
(90) |
Feb
(53) |
Mar
(121) |
Apr
(103) |
May
(113) |
Jun
(103) |
Jul
(104) |
Aug
(67) |
Sep
(78) |
Oct
(82) |
Nov
(78) |
Dec
(70) |
| 2007 |
Jan
(77) |
Feb
(76) |
Mar
(63) |
Apr
(30) |
May
(47) |
Jun
(41) |
Jul
(44) |
Aug
(44) |
Sep
(49) |
Oct
(33) |
Nov
(25) |
Dec
(21) |
| 2008 |
Jan
(45) |
Feb
(13) |
Mar
(15) |
Apr
(12) |
May
(9) |
Jun
(33) |
Jul
(30) |
Aug
(7) |
Sep
(20) |
Oct
(17) |
Nov
(20) |
Dec
(10) |
| 2009 |
Jan
(8) |
Feb
(5) |
Mar
(12) |
Apr
(17) |
May
(19) |
Jun
(97) |
Jul
(77) |
Aug
(33) |
Sep
(24) |
Oct
(41) |
Nov
(16) |
Dec
(32) |
| 2010 |
Jan
(24) |
Feb
(14) |
Mar
(50) |
Apr
(71) |
May
(70) |
Jun
(64) |
Jul
(45) |
Aug
(62) |
Sep
(32) |
Oct
(4) |
Nov
(12) |
Dec
(2) |
| 2011 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(3) |
May
(6) |
Jun
(1) |
Jul
(4) |
Aug
(3) |
Sep
(4) |
Oct
(6) |
Nov
(3) |
Dec
(3) |
| 2012 |
Jan
(4) |
Feb
(8) |
Mar
(6) |
Apr
(10) |
May
(2) |
Jun
(3) |
Jul
(11) |
Aug
(10) |
Sep
(4) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2013 |
Jan
(4) |
Feb
(1) |
Mar
(9) |
Apr
(1) |
May
(8) |
Jun
(2) |
Jul
(5) |
Aug
(2) |
Sep
|
Oct
(3) |
Nov
(10) |
Dec
(8) |
| 2014 |
Jan
(3) |
Feb
(12) |
Mar
(9) |
Apr
(12) |
May
(2) |
Jun
|
Jul
(3) |
Aug
(1) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(2) |
| 2015 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(9) |
May
(2) |
Jun
(2) |
Jul
|
Aug
(2) |
Sep
(7) |
Oct
(9) |
Nov
(7) |
Dec
(9) |
| 2016 |
Jan
(7) |
Feb
(5) |
Mar
(5) |
Apr
(5) |
May
(8) |
Jun
(4) |
Jul
(5) |
Aug
(4) |
Sep
(6) |
Oct
(7) |
Nov
(2) |
Dec
(3) |
| 2017 |
Jan
(7) |
Feb
(8) |
Mar
(7) |
Apr
(3) |
May
(4) |
Jun
(3) |
Jul
(5) |
Aug
(8) |
Sep
(4) |
Oct
(2) |
Nov
(3) |
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2021 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(5) |
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
| 2026 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Darren D. <da...@sh...> - 2005-09-02 04:33:16
|
1125635587 FAILED This is an automated mail from one of the SF Compile Farm machines. The machine name noted in the subject encountered a failure building or running the Spring test suite. The last few lines of the output were included for info. NB: No further mail will be sent from this machine until a manual reset occurs on the cf-shell machine, although builds will continue as scheduled. See http://springframework.sourceforge.net/test/ for further information. |
|
From: <al...@in...> - 2005-09-01 22:35:23
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20050902001702Lbuild.338 |
|
From: Andreas S. <an...@sc...> - 2005-09-01 13:46:46
|
Colin Sampaleanu wrote: > InternalResourceView just does a RequestDispatcher.forward (or include > in some cases). This is exactly how you are suppose to get to the JSP > engine. There is no 'more effiicient' or direct mechanism. The problem with .forward() is that you can't set any page scoped attributes. IMHO, using request attributes for exposing the model attributes is not ideal, as request attributes are inherited to further included resources. But since there does not seem to be an alternative, of course the discussion is useless. I just wanted to check for alternatives. Thanks anyway! Regards, Andreas |
|
From: Colin S. <col...@ex...> - 2005-09-01 00:37:13
|
InternalResourceView just does a RequestDispatcher.forward (or include in some cases). This is exactly how you are suppose to get to the JSP engine. There is no 'more effiicient' or direct mechanism. Regards, Colin Andreas Schildbach wrote: > Hello everyone, > > Please consider the InternalResourceView, which re-routes a request > through the whole "webapp pipeline" (filters, JSP servlet...) again. > > Wouldn't it be possible to somehow plug directly to JSP rendering for > JSP based views? > > The main benefit I would expect is that maybe the model could be > exposed as page scope attributes rather than request attributes, so > they would be local to the page only. > > The other benefit would be perhaps a performance gain. I'm a bit > suspicious that in a large application with many include fragements > and such, a lot time is wasted in the "pipeline"... > > What do you think? Would it be possible? > > Regards, > > Andreas > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing > & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: John L. <jl...@ar...> - 2005-08-31 23:34:05
|
A new release of Spring Portlet MVC is now available that includes the following changes: * Due to an unfortunate render parameter limitation in Pluto, AbstractFormController (and therefore its descendants like SimpleFormController and AbstractWizardFormController) no longer passes all the submitted parameters from the action phase to the render phase. This means that if you have form parameters that you need during the render phase, you will need to pass those forward explicitly via the ActionResponse.setRenderParameter method. Be sure to test this with existing code before deploying this into production. * All changes to the equivalent classes in the 1.2.4 release of the Servlet MVC Framework have been included here, as appropriate. * Several minor bug fixes, including a problem with AbstractController calling handleActionRequestInternal twice when the controller is synchronized on the session. Also a new version of the sample application is available. It now includes the use of an AbstractWizardFormController and a simple example of using the Mock classes to test a controller via JUnit. As always, you can download the updates from the Wiki site: http://opensource2.atlassian.com/confluence/spring/display/JSR168/Home The current source code is also in CVS in the Spring sandbox. Please send me any feedback. Thanks! John Lewis |
|
From: Oliver H. <Ol...@ou...> - 2005-08-31 23:02:28
|
If you checkout the "repository" module from the Spring's CVS it should be in there. Ollie > -----Original Message----- > From: spr...@li...=20 > [mailto:spr...@li...] > On Behalf Of Andy Depue > Sent: Thursday, 1 September 2005 3:23 AM > To: spr...@li... > Subject: [Springframework-developer] Ivy and spring-binding >=20 > I'm moving my build to Ivy and have a dependency on=20 > spring-binding, which doesn't seem to be included in the main=20 > Spring distribution. Can spring-binding be found in any=20 > public repository (can't seem to find it on ibiblio), or do I=20 > need to keep a copy in a local ivy repository? >=20 > Thanks, > Andy >=20 >=20 > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference &=20 > EXPO September 19-22, 2005 * San Francisco, CA * Development=20 > Lifecycle Practices Agile & Plan-Driven Development *=20 > Managing Projects & Teams * Testing & QA Security * Process=20 > Improvement & Measurement * http://www.sqe.com/bsce5sf=20 > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 |
|
From: <al...@in...> - 2005-08-31 22:30:56
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20050901001653Lbuild.337 |
|
From: Andy D. <an...@ma...> - 2005-08-31 17:23:49
|
I'm moving my build to Ivy and have a dependency on spring-binding, which doesn't seem to be included in the main Spring distribution. Can spring-binding be found in any public repository (can't seem to find it on ibiblio), or do I need to keep a copy in a local ivy repository? Thanks, Andy |
|
From: Darren D. <da...@sh...> - 2005-08-31 14:20:28
|
1125498018
FAILED
[junit] Testcase: testRmiProxyFactoryBeanWithBusinessInterfaceAndConnectExceptionAndRefresh took 0,263 sec
[junit] Testcase: testRmiProxyFactoryBeanWithBusinessInterfaceAndConnectIOExceptionAndRefresh took 0,348 sec
[junit] Testcase: testRmiProxyFactoryBeanWithBusinessInterfaceAndUnknownHostExceptionAndRefresh took 0,154 sec
[junit] Testcase: testRmiProxyFactoryBeanWithBusinessInterfaceAndNoSuchObjectExceptionAndRefresh took 0,076 sec
[junit] Testcase: testRmiProxyFactoryBeanWithBusinessInterfaceAndStubNotFoundExceptionAndRefresh took 0,499 sec
[junit] Testcase: testRmiProxyFactoryBeanWithBusinessInterfaceAndMarshalExceptionAndRefresh took 0,171 sec
[junit] Testcase: testRmiProxyFactoryBeanWithBusinessInterfaceAndUnmarshalExceptionAndRefresh took 0,256 sec
[junit] Testcase: testRmiClientInterceptorRequiresUrl took 0,65 sec
[junit] Testcase: testRemoteInvocation took 0,254 sec
[junit] Testcase: testRmiInvokerWithSpecialLocalMethods took 2,023 sec
[junit] Tests run: 11, Failures: 1, Errors: 0, Time elapsed: 333,047 sec
[junit] Testsuite: org.springframework.scheduling.quartz.QuartzSupportTests
[junit] Tests run: 11, Failures: 1, Errors: 0, Time elapsed: 333,047 sec
[junit] Testcase: testSchedulerFactoryBean took 192,403 sec
[junit] Testcase: testSchedulerFactoryBeanWithExplicitJobDetail took 0,651 sec
[junit] Testcase: testSchedulerFactoryBeanWithListeners took 2,788 sec
[junit] Testcase: testSchedulerFactoryBeanWithPlainQuartzObjects took 0,275 sec
[junit] Testcase: testSchedulerFactoryBeanWithApplicationContext took 0,959 sec
[junit] Testcase: testJobDetailBeanWithApplicationContext took 0,002 sec
[junit] Testcase: testJobDetailBeanWithListenerNames took 0,003 sec
[junit] Testcase: testCronTriggerBeanWithListenerNames took 0,002 sec
[junit] Testcase: testSimpleTriggerBeanWithListenerNames took 0,001 sec
[junit] Testcase: testMultipleSchedulers took 90,257 sec
[junit] Testcase: testWithTwoAnonymousMethodInvokingJobDetailFactoryBeans took 35,429 sec
[junit] FAILED
[junit] doExport not called on exportService expected:<2> but was:<0>
[junit] junit.framework.AssertionFailedError: doExport not called on exportService expected:<2> but was:<0>
[junit] at org.springframework.scheduling.quartz.QuartzSupportTests.testWithTwoAnonymousMethodInvokingJobDetailFactoryBeans(QuartzSupportTests.java:456)
This is an automated mail from one of the SF Compile Farm machines.
The machine name noted in the subject encountered a failure building
or running the Spring test suite. The last few lines of the output
were included for info.
NB: No further mail will be sent from this machine until a
manual reset occurs on the cf-shell machine, although builds will
continue as scheduled.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: <al...@in...> - 2005-08-30 22:34:43
|
View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20050831001724Lbuild.336 |
|
From: Andreas S. <an...@sc...> - 2005-08-30 20:46:53
|
Hello everyone, Please consider the InternalResourceView, which re-routes a request through the whole "webapp pipeline" (filters, JSP servlet...) again. Wouldn't it be possible to somehow plug directly to JSP rendering for JSP based views? The main benefit I would expect is that maybe the model could be exposed as page scope attributes rather than request attributes, so they would be local to the page only. The other benefit would be perhaps a performance gain. I'm a bit suspicious that in a large application with many include fragements and such, a lot time is wasted in the "pipeline"... What do you think? Would it be possible? Regards, Andreas |
|
From: Seth L. <set...@gm...> - 2005-08-30 18:20:22
|
On 8/29/05, Kristofer Eriksson <kri...@gm...> wrote: > Hi, and thanks for the reply.=20 > =20 > I have been playing around and have no problems creating objects etc. > Though, for me it is the dynamic reloading functionality that makes it > really interesting to use. If it worked before, we can only hope it will > work again soon. I agree, it's the dynamic reloading that is the killer feature. It might help to put a comment in the JIRA issue indicating your are "voting" for this feature. Seth |
|
From: Kristofer E. <kri...@gm...> - 2005-08-30 08:18:41
|
Hi, and thanks for the reply.=20 I have been playing around and have no problems creating objects etc.=20 Though, for me it is the dynamic reloading functionality that makes it=20 really interesting to use. If it worked before, we can only hope it will=20 work again soon. Btw, do you know at what point it stopped working? I saw your recent jira= =20 post reg this (thx for pointing me to it in the forum as well), unfortunatl= y=20 no reactions so far from the maestros. I have been trying to look into the= =20 code but as you put it, it requires a deeper undertanding to be able to do= =20 anything there. Meanwhile, I am playing around abit with a own bean factory based on the=20 script engine provided by the Groovy project itself but the solution is by= =20 no means as elegant a the one here (when it works).=20 As said, hopefully this can be solved soon. Any solution appreciated. Cheers Kristofer On 8/29/05, Seth Ladd <set...@gm...> wrote: >=20 > On 8/29/05, Kristofer Eriksson <kri...@gm...> wrote: > > Hi everybody, > > > > I recently posted a question regarding the scripting (groovy) support > > in sandbox in the core support forum, which might not have been the > > right place (http://forum.springframework.org/viewtopic.php?t=3D8244). > > If not, excuse me. >=20 > Scripting in general works quite well, and is a very nice way to get > scripted objects into Spring while using all of the nice Spring > features. >=20 > However, dynamic reloading currently is not working. It used to, so > expect a fix soon (hopefully). >=20 > If you don't need dynamic reloading, then you should start playing > around with it. The tests, found in the sandbox, show you how to get > started. The more feedback, the better! >=20 > Seth >=20 >=20 > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle=20 > Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q= A > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Seth L. <set...@gm...> - 2005-08-29 18:24:27
|
On 8/29/05, Kristofer Eriksson <kri...@gm...> wrote: > Hi everybody, >=20 > I recently posted a question regarding the scripting (groovy) support > in sandbox in the core support forum, which might not have been the > right place (http://forum.springframework.org/viewtopic.php?t=3D8244). > If not, excuse me. Scripting in general works quite well, and is a very nice way to get scripted objects into Spring while using all of the nice Spring features. However, dynamic reloading currently is not working. It used to, so expect a fix soon (hopefully). If you don't need dynamic reloading, then you should start playing around with it. The tests, found in the sandbox, show you how to get started. The more feedback, the better! Seth |
|
From: Thomas V. de V. <tho...@gm...> - 2005-08-29 18:12:38
|
As a general remark, I was wondering if Groovy style scripting is ready for= =20 prime time. Personally I haven't seen this on big projects. Would be=20 interesting to hear what other users' experiences are. Cheers, Thomas On 8/29/05, Kristofer Eriksson <kri...@gm...> wrote: >=20 > Hi everybody, >=20 > I recently posted a question regarding the scripting (groovy) support > in sandbox in the core support forum, which might not have been the > right place (http://forum.springframework.org/viewtopic.php?t=3D8244). > If not, excuse me. >=20 > I have looked through all mailing list archive, forums etc to try to > find out more about this subject but found very little that is not a > year old or so. With what is in the sandbox, when it is working, I see > lot of potential especially with Groovy gaining more and more > interest. There has been mentioning of some scripting support in 1.3 > but nothing detailed as far as I have seen. >=20 > If anyone have gotten the current code in the sandbox to work, I'd > appreciate it so much if I only could be pushed in the right > direction, or maybe get some tips on how to get it to work. >=20 > Also, what about the status of scripting support in general, is anyone > actually working on it for comming releases, or is this not "on the > table" any more? I am seriously interested in developing in this area. >=20 > Appreciate any response. >=20 > Kind Regards >=20 > /Kristofer Eriksson >=20 >=20 > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle=20 > Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q= A > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer >=20 --=20 Cheers, Thomas |
|
From: Alexandru P. <the...@gm...> - 2005-08-29 17:31:08
|
#: Eugene Kuleshov changed the world a bit at a time by saying on 8/29/2005 3:59 PM :#
> Alexandru Popescu wrote:
>
>>>> This looks to me pretty unintuitive, because we are talking about
>>>> after advices. The rules you are exposing are correct, but they apply
>>>> to around advice. I imagine that this is caused by the fact that
>>>> Spring doesn't have real before and after advices, but rather it is
>>>> emulating them using always around (this is true for all proxy based
>>>> aop solutions).
>>>
>>>
>>> First of all there are explicit Before and After advices
>>> semantically possible with Spring. It has very little todo that actual
>>> implementation is using proxy, which is always gives an around advice.
>>
>> imo it doesn't matter that you are implementing Before or After as long
>> as you refere to them as advices/interceptors and they are proxies. You
>> will always have this ordering, because they are in fact around advices
>> and the rules for around advices are those exposed before.
>>
>> this is just my opinion and I don't see any gain from continuing an
>> argument on this matter :-).
>
> Right. My point is that there is only one collection of advices in
> Spring bean definitions, so all advice tytes has to be somehow unified
> and there is nothing wrong to unify them all around advice. And if you
> think about it this way it is quite intuitive. :-)
>
>
Yep, we are both agreeing on this part :-).
:alex |.::the_mindstorm::.|
rergards,
> Eugene
>
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
|
|
From: Kristofer E. <kri...@gm...> - 2005-08-29 14:40:13
|
Hi everybody, I recently posted a question regarding the scripting (groovy) support in sandbox in the core support forum, which might not have been the right place (http://forum.springframework.org/viewtopic.php?t=3D8244). If not, excuse me. I have looked through all mailing list archive, forums etc to try to find out more about this subject but found very little that is not a year old or so. With what is in the sandbox, when it is working, I see lot of potential especially with Groovy gaining more and more interest. There has been mentioning of some scripting support in 1.3 but nothing detailed as far as I have seen. If anyone have gotten the current code in the sandbox to work, I'd appreciate it so much if I only could be pushed in the right direction, or maybe get some tips on how to get it to work. Also, what about the status of scripting support in general, is anyone actually working on it for comming releases, or is this not "on the table" any more? I am seriously interested in developing in this area. Appreciate any response. Kind Regards /Kristofer Eriksson |
|
From: Eugene K. <eu...@md...> - 2005-08-29 14:02:15
|
Alexandru Popescu wrote: >>> This looks to me pretty unintuitive, because we are talking about >>> after advices. The rules you are exposing are correct, but they apply >>> to around advice. I imagine that this is caused by the fact that >>> Spring doesn't have real before and after advices, but rather it is >>> emulating them using always around (this is true for all proxy based >>> aop solutions). >> >> >> First of all there are explicit Before and After advices >> semantically possible with Spring. It has very little todo that actual >> implementation is using proxy, which is always gives an around advice. > > imo it doesn't matter that you are implementing Before or After as long > as you refere to them as advices/interceptors and they are proxies. You > will always have this ordering, because they are in fact around advices > and the rules for around advices are those exposed before. > > this is just my opinion and I don't see any gain from continuing an > argument on this matter :-). Right. My point is that there is only one collection of advices in Spring bean definitions, so all advice tytes has to be somehow unified and there is nothing wrong to unify them all around advice. And if you think about it this way it is quite intuitive. :-) rergards, Eugene |
|
From: Alexandru P. <the...@gm...> - 2005-08-29 12:34:43
|
#: Eugene Kuleshov changed the world a bit at a time by saying on 8/29/2005 2:06 PM :# > Alexandru Popescu wrote: > >>> After returning advice is indeed processed in the opposite order. >>> Since the method invocation moves back up the advisor chain the last >>> advisor is processed first, then the second to last and so on until >>> all advisors have been processed. >>> >>> If you would chain an number of around advices (method interceptors) >>> they would also be processed in the inverse order once the target >>> method exits although they have been called in the expected order when >>> the method invocation starts. >> >> This looks to me pretty unintuitive, because we are talking about >> after advices. The rules you are exposing are correct, but they apply >> to around advice. I imagine that this is caused by the fact that >> Spring doesn't have real before and after advices, but rather it is >> emulating them using always around (this is true for all proxy based >> aop solutions). > > First of all there are explicit Before and After advices semantically > possible with Spring. It has very little todo that actual implementation > is using proxy, which is always gives an around advice. imo it doesn't matter that you are implementing Before or After as long as you refere to them as advices/interceptors and they are proxies. You will always have this ordering, because they are in fact around advices and the rules for around advices are those exposed before. this is just my opinion and I don't see any gain from continuing an argument on this matter :-). take care, :alex |.::the_mindstorm::.| > Note, that nothing actually stops user to implement Before and After > interfaces in the same class and put it into the list of advices (even > mixed with around advices). So, current behavior seems very logical if > you'll take this fact into the account. > > regards, > Eugene > |
|
From: Eugene K. <eu...@md...> - 2005-08-29 12:10:49
|
Alexandru Popescu wrote: >> After returning advice is indeed processed in the opposite order. >> Since the method invocation moves back up the advisor chain the last >> advisor is processed first, then the second to last and so on until >> all advisors have been processed. >> >> If you would chain an number of around advices (method interceptors) >> they would also be processed in the inverse order once the target >> method exits although they have been called in the expected order when >> the method invocation starts. > > This looks to me pretty unintuitive, because we are talking about > after advices. The rules you are exposing are correct, but they apply > to around advice. I imagine that this is caused by the fact that > Spring doesn't have real before and after advices, but rather it is > emulating them using always around (this is true for all proxy based > aop solutions). First of all there are explicit Before and After advices semantically possible with Spring. It has very little todo that actual implementation is using proxy, which is always gives an around advice. Note, that nothing actually stops user to implement Before and After interfaces in the same class and put it into the list of advices (even mixed with around advices). So, current behavior seems very logical if you'll take this fact into the account. regards, Eugene |
|
From: Alexandru P. <the...@gm...> - 2005-08-29 09:53:01
|
#: Steven Devijver changed the world a bit at a time by saying on 8/29/2005 10:29 AM :#
> Lilantha,
>
> After returning advice is indeed processed in the opposite order.
> Since the method invocation moves back up the advisor chain the last
> advisor is processed first, then the second to last and so on until
> all advisors have been processed.
>
> If you would chain an number of around advices (method interceptors)
> they would also be processed in the inverse order once the target
> method exits although they have been called in the expected order when
> the method invocation starts.
>
> Steven
>
This looks to me pretty unintuitive, because we are talking about after advices. The rules you are
exposing are correct, but they apply to around advice. I imagine that this is caused by the fact
that Spring doesn't have real before and after advices, but rather it is emulating them using always
around (this is true for all proxy based aop solutions).
:alex |.::the_mindstorm::.|
> On 8/29/05, Lilantha Darshana <Lil...@si...> wrote:
>>
>>
>>
>> Hi
>>
>>
>>
>> I'm trying a to invoke a joint point where I have two after returning
>> advices that I need to execute
>>
>> In the order that I have specified in the config bean. My bean definitions
>> is something like:
>>
>>
>>
>> <bean id="test"
>> class="org.springframework.aop.framework.ProxyFactoryBean">
>>
>> <property
>> name="proxyInterfaces"><value>ITarget</value></property>
>>
>> <property name="target"><ref local="testTarget"/></property>
>>
>> <property name="interceptorNames">
>>
>> <value>testAdvice1,testAdvice2</value>
>>
>> </property>
>>
>> </bean>
>>
>> <bean id="testTarget" class="Target"/>
>>
>>
>>
>> <bean id="testAdvice1"
>> class="org.springframework.aop.support.RegexpMethodPointcutAdvisor">
>>
>> <property name="advice">
>>
>> <bean class="AfterAdvice1"/>
>>
>> </property>
>>
>> <property name="patterns">
>>
>> <list>
>>
>> <value>.*foo</value>
>>
>> </list>
>>
>> </property>
>>
>> </bean>
>>
>> <bean id="testTarget" class="Target"/>
>>
>>
>>
>> <bean id="testAdvice2"
>> class="org.springframework.aop.support.RegexpMethodPointcutAdvisor">
>>
>> <property name="advice">
>>
>> <bean class="AfterAdvice2"/>
>>
>> </property>
>>
>> <property name="patterns">
>>
>> <list>
>>
>> <value>.*foo</value>
>>
>> </list>
>>
>> </property>
>>
>> </bean>
>>
>>
>>
>> My expectation is, after retuning from the join point it should execute
>> return method of each of
>>
>> these after advices in the same order as I have specified in the bean.
>>
>> i.e. testAdvice1 followed by testAdvice2.
>>
>>
>>
>> However, it's executes them in opposite order. This seems due to following
>> method of
>>
>> AfterReturningAdviceInterceptor class.
>>
>>
>>
>> public Object invoke(MethodInvocation mi) throws Throwable {
>>
>> Object retVal = mi.proceed();
>>
>> this.advice.afterReturning(retVal, mi.getMethod(),
>> mi.getArguments(), mi.getThis());
>>
>> return retVal;
>>
>> }
>>
>>
>>
>> Appriciate if you would clarify why it is execute in opposite order? Is it
>> the intended way to execute them?
>>
>>
>>
>> Thanks
>>
>> -Lilantha
>>
>> _______________
>> Siebel
>> IT'S ALL ABOUT THE CUSTOMER
>> Visit www.siebel.com
>>
>> This e-mail message is for the sole use of the intended recipient(s) and
>> contains confidential and/or privileged information belonging to Siebel
>> Systems, Inc. or its customers or partners. Any unauthorized review, use,
>> copying, disclosure or distribution of this message is strictly prohibited.
>> If you are not an intended recipient of this message, please contact the
>> sender by reply e-mail and destroy all soft and hard copies of the message
>> and any attachments. Thank you for your cooperation.
>>
>
>
|
|
From: Steven D. <ste...@gm...> - 2005-08-29 08:29:36
|
Lilantha,
After returning advice is indeed processed in the opposite order.
Since the method invocation moves back up the advisor chain the last
advisor is processed first, then the second to last and so on until
all advisors have been processed.
If you would chain an number of around advices (method interceptors)
they would also be processed in the inverse order once the target
method exits although they have been called in the expected order when
the method invocation starts.
Steven
On 8/29/05, Lilantha Darshana <Lil...@si...> wrote:
> =20
> =20
>=20
> Hi=20
>=20
> =20
>=20
> I'm trying a to invoke a joint point where I have two after returning
> advices that I need to execute=20
>=20
> In the order that I have specified in the config bean. My bean definition=
s
> is something like:=20
>=20
> =20
>=20
> <bean id=3D"test"
> class=3D"org.springframework.aop.framework.ProxyFactoryBean">
>=20
> <property
> name=3D"proxyInterfaces"><value>ITarget</value></property>=20
>=20
> <property name=3D"target"><ref local=3D"testTarget"/></property=
>=20
>=20
> <property name=3D"interceptorNames">=20
>=20
> <value>testAdvice1,testAdvice2</value>=20
>=20
> </property>=20
>=20
> </bean>=20
>=20
> <bean id=3D"testTarget" class=3D"Target"/>=20
>=20
> =20
>=20
> <bean id=3D"testAdvice1"
> class=3D"org.springframework.aop.support.RegexpMethodPointcutAdvisor">
>=20
> <property name=3D"advice">=20
>=20
> <bean class=3D"AfterAdvice1"/>=20
>=20
> </property>=20
>=20
> <property name=3D"patterns">=20
>=20
> <list>=20
>=20
> <value>.*foo</value>=20
>=20
> </list>=20
>=20
> </property>=20
>=20
> </bean>=20
>=20
> <bean id=3D"testTarget" class=3D"Target"/>=20
>=20
> =20
>=20
> <bean id=3D"testAdvice2"
> class=3D"org.springframework.aop.support.RegexpMethodPointcutAdvisor">
>=20
> <property name=3D"advice">=20
>=20
> <bean class=3D"AfterAdvice2"/>=20
>=20
> </property>=20
>=20
> <property name=3D"patterns">=20
>=20
> <list>=20
>=20
> <value>.*foo</value>=20
>=20
> </list>=20
>=20
> </property>=20
>=20
> </bean>=20
>=20
> =20
>=20
> My expectation is, after retuning from the join point it should execute
> return method of each of=20
>=20
> these after advices in the same order as I have specified in the bean.=20
>=20
> i.e. testAdvice1 followed by testAdvice2.=20
>=20
> =20
>=20
> However, it's executes them in opposite order. This seems due to followin=
g
> method of=20
>=20
> AfterReturningAdviceInterceptor class.=20
>=20
> =20
>=20
> public Object invoke(MethodInvocation mi) throws Throwable {=20
>=20
> Object retVal =3D mi.proceed();=20
>=20
> this.advice.afterReturning(retVal, mi.getMethod(),
> mi.getArguments(), mi.getThis());=20
>=20
> return retVal;=20
>=20
> }=20
>=20
> =20
>=20
> Appriciate if you would clarify why it is execute in opposite order? Is i=
t
> the intended way to execute them?=20
>=20
> =20
>=20
> Thanks=20
>=20
> -Lilantha=20
>=20
> _______________
> Siebel
> IT'S ALL ABOUT THE CUSTOMER
> Visit www.siebel.com
> =20
> This e-mail message is for the sole use of the intended recipient(s) and
> contains confidential and/or privileged information belonging to Siebel
> Systems, Inc. or its customers or partners. Any unauthorized review, use,
> copying, disclosure or distribution of this message is strictly prohibite=
d.
> If you are not an intended recipient of this message, please contact the
> sender by reply e-mail and destroy all soft and hard copies of the messag=
e
> and any attachments. Thank you for your cooperation.
> =20
--=20
"If you want to be a different fish, you gotta jump out of the school."
-- Captain Beefheart
|
|
From: Juergen H. <ju...@in...> - 2005-08-29 06:42:35
|
Dear Spring community, I'm pleased to announce that Spring 1.2.4 has just been released. This is a bugfix and minor enhancement release, fixing a number of issues found in previous 1.2.x releases and introducing various minor new features. All Spring 1.2.x users are encouraged to upgrade to Spring 1.2.4. Watch out for a Spring 1.3 release candidate, including Portlet support, and the first Web Flow release candidate in late September! Cheers, Juergen ----- Juergen Hoeller Interface21 - Spring Services from the Source http://www.springframework.com |
|
From: Lilantha D. <Lil...@Si...> - 2005-08-29 04:35:08
|
Hi=20
=20
I'm trying a to invoke a joint point where I have two after returning
advices that I need to execute
In the order that I have specified in the config bean. My bean
definitions is something like:
=20
<bean id=3D"test"
class=3D"org.springframework.aop.framework.ProxyFactoryBean">
<property
name=3D"proxyInterfaces"><value>ITarget</value></property>
<property name=3D"target"><ref local=3D"testTarget"/></property>
<property name=3D"interceptorNames">
<value>testAdvice1,testAdvice2</value>
</property>
</bean>
<bean id=3D"testTarget" class=3D"Target"/>
=20
<bean id=3D"testAdvice1"
class=3D"org.springframework.aop.support.RegexpMethodPointcutAdvisor">
<property name=3D"advice">
<bean class=3D"AfterAdvice1"/>
</property>
<property name=3D"patterns">
<list>
<value>.*foo</value>
</list>
</property>
</bean>
<bean id=3D"testTarget" class=3D"Target"/>
=20
<bean id=3D"testAdvice2"
class=3D"org.springframework.aop.support.RegexpMethodPointcutAdvisor">
<property name=3D"advice">
<bean class=3D"AfterAdvice2"/>
</property>
<property name=3D"patterns">
<list>
<value>.*foo</value>
</list>
</property>
</bean>
=20
My expectation is, after retuning from the join point it should execute
return method of each of=20
these after advices in the same order as I have specified in the bean.
i.e. testAdvice1 followed by testAdvice2.
=20
However, it's executes them in opposite order. This seems due to
=66ollowing method of=20
AfterReturningAdviceInterceptor class.
=20
public Object invoke(MethodInvocation mi) throws Throwable {
Object retVal =3D mi.proceed();
this.advice.afterReturning(retVal, mi.getMethod(),
mi.getArguments(), mi.getThis());
return retVal;
}
=20
Appriciate if you would clarify why it is execute in opposite order=3F Is
it the intended way to execute them=3F
=20
Thanks
-Lilantha
_______________
Siebel
IT'S ALL ABOUT THE CUSTOMER
Visit www.siebel.com
This e-mail message is for the sole use of the intended recipient(s) and =
contains confidential and/or privileged information belonging to Siebel =
Systems, Inc. or its customers or partners. Any unauthorized review, use, =
copying, disclosure or distribution of this message is strictly prohibited.=
=
If you are not an intended recipient of this message, please contact the =
sender by reply e-mail and destroy all soft and hard copies of the message =
and any attachments. Thank you for your cooperation.
|
|
From: Colin S. <col...@ex...> - 2005-08-28 00:17:29
|
I think Juergen didn't have time for an announcement. I'm going to update the web site at least for now. Thomas Risberg wrote: > Never mind. I just saw the release available on SF. > > Thomas > > > On Aug 27, 2005, at 11:24 AM, Thomas Risberg wrote: > >> What's the current ETA for 1.2.4? I have some jdbc changes for 1.3 >> waiting - would like to avoid too many merges. >> >> Thomas >> >> >> On Aug 23, 2005, at 4:22 AM, Juergen Hoeller wrote: >> >> >>> Eugene, >>> >>> A couple of last-minute reports came in that we aimed to address >>> but didn't >>> quite manage to finish on the weekend. The actual release is now gonna >>> happen on Thursday 25th. >>> >>> If you need a feature or fix beyond 1.2.3, I recommend to use one >>> of the >>> recent 1.2.4 nightly snapshots in the meantime, which are fully >>> stable. They >>> just don't contain a couple of specific fixes that we still want to >>> get into >>> 1.2.4. >>> >>> Juergen >>> >>> >>> -----Original Message----- >>> From: spr...@li... >>> [mailto:spr...@li...] On >>> Behalf Of >>> Eugene Kuleshov >>> Sent: Monday, August 22, 2005 4:08 PM >>> To: spr...@li... >>> Subject: Re: [Springframework-developer] Preparing for 1.2.4 >>> >>> Rob, Juergen, >>> >>> What is happening with 1.2.4 release? It is almost a week since >>> Rob's >>> email. >>> >>> Do you have any specific date when it going to be? >>> >>> Thanks. >>> >>> Eugene >>> >>> >>> Rob Harrop wrote: >>> >>> >>>> All, >>>> >>>> I will be starting the finishing steps for polishing the 1.2.4 >>>> release >>>> tomorrow so if there are any pressing issues please let me know. >>>> Please refrain from committing any code for new features - only >>>> bug fixes! >>>> >>>> Target date for the release is Saturday. >>>> >>>> Regards, >>>> >>>> Rob >>>> >>>> >>>> >>> >>> >>> >>> ------------------------------------------------------- >>> SF.Net email is Sponsored by the Better Software Conference & EXPO >>> September >>> 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices >>> Agile & >>> Plan-Driven Development * Managing Projects & Teams * Testing & QA >>> Security >>> * Process Improvement & Measurement * http://www.sqe.com/bsce5sf >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework- developer >>> >>> >>> >>> >>> ------------------------------------------------------- >>> SF.Net email is Sponsored by the Better Software Conference & EXPO >>> September 19-22, 2005 * San Francisco, CA * Development Lifecycle >>> Practices >>> Agile & Plan-Driven Development * Managing Projects & Teams * >>> Testing & QA >>> Security * Process Improvement & Measurement * http://www.sqe.com/ >>> bsce5sf >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework- developer >>> >>> >>> >>> >> >> >> >> ------------------------------------------------------- >> SF.Net email is Sponsored by the Better Software Conference & EXPO >> September 19-22, 2005 * San Francisco, CA * Development Lifecycle >> Practices >> Agile & Plan-Driven Development * Managing Projects & Teams * >> Testing & QA >> Security * Process Improvement & Measurement * http://www.sqe.com/ >> bsce5sf >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> >> > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing > & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer |