springframework-developer — Spring Framework developers list

[Springframework-developer] spring Build Failed

[<al...@in...>]

View results here -> http://opensource.jteam.nl/build/buildresults/spring?log=log20051117001626

[Springframework-developer] FAILED BUILD: sparc-solaris2 (last 30 lines included)

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

1132176960
FAILED
Buildfile: build.xml

clean:
   [delete] Deleting directory /home/users/d/da/davison/checkouts/spring/target/classes
   [delete] Deleting directory /home/users/d/da/davison/checkouts/spring/target

compileattr:
[attribute-compiler] Generated attribute information for 1 classes. Ignored 0 classes.

buildmain:
    [mkdir] Created dir: /home/users/d/da/davison/checkouts/spring/target/classes
    [mkdir] Created dir: /home/users/d/da/davison/checkouts/spring/target/classes/META-INF
    [javac] Compiling 1130 source files to /home/users/d/da/davison/checkouts/spring/target/classes
    [javac] /home/users/d/da/davison/checkouts/spring/src/org/springframework/util/ReflectionUtils.java:96: cannot resolve symbol
    [javac] symbol  : constructor IllegalStateException  (java.lang.String,java.lang.IllegalAccessException)
    [javac] location: class java.lang.IllegalStateException
    [javac] 			throw new IllegalStateException("Should not get here.", e);
    [javac]                               ^
    [javac] /home/users/d/da/davison/checkouts/spring/src/org/springframework/util/ReflectionUtils.java:100: cannot resolve symbol
    [javac] symbol  : constructor IllegalStateException  (java.lang.String,java.lang.reflect.InvocationTargetException)
    [javac] location: class java.lang.IllegalStateException
    [javac] 			throw new IllegalStateException("Should not get here.", e);
    [javac]                               ^
    [javac] Note: Some input files use or override a deprecated API.
    [javac] Note: Recompile with -deprecation for details.
    [javac] 2 errors
Last CVS updates prior to this build were:
1132175581

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
successful build occurs on the machine in question.

See http://springframework.sourceforge.net/test/ for further
information.

[Springframework-developer] FAILED BUILD: ppc-osx2 (last 30 lines included)

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

1132173272
FAILED
Buildfile: build.xml

clean:
   [delete] Deleting directory /home/users/d/da/davison/checkouts/spring/target/classes
   [delete] Deleting directory /home/users/d/da/davison/checkouts/spring/target

compileattr:
[attribute-compiler] Generated attribute information for 1 classes. Ignored 0 classes.

buildmain:
    [mkdir] Created dir: /home/users/d/da/davison/checkouts/spring/target/classes
    [mkdir] Created dir: /home/users/d/da/davison/checkouts/spring/target/classes/META-INF
    [javac] Compiling 1130 source files to /home/users/d/da/davison/checkouts/spring/target/classes
    [javac] /home/users/d/da/davison/checkouts/spring/src/org/springframework/util/ReflectionUtils.java:96: cannot resolve symbol
    [javac] symbol  : constructor IllegalStateException (java.lang.String,java.lang.IllegalAccessException)
    [javac] location: class java.lang.IllegalStateException
    [javac] 			throw new IllegalStateException("Should not get here.", e);
    [javac]                               ^
    [javac] /home/users/d/da/davison/checkouts/spring/src/org/springframework/util/ReflectionUtils.java:100: cannot resolve symbol
    [javac] symbol  : constructor IllegalStateException (java.lang.String,java.lang.reflect.InvocationTargetException)
    [javac] location: class java.lang.IllegalStateException
    [javac] 			throw new IllegalStateException("Should not get here.", e);
    [javac]                               ^
    [javac] Note: Some input files use or override a deprecated API.
    [javac] Note: Recompile with -deprecation for details.
    [javac] 2 errors
