Hi list!

I have updated the issue TAP5-1321 with a new patch. It can also be pulled from my git, git://hetdiana.dyndns.org/tapestry5.git branch 1321.

What it does is it adds a getService to the ObjectLocator interface that allows callers to get a service using just the interface and the markers.

Now, there is an issue that might be up to debate: how to use @Local ? My solution is to allow callers to use the module builder class instead of Local.class. e.g.:

getService(Example.class, MyExampleTapestryModule.class, SomeMarker.class);

This is equivalent to an injected service "@Local @SomeMarker" from a service implementation of Example provided by MyExampleTapestryModule.

Also, the patch adds a getService to the InternalRegistry interface for ObjectLocatorImpl, that uses the Module object instead of the module builder class, because ObjectLocatorImpl has access to the internal Module object.

Feedback appreciated!

Regards,
Tom.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to