On Wed, 24 Aug 2011 15:09:07 -0300, Lenny Primak <lpri...@hope.nyc.ny.us>
wrote:
For example:
core.getServiceFiter().contribute(myTimingFilter)
Is this asking to add contributions after the service registry is
instantiated? If yes, I don't think this will ever be implemented because
this would change too much how Tapestry-IoC works. I could see this as an
alternative syntax to do service configuration contributions, but do we
really need two ways of doing the same thing? I don't think so.
core.getComponentResources().xxx();
ComponentResources is not a service at all. It's a way from one component,
class or mixin access methods and fields (indirectlyl) that were added by
Tapestry to these classes, so I can't see how this could be impelmented.
core.getApplicationDefaults.set();
Same as my first comment here.
core.getJavaScriptSupport().importLibrary();
JavaScriptSupport is an environmental object, not a service. This can be
implemented easily, but it would only work when JavaScriptSupport is
available (threads which are HTTP requests).
core.getFormSupport().xxx();
Same as above.
Basically, an interface that makes up 'core' services.
Obviously, not complete but I think the you can get the idea here.
A single service which provides getXXX() methods where XXX is some service
or environmental object? Which services and objects?
Basically, a simple, one entry-point into the guts of tapestry via an
API that's well defined rather than having to hunt for
cookbooks/javadocs/example code, etc.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
