My latest use of IoC was to rewire my DAOs so that they accept a
DbConnectionFactory I @Inject in pages.
When a DAO method is called with an ASO holding a user's DB Connection
info, the injected factory's getConnection() is used.
For some factories, getConnection() will create a small connection
p
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 gene
We work with an application using multiple databases. So depending on
the logged user a different datasource might be used. Tapestry IoC made
it a breeze to hide this logic away from the pages and just @inject the
services.
We have a highly tier-ed application where all low lever logic is defi
Outside of framework building (of course) my more mundane tasks:
Building DAO services around Hibernate, to reduce code clutter.
Building a deferred job execution service, to process operations in
the background.
Integrating with significant subsystems, like Quartz.
Creating tools to allow page
