I found this paper which describes a method of implementing a generic
DAO using Spring advisor/interceptor to catch some method calls and
route them to queries stored in hibernate mappings... It sounds pretty
cool so I wanted to try it in hivemind....
http://www-128.ibm.com/developerworks/java/library/j-genericdao.html
(At the end they describe a 'A reusable DAO class')
I guess one option is to create my own service model to create a proxy
for each instance so I can add interceptors to it.
-Aj
James Carman wrote:
Off the top of my head, I don't think that's possible at the moment.
HiveMind uses one outer proxy for each service point (from what I
remember). Do you need it to remember state across calls from the
same caller? If not, you might try implementing a "prototype" model,
which vends out a new one for each method invocation (can get
expensive, though). What exactly is it that you're trying to do?
Maybe we can help you come up with an alternative that HM supports
"out of the box."
On 10/20/06, *Aj Gregory* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
I'm looking for a method so each proxy delegates to it's own instance
which is unique to that proxy....
Ultimately what I'm trying to do is create a service-point which vends
out a proxy to an instance so I can create an interceptor on the
proxy
to implement some of the methods from the interface and pass other
method calls to the instance wrapped in the proxy...
Has anybody done something similar?
-Aj
James Carman wrote:
> You can use the "threaded" model. That would give you a unique
> instance for each thread (or web request if you're writing a
webapp).
> HiveMind doesn't really inject the implementation object into other
> objects. It injects a proxy. The proxy will make sure it
delegates
> to the appropriate implementation object based on the service
> lifecycle model.
>
> On 10/20/06, *Aj Gregory* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
> <mailto: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>> wrote:
>
> Is there some way to create a service-point so it will
create a new
> instance of an implementation class each time the service is
injected
> somewhere? Kinda the exact opposite of singleton.
>
> Thanks,
> -Aj
>
>
