<div dir="ltr">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.<div><br></div><div>Cheers</div><div>Dan</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 23, 2015 at 12:02 PM, Sebastian Łaskawiec <span dir="ltr"><<a href="mailto:slaskawi@redhat.com" target="_blank">slaskawi@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey Dan!<br>
<br>
Regarding to CDI Extension - yes, that's possible.<br>
We can set it to "DefaultCDIManager" or something similar. On the other<br>
hand it will cause the same exception if user deploys 2 applications and<br>
each will use a Default CDI Producer (unfortunately CDI does not expose<br>
any deployment information, so we can't use deployment name for that<br>
purpose). Nevertheless I think that situation would be perfectly acceptable.<br>
<br>
Thanks<br>
<span class="HOEnZb"><font color="#888888">Sebastian<br>
</font></span><span class="im HOEnZb"><br>
On 01/22/2015 10:41 AM, Dan Berindei wrote:<br>
> Couldn't WildFly and the CDI provider both set a different<br>
> globalJmxStatistics().cacheManagerName() for the cache managers they<br>
> create?<br>
<br>
</span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</div></div></blockquote></div><br></div>