[jboss-as7-dev] Modularity is the spawn of Lucifer and a stinking donkey

Paul Ferraro paul.ferraro at redhat.com
Thu May 10 13:44:03 EDT 2012


On Thu, 2012-05-10 at 18:33 +0200, Ales Justin wrote:
> >> The problem as you can see is that deployment module cannot be found by
> >> plain ModuleLoader,
> >> but - I guess?- only by AS7' ServiceModuleLoader -- which has the
> >> deployment module info.
> >> 
> >> Do we already have such (based off ServiceML) ClassResolver?
> >> If yes, why it's not used?
> >> As I don't see how apps that use Infinispan (EDG?) can work w/o it (aka
> >> not having the same problem).
> > 
> > Yes it should be using the SML, it looks like its set up correctly in CacheContainerAdd.java:265. So not sure how it's getting the wrong value?
> 
> I'm cloning configurations from pre-defined configs (in infinispan.xml), for each app.
> Perhaps there is where it gets lost? <------- Paul
> (I've seen other configs get lost before :-))
> 
> Although, I don't know why plain ModuleLoader would then be used ...
> 
> -Ales

If you're loading cache configurations from infinispan.xml - they will
not be wired using the SML.  Only cache configurations defined in the
infinispan subsystem - or via the management API - will use this add
operation.  When you clone your cache configurations, you'll want to
wire them to use the ModularClassResolver via
ConfigurationBuilder.classResolver(...) method.

Paul



More information about the jboss-as7-dev mailing list