That sounds very similar to what that one person was trying to do with CDI injection
between different jboss-module modules.
----- Original Message -----
From: "Pete Muir" <pmuir(a)redhat.com>
To: "Jason Porter" <jporter(a)redhat.com>
Cc: jdf-dev(a)lists.jboss.org, "Stuart Douglas" <sdouglas(a)redhat.com>
Sent: Monday, July 2, 2012 11:41:49 AM
Subject: Re: [jdf-dev] Inter-module communication
Ah, sorry. Inter-JBoss-Module communication.
Stuart's planning to add the ability to use JBoss Modules as
"installed libraries", but some people actually want to deploy
modules as units, and then have the communicate.
On 2 Jul 2012, at 15:44, Jason Porter wrote:
> This is inter-module as in same EAR, different WARs? Or something
> else? I'm missing something here.
>
> ----- Original Message -----
>> From: "Pete Muir" <pmuir(a)redhat.com>
>> To: jdf-dev(a)lists.jboss.org
>> Sent: Thursday, June 28, 2012 6:34:11 PM
>> Subject: [jdf-dev] Inter-module communication
>>
>> One topic that came up repeatedly at JBossWorld was inter-module
>> communication using CDI. Jason came up with good pattern to
>> address
>> this, short term, involving EJB singletons, JNDI, and CDI producer
>> fields. In A.jar, we expose the service using @Singleton. In
>> B.jar,
>> we write an alias using a CDI producer field, that uses JNDI to
>> lookup the EJB reference. This allows us to cleanly declare what
>> should be exposed, will work today, and preseves the CDI
>> programming
>> model on both sides.
>>
>> I'll write a quickstart for this next week or two.
>> _______________________________________________
>> jdf-dev mailing list
>> jdf-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jdf-dev
>>