Indeed, I wouldn't consider it a problem if the warning appears with two applications deployed. I would suggest also changing the warning message to point to cacheManagerName, not just allowDuplicateDomains.
Cheers Dan On Fri, Jan 23, 2015 at 12:02 PM, Sebastian Łaskawiec <slask...@redhat.com> wrote: > Hey Dan! > > Regarding to CDI Extension - yes, that's possible. > We can set it to "DefaultCDIManager" or something similar. On the other > hand it will cause the same exception if user deploys 2 applications and > each will use a Default CDI Producer (unfortunately CDI does not expose > any deployment information, so we can't use deployment name for that > purpose). Nevertheless I think that situation would be perfectly > acceptable. > > Thanks > Sebastian > > On 01/22/2015 10:41 AM, Dan Berindei wrote: > > Couldn't WildFly and the CDI provider both set a different > > globalJmxStatistics().cacheManagerName() for the cache managers they > > create? > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev >
_______________________________________________ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev
