you said that you know which service you should use at compilation time ? you can create 1 module for the interface and 3 separate modules (aka component library) one for each implementation (and contribution) and include one of them in your build conditionally(for example, with maven or ant or gradle).
In this way, you develop only the first time and you can use there modules in many webapp. I hope that helps. 2011/10/6 josete <mual...@gmail.com> > Thanks thiago, but that's not ideal for me, as i do not know at runtime > which > module i will use. > > My ideal is to bind the service at compilation time, and i think i've found > the solution in my previous posts, just by defining a system property of > -Dtapestry.execution-mode=customer1. > > That way, the system will @inject the customer1 app module, with itself, > defines the desired customer1 behaviour. > > By using the registry, i think i'm doing 2-3 more steps than just using the > tapestry.execution variable. > > Is there a way to handle this without the tapestry.execution logic ? > > Thanks ! > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Tapestry-and-CDI-the-need-for-tp4876507p4876947.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
