Re: Spring Action Instantiation
I'm using the spring id only. On 6/19/07, Adam Ruggles [EMAIL PROTECTED] wrote: Are you specifying the entire class name in the action mapping definition instead of using the spring bean id? [EMAIL PROTECTED] 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Scott [EMAIL PROTECTED]
Re: Spring Action Instantiation
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]
Re: Spring Action Instantiation
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]
Re: Spring Action Instantiation
Oooop! The struts.xml change did not force the context to reload! Now that I have changed the class in the action mapping to the fully qualified class name, it *is* being instantiated on each request! So why is it not working with the Spring bean id? On 6/20/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: 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] -- Scott [EMAIL PROTECTED]
Re: Spring Action Instantiation
Assuming Spring is your AOP framework Logging is now an Advised entity to be injected at compile time or runtime via 'pointcut' details on implementation are located here http://www.devx.com/Java/Article/30799/0/page/1 to quote 'Because this FactoryBean concept is how Spring wraps beans and then creates a proxy for the bean (using some internal tool such as dynamic proxies, CGLIB, etc.) that executes some advice on method calls when the pointcut says the method is a joinpoint (assuming a pointcut is defined). ' M-- This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: [EMAIL PROTECTED] To: Struts Users Mailing List user@struts.apache.org Sent: Wednesday, June 20, 2007 9:45 AM Subject: Re: Spring Action Instantiation 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Spring Action Instantiation
?! --- Martin Gainty [EMAIL PROTECTED] wrote: Assuming Spring is your AOP framework Logging is now an Advised entity to be injected at compile time or runtime via 'pointcut' details on implementation are located here http://www.devx.com/Java/Article/30799/0/page/1 to quote 'Because this FactoryBean concept is how Spring wraps beans and then creates a proxy for the bean (using some internal tool such as dynamic proxies, CGLIB, etc.) that executes some advice on method calls when the pointcut says the method is a joinpoint (assuming a pointcut is defined). ' M-- This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: [EMAIL PROTECTED] To: Struts Users Mailing List user@struts.apache.org Sent: Wednesday, June 20, 2007 9:45 AM Subject: Re: Spring Action Instantiation 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on, when. http://tv.yahoo.com/collections/222 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Spring Action Instantiation
Spring is my IOC container. So are you suggesting Spring is *not* instantiating action classes on each request? I am confused that it would be creating the beans used by the actions on each invocation but not the action itself. Also, I am not sure how Spring could advise which methods to call on a dirty action class without *some* advice from me! On 6/20/07, Martin Gainty [EMAIL PROTECTED] wrote: Assuming Spring is your AOP framework Logging is now an Advised entity to be injected at compile time or runtime via 'pointcut' details on implementation are located here http://www.devx.com/Java/Article/30799/0/page/1 to quote 'Because this FactoryBean concept is how Spring wraps beans and then creates a proxy for the bean (using some internal tool such as dynamic proxies, CGLIB, etc.) that executes some advice on method calls when the pointcut says the method is a joinpoint (assuming a pointcut is defined). ' M-- This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: [EMAIL PROTECTED] To: Struts Users Mailing List user@struts.apache.org Sent: Wednesday, June 20, 2007 9:45 AM Subject: Re: Spring Action Instantiation 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Scott [EMAIL PROTECTED]
Re: Spring Action Instantiation
On 20/06/07, Dave Newton [EMAIL PROTECTED] wrote: ?! I didn't understand a word of that either :-) --- Martin Gainty [EMAIL PROTECTED] wrote: Assuming Spring is your AOP framework Logging is now an Advised entity to be injected at compile time or runtime via 'pointcut' details on implementation are located here http://www.devx.com/Java/Article/30799/0/page/1 to quote 'Because this FactoryBean concept is how Spring wraps beans and then creates a proxy for the bean (using some internal tool such as dynamic proxies, CGLIB, etc.) that executes some advice on method calls when the pointcut says the method is a joinpoint (assuming a pointcut is defined). ' M-- This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: [EMAIL PROTECTED] To: Struts Users Mailing List user@struts.apache.org Sent: Wednesday, June 20, 2007 9:45 AM Subject: Re: Spring Action Instantiation 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on, when. http://tv.yahoo.com/collections/222 - 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]
Re: Spring Action Instantiation
That should be it, and scope=prototype has always done the trick for me, why don't you post relevant parts of the spring conf file? regards musachy On 6/20/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Oooop! The struts.xml change did not force the context to reload! Now that I have changed the class in the action mapping to the fully qualified class name, it *is* being instantiated on each request! So why is it not working with the Spring bean id? On 6/20/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: 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] -- Scott [EMAIL PROTECTED] -- Hey you! Would you help me to carry the stone? Pink Floyd
Re: Spring Action Instantiation
!-- Actions --
bean id=pufAction class=actions.PayrollUpdateAction
scope=prototype
property name=payrollUpdate ref=anUpdate/
/bean
!-- Add actions here --
action name=PayrollUpdate_* method={1} class=pufAction
result name=inputPayrollUpdate/result
result name=listPayrollUpdate_list/result
result name=addPayrollUpdate/result
result name=showPayrollUpdate/result
result name=editPayrollUpdate/result
result name=destroyPayrollUpdate/result
result name=notes
type=chainPayrollUpdateNotes_list/result
/action
On 6/20/07, Musachy Barroso [EMAIL PROTECTED] wrote:
That should be it, and scope=prototype has always done the trick for me,
why don't you post relevant parts of the spring conf file?
regards
musachy
On 6/20/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Oooop! The struts.xml change did not force the context to reload! Now
that
I have changed the class in the action mapping to the fully qualified
class
name, it *is* being instantiated on each request! So why is it not
working
with the Spring bean id?
On 6/20/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
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]
--
Scott
[EMAIL PROTECTED]
--
Hey you! Would you help me to carry the stone? Pink Floyd
--
Scott
[EMAIL PROTECTED]
Re: Spring Action Instantiation
That looks right to me :)
musachy
On 6/20/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
!-- Actions --
bean id=pufAction class=actions.PayrollUpdateAction
scope=prototype
property name=payrollUpdate ref=anUpdate/
/bean
!-- Add actions here --
action name=PayrollUpdate_* method={1} class=pufAction
result name=inputPayrollUpdate/result
result name=listPayrollUpdate_list/result
result name=addPayrollUpdate/result
result name=showPayrollUpdate/result
result name=editPayrollUpdate/result
result name=destroyPayrollUpdate/result
result name=notes
type=chainPayrollUpdateNotes_list/result
/action
On 6/20/07, Musachy Barroso [EMAIL PROTECTED] wrote:
That should be it, and scope=prototype has always done the trick for
me,
why don't you post relevant parts of the spring conf file?
regards
musachy
On 6/20/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Oooop! The struts.xml change did not force the context to
reload! Now
that
I have changed the class in the action mapping to the fully qualified
class
name, it *is* being instantiated on each request! So why is it not
working
with the Spring bean id?
On 6/20/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
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]
--
Scott
[EMAIL PROTECTED]
--
Hey you! Would you help me to carry the stone? Pink Floyd
--
Scott
[EMAIL PROTECTED]
--
Hey you! Would you help me to carry the stone? Pink Floyd
Spring Action Instantiation
It appears as though I am not getting a new Action instance created for each req -- Scott [EMAIL PROTECTED]
Spring Action Instantiation
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
Re: Spring Action Instantiation
Are you specifying the entire class name in the action mapping definition instead of using the spring bean id? [EMAIL PROTECTED] 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Spring Action Instantiation
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]
