tance
> > created
> > > > > for
> > > > > > each
> > > > > > request! I have placed a logging statement in the constructor
> of
> > my
> > > > > > Action
> > > > > > class and it is not emitting outp
gt; > > > 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
on
> > > *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
- 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.
ave 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
> > >
>
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.
&
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.
--
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
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:
htt
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
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 bean
It appears as though I am not getting a new Action instance created for each
req
--
Scott
[EMAIL PROTECTED]
15 matches
Mail list logo
