On Wed, 28 Mar 2012 18:03:39 -0300, Howard Lewis Ship <hls...@gmail.com>
wrote:
HiveMind, the predecessor to Tapestry IoC, had private services &
visibility. In my opinion, it caused more problems than it was worth.
What I'm hearing is a basic lack of trust between one developer and
another within your team. One possible solution there is to work on
that, or better documentation about how your services are meant to be
used.
You can never make things simple by adding complexity. Adding privacy
will increase complexity, and add whole new ambiguities ... such as
who can see a service in order for it to be advised or decorated.
Agreed. By the way, Tapestry itself has many services that aren't supposed
to be used outside it. In other words, private services. The solution? Put
them under org.apache.tapestry5.internal and have a big warning in the
documentation about not using them.
--
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: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
