I replaced the spring bean id in my action mapping with the fully qualified class name to rule Spring out completely. I am still never seeing the log4j output in the constructor of my action class! I have double checked my log4j.properties and the debug output would be written out if the constructor were called.
Any ideas? Could this have anything to do with an interceptor? On 6/20/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I'm using Spring 2.x and the attribute scope="prototype" On 6/19/07, Zarar Siddiqi <[EMAIL PROTECTED] > wrote: > > > It sounds to me like your Action class might be configured as a > singleton. > If that's the case the action class' constructor would only be called > once > on startup. Make sure you have singleton="false" in your Spring config > for > the action class. The default value for singleton is true. > > > > stanlick wrote: > > > > It appears as though I am not getting a new Action instance created > for > > each > > request! I have placed a logging statement in the constructor of my > > Action > > class and it is not emitting output. The Bean inside the Action *is* > > emitting log statements from its constructor so I must have the Spring > > beans > > wired correctly. I am injecting both the Actions and Action Beans via > > > Spring. I have scope=prototype on them both. > > > > Any ideas? > > > > Thanks, > > Scott > > > > > > -- > View this message in context: > http://www.nabble.com/Spring-Action-Instantiation-tf3948840.html#a11205652 > Sent from the Struts - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Scott [EMAIL PROTECTED]
-- Scott [EMAIL PROTECTED]
