I would agree that once one is familiar with Spring, the way in which
commons-chain is heavily geared towards its own XML config can be a bit
challenging to ones design. I have had decent success creating chains and
commands in Spring, but I use them by knowing that they are in the Spring
Applica
Antonio is correct. I was trying to create a Struts 1.3 Spring Command
to autowire my actions. The code is 95% from Spring's 1.2 version
(AutowireRequestProcessor), but then I realized I had no way to
initialize the instance variables which are needed.
In the old RP, there was an init() method
2007/2/22, Wendy Smoak <[EMAIL PROTECTED]>:
(I never got very far with Spring + Commons Chain, but as Antonio
suggests, that could be another option.)
Oops sorry, I confused Command with Action!
I don't know if Spring can inject beans in commands, sorry again :-(
Antonio
On 2/21/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
I can't even make that assumption in Struts? I should be able to assume
how the Struts Chain works for a Struts Command. But in terms of a
solution, what do you suggest? I find it implausible there is no way for
a command to perform first-time
If we are talking about application scope, then any member could do
the initialization. It need not be the command, but could be a Struts
1 "PlugIn".
On 2/21/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
Niall Pemberton wrote:
> The Commands have access to the application scope through the contex
2007/2/22, Paul Benedict <[EMAIL PROTECTED]>:
I was thinking of adding a ServletAwareCommand
interface which a Command can implement to accept the ActionServlet, so
it can access other pieces of data from the web application.
It seems like Dependency Injection, why don't use Spring to accomplis
I can't even make that assumption in Struts? I should be able to assume
how the Struts Chain works for a Struts Command. But in terms of a
solution, what do you suggest? I find it implausible there is no way for
a command to perform first-time initialization in Struts.
Paul
Martin Cooper wrot
On 2/21/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
One thing I noticed in s1 is that there is no way to initialize a
command. I am not speaking about the public constructor, but a way for a
servlet-aware command to perform first-time initialization before its
execute() method gets invoked.
Niall Pemberton wrote:
The Commands have access to the application scope through the context
- isn't that the best way to get any required resources that it needs
to use during execution?
Niall, the context is only available at invocation time. What about
first time setup? I cannot solve concur
On 2/22/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
One thing I noticed in s1 is that there is no way to initialize a
command. I am not speaking about the public constructor, but a way for a
servlet-aware command to perform first-time initialization before its
execute() method gets invoked.
Wha
One thing I noticed in s1 is that there is no way to initialize a
command. I am not speaking about the public constructor, but a way for a
servlet-aware command to perform first-time initialization before its
execute() method gets invoked.
What should be done? I was thinking of adding a Servle
11 matches
Mail list logo