Howard Lewis Ship wrote:
[..]
I kind of think that if you can't find a true purpose for the base
class beyond a convienient place for the common injections, then
perhaps you are on the wrong track.
Well, now that you explain me that, I think it's my problem. I almost
only use the base page/component as a container for common
services/logic. But as you said, it should be better suited to create
new services than a base page for that, and only use them where they are
needed.
I kind of like the list of
injections in my components ... it's kind of like a cast of characters
in a play.
And I completely agree with that.
In each component, I use a really visible comment to hilight the
injected services : just with that, I can (almost) know what the
component is going to do, or at least what may be its side effects.
So, it's a really good reason to inject services every time they are
really need.
Ok, so I should build more unit services, make some facade for logically
linked services... Well, just really use the power of Tapestry services ;)
Thank you really much for the advices, and I believe I'm going to remove
this needless base page :)
--
Francois Armand
Etudes & Développements J2EE
Groupe Linagora - http://www.linagora.com
Tél.: +33 (0)1 58 18 68 28
-----------
InterLDAP - http://interldap.org
FederID - http://www.federid.org/
Open Source identities management and federation
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
