What you do is the following:
- you configure a service in hivemind, normally using an interface.
- you configure an implementation for the service, also in hivemind.
- you inject the service to the component (using the interface in the
method signature), and hivemind creates an instance for you. The page is
not involved.
If you want to inject different implementations of the same interface to
different components, making the decision on the page level, use a
normal component parameter.
Cheers,
Ron
Didier LAFFORGUE wrote:
Hi guys,
I'm creating a new component for Tapestry 4.0 and I have a big question about
hivemind and its integration in my component.
If my component uses a hivemind service, is it possible to "inject" an implementation of
this service when I declare my component in a page ? In this case, my component will use only the
"interface" of the service and I should declare the implementation in the hivemind.xml of
my application. Is it right ?
Best regards.
Didier
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
