A Tapestry IoC service is just a bean. If you read up on Spring IoC or
Guice IoC they are all the same concepts and fulfill the same purposes.
Each might have slightly different features mechanisms, but you get the
idea. So if your question is truly academic, you should be reading up
on generic IoC concepts, sprint and guice as well.
The main design pattern used is around constructing singletons ( mostly:
general configuration, dao access, overriding tapestry logic, and
business logic with caching ). But you can have the IoC container
construct objects according to a scope, so it's not just a singleton
pattern, but a new object per request, (business logic that has state
specific to the current request only).
On 12/1/09 9:30 PM, Yeargan Yancey wrote:
I have a largely academic interest in Tapestry and have been following the list
for several months. I have seen many discussions go by about the technical
issues of implementing and using Tapestry IOC services. Recently, however, I
began to develop a persistent and growing curiosity about the sorts of tasks
that seasoned Tapestry developers decide to implement as IOC services; being
especially curious about complex combinations of such services. I suspect some
have come up with quite clever solutions and are just dying to share. Here's
your chance. I'm asking. What is it that your IOC services do?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
