I prefer tapestry-ioc over any other ioc implementation.Thats why i would
like to understand a little bit more about how everything is connected.Sure
anyone can initiate the ioc in some simple manner but for more advanced
things like type coercers,class transformations,instantiators,invalidation
hubs, things get little bit trickier and sometimes i find it difficult to
follow it in the source code of tapestry-core with so much abstraction
happening.
On Wed, Dec 21, 2011 at 6:36 PM, Dmitriy Vsekhvalnov <dvsekhval...@gmail.com
> wrote:
> well, i'm using tapestry-ioc alone with several projects, may be around
> ~10. I perfer it by many means to Spring as i were doing before with
> HiveMind.
>
> Here is how it is typically looks like with my projects:
>
> pom.xml
>
> <dependency>
> <groupId>org.apache.tapestry</groupId>
> <artifactId>tapestry-ioc</artifactId>
> <version>5.1.0.5</version>
> </dependency>
>
> Somewhere in the servlet init class (or may be Main class or any other
> entry point to your app):
>
> RegistryBuilder builder = new RegistryBuilder();
> builder.add(ServerModule.class); //add your own module
> builder.add(HibernateCoreModule.class); //add some other 3rd
> party or yours module, why not Hibernate :)
>
> And bind everything together in your ServerModule:
>
> public class ServerModule
> {
> private static final Logger slog = LoggerFactory.getLogger("SERVER");
> private static final Logger elog = LoggerFactory.getLogger("ERROR");
>
> public static void bind(ServiceBinder binder)
> {
> binder.bind(...);
> }
> }
>
> Have fun :)
>
>
>
>
>
>
> On Wed, Dec 21, 2011 at 7:19 PM, Dimitris Zenios
> <dimitris.zen...@gmail.com>wrote:
>
> > Maybe someone has to write a page on how tapestry core-works and how it
> > links tapestry-ioc with web applications.Many including me want to used
> > tapestry-ioc into their own applications but some times i find it very
> > difficult to understand how everything glues together in
> tapestry-core.Some
> > things just work automagically :)
> >
>
