AFAIK its the same in the manner you can inject it anywhere.
Its not the same when accessing your object from other services and when
accessing services from your object.
If you use the ASO as a service instead of as a *state* container, you
should configure it as a hivemind (or spring) service instead.
There are some benfits to that:
lazy initialization (which might also happen on the ASO, but I *think*
services are more lazy - which means, they will be created only uppon
calling a method, and not on accessing the object itself).
Autowiring and wiring- the service can use other services and other
services can use this one, at the best seamlessly...
Cheers,
Ron
ציטוט Jesse Kuhnert:
No I think you are basically right, but there is a lot more going on than
you describe.
ApplicationObjects don't have any other special construct within hivemind
than any other service configuration contribution...Other than the fact that
howard has made most of the inner workings of tapestry
configurable/constructed via hivemind. Almost any aspect of the system can
be found as a service within hivemind. Once you get beyond a basic
understanding of tapestry it would behoove most people to become very
familiar with hivemind.
It's not any harder to grock than spring though. It's the same exact thing,
only it happens to be used directly by tapestry for almost everything.
If you download the tacos demo war application you can start to get a better
feel for how these things start interacting..The demo web-inf configures
only one service (SiteMap), but if you look at the tacos source under
net.sf.tacos you will find a few more hivemodule.xml files used to configure
and allow tacos to integrate into tapestry.
jesse
On 10/27/05, Henri Dupre <[EMAIL PROTECTED]> wrote:
It seems to me that a hivemind service is similar to a contribution to
ApplicationObjects with scope "application". Is this true or am I
getting lost in hivemind?
Thanks,
Henri.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