Last CVS updates prior to this build were:
1132171981
? ?
? junit423465713.properties
? junittestcases2136842450.properties
? sandbox/src/org/springframework/core/closure/ElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java
? sandbox/src/org/springframework/core/closure/support/IfBlock.java
? sandbox/src/org/springframework/jms/listener
? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
C sandbox/src/org/springframework/jms/listener/AbstractMessageListenerContainer.java
C sandbox/src/org/springframework/jms/listener/SessionAwareMessageListener.java
C sandbox/src/org/springframework/jms/listener/SimpleMessageListenerContainer.java
C sandbox/src/org/springframework/jms/listener/SimpleMessageListenerContainer102.java
C sandbox/src/org/springframework/jms/listener/package.html
C sandbox/src/org/springframework/jms/listener/server/AbstractPoolingServerSessionFactory.java
C sandbox/src/org/springframework/jms/listener/server/CommonsPoolServerSessionFactory.java
C sandbox/src/org/springframework/jms/listener/server/ListenerSessionManager.java
C sandbox/src/org/springframework/jms/listener/server/ServerMessageListenerContainer.java
C sandbox/src/org/springframework/jms/listener/server/ServerMessageListenerContainer102.java
C sandbox/src/org/springframework/jms/listener/server/ServerSessionFactory.java
C sandbox/src/org/springframework/jms/listener/server/SimpleServerSessionFactory.java
C sandbox/src/org/springframework/jms/listener/server/package.html
C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml

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
successful build occurs on the machine in question.

See http://springframework.sourceforge.net/test/ for further
information.

[Springframework-developer] FAILED BUILD: sparc-solaris1 (last 30 lines included)

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

1132141735
FAILED
    [junit] Testcase: testAutowireWithDefault took 0.045 sec
    [junit] Testcase: testAutowireByConstructor took 0.113 sec
    [junit] Testcase: testAutowireByConstructorWithSimpleValues took 0.065 sec
    [junit] Testcase: testConstructorArgResolution took 0.206 sec
    [junit] Testcase: testConstructorArgWithSingleMatch took 0.081 sec
    [junit] Testcase: testThrowsExceptionOnTooManyArguments took 0.068 sec
    [junit] Testcase: testThrowsExceptionOnAmbiguousResolution took 0.206 sec
    [junit] Testcase: testFactoryBeanDefinedAsPrototype took 0.107 sec
    [junit] Testcase: testDependsOn took 0.324 sec
    [junit] Testcase: testDependsOnInInnerBean took 0.231 sec
    [junit] Testcase: testDependenciesThroughConstructorArguments took 0.051 sec
    [junit] Testcase: testDependenciesThroughConstructorArgumentAutowiring took 0.1 sec
    [junit] Testcase: testDependenciesThroughConstructorArgumentsInInnerBean took 0.117 sec
    [junit] Testcase: testDependenciesThroughProperties took 0.043 sec
    [junit] Testcase: testDependenciesThroughPropertiesWithInTheMiddle took 0.14 sec
    [junit] Testcase: testDependenciesThroughPropertyAutowiringByName took 0.036 sec
    [junit] Testcase: testDependenciesThroughPropertyAutowiringByType took 0.039 sec
    [junit] Testcase: testDependenciesThroughPropertiesInInnerBean took 0.151 sec
    [junit] Testcase: testClassNotFoundWithDefault took 0.039 sec
    [junit] Testcase: testClassNotFoundWithNoBeanClassLoader took 0.046 sec
    [junit] Testcase: testResourceAndInputStream took 0.329 sec
    [junit] Testcase: testClassPathResourceWithImport took 0.311 sec
    [junit] Testcase: testUrlResourceWithImport took 0.282 sec
    [junit] Testcase: testFileSystemResourceWithImport took 0.084 sec
    [junit] Testcase: testLookupOverrideMethodsWithSetterInjection took 2.1 sec
    [junit] 	FAILED
    [junit] null
    [junit] junit.framework.AssertionFailedError
    [junit] 	at org.springframework.beans.factory.xml.XmlBeanFactoryTests.testLookupOverrideMethodsWithSetterInjection(XmlBeanFactoryTests.java:897)

