Hello,
I am trying to add a new flavor of service dependency to iPojo. It's
purpose in life is to provide the dynamic-proxy approach to service
tracking. I.e. it will make iPojo a bit like Spring Dynamic Modules -
but without the tons of XML and with a nicer architecture ;P
I need this because:
1) I want to propagate the service dependencies from components into
collaborator objects.
2) I don't want to create anonymous proxies manually and have iPojo
instrument them. Too verbose.
3) I want to use collections for the aggregate services rather than arrays.
4) I will not be using this in an embedded device so the performance
overhead of proxies is not that much of an issue (the proxies I have
here make the coast of a method call equal to about 1.5 the coast of a
normal Java synchronized method call).
At the same time I still want to retain all the the other goodies iPojo
adds to the normal service dependencies. After looking for a while at
the DependencyHandler, Dependency, DependencyCallback classes I came to
the conclusion that I need to code my dependency stuff directly from
PrimitiveHandler :(
If you have an idea what can I extend to reuse most of that code -
please tell me.
Fortunately with the exception of compositions I seem to have everything
else implemented already. From the DependencyHandler code it seems the
composition support is relatively easy to add. The last bit that worries
me is this:
ProvidedServiceHandler refers to the DependencyHandler. It seems it
needs to check if all incoming dependencies are valid before it can
register a component as a service. So it seems I will have to code both
the service registration and the service consumption. Or is there a way
I can code just the service consumption and still get the registration
check out my dependencies for validity?
Cheers,
Todor
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
