I agree with Nils; I'd be double-checking the deployment etc. There's nothing obviously wrong (except that you say it doesn't work ;)
What happens if you throw an exception in the interceptor? In a *different* action? That could help diagnose a deployment issue, anyway. Dave --- Peter Theissen <[EMAIL PROTECTED]> wrote: > Hi, > > > > > Are you sure it isn't? > > > yes ;-) > > What happens if you return something other than SUCCESS from your action? > > > Unfortunately, exactly the same happens. > > That will test whether or not it's getting the result from the intercept > call > > or the action itself. > Now I returned Action.NONE and the System.out.println statement before > still didnt work. > > Are you able to see other sysout statements across the > > application? (Use a logger!) > Yes, I guess I can see them on the common Eclipse console > > > Are there any startup errors in your log? > Warnings are there: > log4j:WARN No appenders could be found for logger > (org.springframework.util.ClassUtils). > log4j:WARN Please initialize the log4j system properly. > > Is the > > action configured properly in Spring? > > > I hope so. But difficult to judge for a noob. Is there any part I should > examine > especially? > > Thanks for your time and help > Peter > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
