Hi,

I think you could have an ioc module for each customer (each customers code
in his own "project") - and then just drop in the right jar and have it
autoload.

-- 
Chris


On Thu, Oct 6, 2011 at 4:03 PM, Jose Luis Sanchez <
joseluis.sanc...@m-centric.com> wrote:

>
>
> Hi guys !
>
> I do need some behaviour in Tapestry already available to me via CDI in a
> non-web Application.
>
> Let me explain myself :
>
> I have a product, made for different customers.
>
> The product is the same, but for some different implementations of common
> services each one has.
>
> For example :
>
>
> com.mycompany.product.service.**customer1.SubscribeService
> com.mycompany.product.service.**customer2.SubscribeService
> com.mycompany.product.service.**customer3.SubscribeService
>
>
> In CDI ( Using weld ), y do use the beans.xml file facility to populate the
> service for the desired customer.
> Then, in the code all i need is invoking the @Inject into a service, and i
> will get the customer X service  at my disposal.
>
> But in Tapestry, i do not know how to implement this.
>
> I believe that dinamically adding a service to  the /public static void
> bind(ServiceBinder binder)/ in the AppModule is not the wright way to
> achieve it.
>
>
> May any of you help me with this ? I do not need any runtime behaviour,
> just compile time.
>
> Thanks everyone, and long life to Tapestry ! ( So to Howard and all the
> maintainers, of course  :) )
>
>
>
> --
> *Jose Luis Sanchez*
> Senior Developer
>
> *E-mail*: joseluis.sanc...@m-centric.com
> *Phone* : +34 91 277 03 16
> mCentric mobilising imagination
>
>
> c/ Jose Echegaray, 8 Building 3
> 28230 Las Rozas (Madrid). SPAIN.
>
> This message may contain confidential information or privileged material,
> and is intended only for the individual(s) named. If you are not in the
> named addressee you should not disseminate, distribute or copy this e-mail.
> Please notify the sender immediately by e-mail if you have received this
> e-mail by mistake and delete this e-mail from your system E-mail
> transmission cannot be guaranteed to be secured or error-free as information
> could be intercepted, corrupted, lost, destroyed, arrive late or incomplete,
> or contain viruses. The sender therefore does not accept liability for any
> errors or omissions in the contents of this message which arise as a result
> of e-mail transmission. If verification is required please request a
> hard-copy version.
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: 
> users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org>
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>

Reply via email to