Last CVS updates prior to this build were:
1132139581
? ?
? junit423465713.properties
? junittestcases2136842450.properties
? sandbox/src/org/springframework/core/closure/ElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGenerator.java
? sandbox/src/org/springframework/core/closure/support/AbstractElementGeneratorWorkflow.java
? sandbox/src/org/springframework/core/closure/support/IfBlock.java
? sandbox/src/org/springframework/jms/listener
? test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml
C sandbox/src/org/springframework/jms/listener/AbstractMessageListenerContainer.java
C sandbox/src/org/springframework/jms/listener/SessionAwareMessageListener.java
C sandbox/src/org/springframework/jms/listener/SimpleMessageListenerContainer.java
C sandbox/src/org/springframework/jms/listener/SimpleMessageListenerContainer102.java
C sandbox/src/org/springframework/jms/listener/package.html
C sandbox/src/org/springframework/jms/listener/server/AbstractPoolingServerSessionFactory.java
C sandbox/src/org/springframework/jms/listener/server/CommonsPoolServerSessionFactory.java
C sandbox/src/org/springframework/jms/listener/server/ListenerSessionManager.java
C sandbox/src/org/springframework/jms/listener/server/ServerMessageListenerContainer.java
C sandbox/src/org/springframework/jms/listener/server/ServerMessageListenerContainer102.java
C sandbox/src/org/springframework/jms/listener/server/ServerSessionFactory.java
C sandbox/src/org/springframework/jms/listener/server/SimpleServerSessionFactory.java
C sandbox/src/org/springframework/jms/listener/server/package.html
C test/org/springframework/beans/factory/xml/dependencies-prop-inTheMiddle.xml

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
successful build occurs on the machine in question.

See http://springframework.sourceforge.net/test/ for further
information.

[Springframework-developer] Re: unable to turn off automatic detection of all handler adaptors?

[Seth L. <set...@gm...>]

Hi Juergen,

> I've just added a corresponding "detectAllHandlerAdapters" property.

By any chance did this get checked in?  I know sometimes there's a
delay between public and private CVS repos.  I don't see it in the
public CVS.

No rush, just wondering if this is still slated to go in,
Thanks,
Seth

RE: [Springframework-developer] HandlerExceptionResolver not catching taglib exceptions?

[Boyce, K. G. <Kei...@bc...>]

