That looks right to me :)
musachy
On 6/20/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
PayrollUpdate
PayrollUpdate_list
PayrollUpdate
PayrollUpdate
PayrollUpdate
PayrollUpdate
PayrollUpdate
PayrollUpdate_list
PayrollUpdate
PayrollUpdate
PayrollUpdate
PayrollUpdate
PayrollUpdateNotes_list
On 6/20/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:
That s
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 chan
- Original Message -----
> From: <[EMAIL PROTECTED]>
> To: "Struts Users Mailing List"
>
> 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 qual
e 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"
Sent: Wednesday, June 20, 2007 9:45 AM
Subject: Re: Spring Action Instantiation
>
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&qu
--- Original Message -
From: <[EMAIL PROTECTED]>
To: "Struts Users Mailing List"
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.
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 PROTE
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
constru
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 si
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
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
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
clas
13 matches
Mail list logo
