Wow, weird, I didn't get this reply until I saw it on the list today...
(from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by
ares.gofti.com (8.13.7/8.13.4) with ESMTP id k9A7sZhh025176 for
<[EMAIL PROTECTED]>; Tue, 10 Oct 2006 00:54:35 -0700)
The changes required are for the RequestProcessorFactoryFactory to look up the
objects from a pre-existing source. i.e. a RequestProcessorFactory may not
instantiate the object itself, but if it can delegate to another factory, then
this becomes possible for IoC containers such as Spring to do their work.
Jochen Wiedmann wrote:
Perry Nguyen wrote:
I chose StatelessRequestFactoryFactory as it seemed to be the best fit
for what I needed, it doesn't necessarily need to be so. However, it
is essential that Spring be in control of instantiating the service
object, since it allows Spring to inject dependencies as required
(jdbc connections, configuration, etc).
That's the point I am trying to make. What changes are required to use
let Spring create the service object?
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]