The relavent code as seen below is where exception is thrown, exception
resolver handles error, render occurs but because it hasn't determined
the mappedHandler triggerAfterCompletion does nothing:
try {
....
				PortletSession session =3D
request.getPortletSession(false);
				if (session !=3D null) {
				    if
(TRUE.equals(request.getParameter(ACTION_EXCEPTION_PARAMETER))) {
						Exception ex =3D
(Exception)session.getAttribute(ACTION_EXCEPTION_SESSION_ATTRIBUTE);
						if (ex !=3D null) {
						    logger.error("render
phase found exception caught during action phase -- rethrowing it");
						    throw ex;
						}
				    } else {
=0D
session.removeAttribute(ACTION_EXCEPTION_SESSION_ATTRIBUTE);
				    }
				}
			=0D
				// Determine handler for the current
request.
				mappedHandler =3D
getHandler(processedRequest, false);
}
			catch (Exception ex) {
				Object handler =3D (mappedHandler !=3D null
? mappedHandler.getHandler() : null);
				mv =3D processHandlerException(request,
response, handler, ex);
			}

			// Did the handler return a view to render?
			if (mv !=3D null && !(mv.getView() =3D=3D null &&
mv.getViewName() =3D=3D null && mv.getModel() =3D=3D null)) {
				render(mv, processedRequest, response);
			}


...
	private void triggerAfterCompletion(
			HandlerExecutionChain mappedHandler, int
interceptorIndex,
			PortletRequest request, PortletResponse
response, Exception ex)
			throws Exception {

		// Apply afterCompletion methods of registered
interceptors.
		if (mappedHandler !=3D null) {
=0D

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf
Of Seth Ladd
Sent: Tuesday, November 15, 2005 6:45 PM
To: spr...@li...
Subject: Re: [Springframework-developer] HandlerExceptionResolver not
catching taglib exceptions?

On 11/15/05, Boyce, Keith Garry <Kei...@bc...> wrote:
>
> But that's the whole deal about the exception resolver. We configure=0D
> the interceptors for a particular handler to handle particular use=0D
> cases and we need someway to to intercept just that.. Isn't there a=0D
> way we can implement the interceptor concept for exceptions.

Oops, I misread the description for afterCompletion:

         * Callback after completion of request processing, that is,
after rendering
	 * the view. Will be called on any outcome of handler execution,
thus allows
	 * for proper resource cleanup.

So afterCompletion is after the view rendering.  Why this isn't picking
up exceptions thrown by your taglibs, I'm not sure.

Seth


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam for All
Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id=16845&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer


This message is a PRIVATE communication.
If you are not the intended recipient, please do not read, copy,
or use it, and do not disclose it to others. Please notify the
sender of the delivery error by replying to this message, and then
delete it from your system. Thank you.

Re: [Springframework-developer] HandlerExceptionResolver not catching taglib exceptions?

[Seth L. <set...@gm...>]

On 11/15/05, Boyce, Keith Garry <Kei...@bc...> wrote:
>
> But that's the whole deal about the exception resolver. We configure the
> interceptors for a particular handler to handle particular use cases and
> we need someway to to intercept just that.. Isn't there a way we can
> implement the interceptor concept for exceptions.

Oops, I misread the description for afterCompletion:

         * Callback after completion of request processing, that is,
after rendering
=09 * the view. Will be called on any outcome of handler execution, thus al=
lows
=09 * for proper resource cleanup.

So afterCompletion is after the view rendering.  Why this isn't
picking up exceptions thrown by your taglibs, I'm not sure.

Seth

RE: [Springframework-developer] HandlerExceptionResolver not catching taglib exceptions?

[Boyce, K. G. <Kei...@bc...>]

But that's the whole deal about the exception resolver. We configure the
interceptors for a particular handler to handle particular use cases and
we need someway to to intercept just that.. Isn't there a way we can
implement the interceptor concept for exceptions.

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf
Of Seth Ladd
Sent: Tuesday, November 15, 2005 5:34 PM
To: spr...@li...
Subject: Re: [Springframework-developer] HandlerExceptionResolver not
catching taglib exceptions?

> If so, what would be the correct way to handle exceptions issued by=0D
> taglibs, using spring MVC?

You're right, in that if the exception is thrown from the view layer,
the handler interceptors won't be invoked.  Those interceptors only
apply to the handlers (controllers).

If the exception is thrown from a view, you can either use Spring's
exception resolving, or the web.xml's exception mapping.  By this point,
the handler is out of the picture.

You could wrap the whole thing in a filter, which would be able to catch
the exceptions thrown from a view.

Seth


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam for All
Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id=16845&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer


This message is a PRIVATE communication.
If you are not the intended recipient, please do not read, copy,
or use it, and do not disclose it to others. Please notify the
sender of the delivery error by replying to this message, and then
delete it from your system. Thank you.

Re: [Springframework-developer] HandlerExceptionResolver not catching taglib exceptions?

[Seth L. <set...@gm...>]

> If so, what would be the correct way to handle exceptions issued by tagli=
bs,
> using spring MVC?

You're right, in that if the exception is thrown from the view layer,
the handler interceptors won't be invoked.  Those interceptors only
apply to the handlers (controllers).

If the exception is thrown from a view, you can either use Spring's
exception resolving, or the web.xml's exception mapping.  By this
point, the handler is out of the picture.

You could wrap the whole thing in a filter, which would be able to
catch the exceptions thrown from a view.

Seth

RE: [Springframework-developer] HandlerExceptionResolver not catching taglib exceptions?

[Boyce, K. G. <Kei...@bc...>]

This is exactly what I am experiencing with the following thread.

> Yes the exception resolver allows you to resolve exception to view but

> there is no current way I found to apply interceptor to it.

> I need a way to have code run after exception is raised from mvc=0D
> handler basically to do some stuff before and after the exception view

> is displayed. Is that something that can be added to framework.=0D
> Basically I need some code to run in order to prepare the error view=0D
> and after the view is displayed I need to clean up some information=0D
> including possibly the exception so in the case of portlet mvc the=0D
> next time the view is rendered I want it to display the view from the=0D
> default handler rather than the exception again which is what is
currently happening.=0D

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf
Of Tim Kettering
Sent: Tuesday, November 15, 2005 3:32 PM
To: spr...@li...
Subject: [Springframework-developer] HandlerExceptionResolver not
catching taglib exceptions?


I'm doing some work with the spring-portlet MVC in our current project,
and one thing I ran across recently is that apparently the
HandlerExceptionResolver on the portlet side does not catch Exceptions
thrown from a taglib (a custom taglib for example).  I've tested this
out by issuing the same exception from inside the handler itself, which
was caught as expected, but throwing that exception from a taglib itself
is not caught.

So it seems that the HandlerExceptionResolver does not handle exceptions
that are issued after the flow of control is handed over to the view
phase.

I e-mailed John Lewis about this, and he said he thinks this is how it
also performs on the servlet-MVC side as well.  Since we do not have any
servlet-MVC code here, I thought I'd ask on the list to see if this is
indeed true as well.

If so, what would be the correct way to handle exceptions issued by
taglibs, using spring MVC? =0D

Thanks!

-tim



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam for All
Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=3D7628&alloc_id=3D16845&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer


This message is a PRIVATE communication.
If you are not the intended recipient, please do not read, copy,
or use it, and do not disclose it to others. Please notify the
sender of the delivery error by replying to this message, and then
delete it from your system. Thank you.

[Springframework-developer] HandlerExceptionResolver not catching taglib exceptions?

[Tim K. <tim...@vi...>]

I'm doing some work with the spring-portlet MVC in our current project, and
one thing I ran across recently is that apparently the
HandlerExceptionResolver on the portlet side does not catch Exceptions
thrown from a taglib (a custom taglib for example).  I've tested this out by
issuing the same exception from inside the handler itself, which was caught
as expected, but throwing that exception from a taglib itself is not caught.

So it seems that the HandlerExceptionResolver does not handle exceptions
that are issued after the flow of control is handed over to the view phase.

I e-mailed John Lewis about this, and he said he thinks this is how it also
performs on the servlet-MVC side as well.  Since we do not have any
servlet-MVC code here, I thought I'd ask on the list to see if this is
indeed true as well.

If so, what would be the correct way to handle exceptions issued by taglibs,
using spring MVC?  

Thanks!

-tim

[Springframework-developer] 1.2.6 in Jira

[Dmitriy K. <dko...@ru...>]

Juergen,

I've "released" version 1.2.6 in our Jira.

Dmitriy.

Re: [Springframework-developer] CVS HEAD dedicated to Spring 1.3

[Michael E. M. <mm...@re...>]

ok.. sorry. i see the "popular issues" link, which gives me an idea of 
what's going on out there.


Michael E. Moores wrote:

> that link is why i posted this question
>
> Magnus Heino wrote:
>
>> http://opensource2.atlassian.com/projects/spring/browse/SPR?report=com.atlassian.jira.plugin.system.project:roadmap-panel 
>> <http://opensource2.atlassian.com/projects/spring/browse/SPR?report=com.atlassian.jira.plugin.system.project:roadmap-panel> 
>>
>>
>> 2005/11/15, Michael E. Moores <mm...@re... 
>> <mailto:mm...@re...>>:
>>
>>     is there a doc that has some details on what v1.3 will be?
>>
>>
>> -- 
>>
>>   /Magnus Heino 
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
> Register for a JBoss Training Course.  Free Certification Exam
> for All Training Attendees Through End of 2005. For more info visit:
> http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>

Re: [Springframework-developer] CVS HEAD dedicated to Spring 1.3

[Michael E. M. <mm...@re...>]

that link is why i posted this question

Magnus Heino wrote:

> http://opensource2.atlassian.com/projects/spring/browse/SPR?report=com.atlassian.jira.plugin.system.project:roadmap-panel 
> <http://opensource2.atlassian.com/projects/spring/browse/SPR?report=com.atlassian.jira.plugin.system.project:roadmap-panel>
>
> 2005/11/15, Michael E. Moores <mm...@re... 
> <mailto:mm...@re...>>:
>
>     is there a doc that has some details on what v1.3 will be?
>
>
> -- 
>
>   /Magnus Heino 

Re: [Springframework-developer] Improvement: I need a way to have code run after exception is raised from mvc handler.

[Seth L. <set...@gm...>]

On 11/15/05, Boyce, Keith Garry <Kei...@bc...> wrote:
>
> Well I need to do something before and after the exception view is
> displayed.
>
> Actually I don't see from the code how interceptors get a handle on
> exception. From what I see if exception is raised interceptors are never
> called again.

Look at afterCompletion, which will be called after any outcome of a
handler execution (including if it throws an exception).  The only
time it won't get called is if preHandle returns true.

Seth

Re: [Springframework-developer] CVS HEAD dedicated to Spring 1.3

[Magnus H. <ma...@fi...>]

http://opensource2.atlassian.com/projects/spring/browse/SPR?report=3Dcom.at=
lassian.jira.plugin.system.project:roadmap-panel

2005/11/15, Michael E. Moores <mm...@re...>:
>
> is there a doc that has some details on what v1.3 will be?
>

--

/Magnus Heino

Re: [Springframework-developer] CVS HEAD dedicated to Spring 1.3

[Michael E. M. <mm...@re...>]

is there a doc that has some details on what v1.3 will be?

Juergen Hoeller wrote:

>Everybody,
>
>CVS HEAD is now finally dedicated to Spring 1.3 development. A maintenance
>branch "mbranch-1-2" serves for any future work in the 1.2.x line.
>
>During the course of this week, we will move already prepared 1.3 features
>from the sandbox over to the main sources. Starting with this, the nightly
>snapshots will be 1.3 RC1 previews, already containing 1.3 features.
>
>Cheers,
>
>Juergen
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
>Register for a JBoss Training Course.  Free Certification Exam
>for All Training Attendees Through End of 2005. For more info visit:
>http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>  
>

RE: [Springframework-developer] Improvement: I need a way to have code run after exception is raised from mvc handler.

[Boyce, K. G. <Kei...@bc...>]

Well I need to do something before and after the exception view is
displayed.=0D

Actually I don't see from the code how interceptors get a handle on
exception. From what I see if exception is raised interceptors are never
called again.

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf
Of Seth Ladd
Sent: Tuesday, November 15, 2005 2:42 AM
To: spr...@li...
Subject: Re: [Springframework-developer] Improvement: I need a way to
have code run after exception is raised from mvc handler.

On 11/14/05, Boyce, Keith Garry <Kei...@bc...> wrote:
>
> Yes the exception resolver allows you to resolve exception to view but

> there is no current way I found to apply interceptor to it.

I'm sorry, I don't follow.  Why do you need to apply an interceptor to
it?

Note that interceptors can get a handle on the exception that was
thrown, if that's what you are looking for.

Seth


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam for All
Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id=16845&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer


This message is a PRIVATE communication.
If you are not the intended recipient, please do not read, copy,
or use it, and do not disclose it to others. Please notify the
sender of the delivery error by replying to this message, and then
delete it from your system. Thank you.

Re: [Springframework-developer] Scripting support (in sandbox)

[Rob H. <rob...@in...>]

I wasn't much really - instantiation aware BPP doesn't work for  
factory-methods so I just moved that piece of functionality  to a  
different part of the logic. I did a general walk through the code  
seeing where we could simplify things at the same time. Hopefully, I  
will be able to add this to the main tree very soon.

Rob
On 14 Nov 2005, at 18:26, Seth Ladd wrote:


> Rob,
>
>
>
>> This issue will be resolved as part of the 1.3RC1 release. I have  
>> mostly
>> resolved the problem now and I will be updating the code when it  
>> moves over into
>> the main source tree.
>>
>>
>
> Great news.  Can you explain what you did to fix it?  IIR it was a
> couple of reasons why the reload didn't work.
>
> Or, I guess I can just wait for the code to drop. :)
>
> Seth
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server.  
> Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>

Re: [Springframework-developer] Improvement: I need a way to have code run after exception is raised from mvc handler.

[Seth L. <set...@gm...>]

On 11/14/05, Boyce, Keith Garry <Kei...@bc...> wrote:
>
> Yes the exception resolver allows you to resolve exception to view but
> there is no current way I found to apply interceptor to it.

I'm sorry, I don't follow.  Why do you need to apply an interceptor to it?

Note that interceptors can get a handle on the exception that was
thrown, if that's what you are looking for.

Seth

RE: [Springframework-developer] Improvement: I need a way to have code run after exception is raised from mvc handler.

[Boyce, K. G. <Kei...@bc...>]

Yes the exception resolver allows you to resolve exception to view but
there is no current way I found to apply interceptor to it.=0D

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf
Of Seth Ladd
Sent: Monday, November 14, 2005 9:50 PM
To: spr...@li...
Subject: Re: [Springframework-developer] Improvement: I need a way to
have code run after exception is raised from mvc handler.

Have you looked into the Exception Resolvers ?  Or Handler Interceptors?

On 11/14/05, Boyce, Keith Garry <Kei...@bc...> wrote:
>
> I need a way to have code run after exception is raised from mvc=0D
> handler basically to do some stuff before and after the exception view

> is displayed. Is that something that can be added to framework.=0D
> Basically I need some code to run in order to prepare the error view=0D
> and after the view is displayed I need to clean up some information=0D
> including possibly the exception so in the case of portlet mvc the=0D
> next time the view is rendered I want it to display the view from the=0D
> default handler rather than the exception again which is what is
currently happening.
>
> This message is a PRIVATE communication.
> If you are not the intended recipient, please do not read, copy, or=0D
> use it, and do not disclose it to others. Please notify the sender of=0D
> the delivery error by replying to this message, and then delete it=0D
> from your system. Thank you.
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today=0D
> Register for a JBoss Training Course.  Free Certification Exam for All

> Training Attendees Through End of 2005. For more info visit:
> http://ads.osdn.com/?ad_idv28&alloc_id=16845&opclick
> _______________________________________________
> Springframework-developer mailing list=0D
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam for All
Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id=16845&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer


This message is a PRIVATE communication.
If you are not the intended recipient, please do not read, copy,
or use it, and do not disclose it to others. Please notify the
sender of the delivery error by replying to this message, and then
delete it from your system. Thank you.

Re: [Springframework-developer] Improvement: I need a way to have code run after exception is raised from mvc handler.

[Seth L. <set...@gm...>]

Have you looked into the Exception Resolvers ?  Or Handler Interceptors?

On 11/14/05, Boyce, Keith Garry <Kei...@bc...> wrote:
>
> I need a way to have code run after exception is raised from mvc handler
> basically to do some stuff before and after the exception view is
> displayed. Is that something that can be added to framework. Basically I
> need some code to run in order to prepare the error view and after the
> view is displayed I need to clean up some information including possibly
> the exception so in the case of portlet mvc the next time the view is
> rendered I want it to display the view from the default handler rather
> than the exception again which is what is currently happening.
>
> This message is a PRIVATE communication.
> If you are not the intended recipient, please do not read, copy,
> or use it, and do not disclose it to others. Please notify the
> sender of the delivery error by replying to this message, and then
> delete it from your system. Thank you.
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
> Register for a JBoss Training Course.  Free Certification Exam
> for All Training Attendees Through End of 2005. For more info visit:
> http://ads.osdn.com/?ad_idv28&alloc_id=16845&opclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>

[Springframework-developer] Improvement: I need a way to have code run after exception is raised from mvc handler.

[Boyce, K. G. <Kei...@bc...>]

I need a way to have code run after exception is raised from mvc handler
basically to do some stuff before and after the exception view is
displayed. Is that something that can be added to framework. Basically I
need some code to run in order to prepare the error view and after the
view is displayed I need to clean up some information including possibly
the exception so in the case of portlet mvc the next time the view is
rendered I want it to display the view from the default handler rather
than the exception again which is what is currently happening.

This message is a PRIVATE communication.
If you are not the intended recipient, please do not read, copy,
or use it, and do not disclose it to others. Please notify the
sender of the delivery error by replying to this message, and then
delete it from your system. Thank you.

[Springframework-developer] CVS HEAD dedicated to Spring 1.3

[Juergen H. <ju...@in...>]

Everybody,

CVS HEAD is now finally dedicated to Spring 1.3 development. A maintenance
branch "mbranch-1-2" serves for any future work in the 1.2.x line.

During the course of this week, we will move already prepared 1.3 features
from the sandbox over to the main sources. Starting with this, the nightly
snapshots will be 1.3 RC1 previews, already containing 1.3 features.

Cheers,

Juergen

[Springframework-developer] Spring Framework 1.2.6 released

[Juergen H. <ju...@in...>]

Dear Spring community,

I'm pleased to announce that Spring 1.2.6 has finally 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.

See the changelog for details.

Cheers,

Juergen

-----
Juergen Hoeller
Interface21 - Spring Services from the Source
http://www.springframework.com