[ https://issues.jboss.org/browse/ARQ-1513?page=com.atlassian.jira.plugin.s... ] Stefan Miklosovic commented on ARQ-1513: ---------------------------------------- The idea discussed with Karel is that in order to get rid of that warning message, you just can not use that property what in turn means we should "guess" that some particular container definition is related to some container adapter located on the class path. E.g. when qualifier contains jboss or there is some specific property used in container definition, it is very high chance that this container def will be related to container adapter class on the classpath of some jboss as adapter. This approach can be done with Android container as well. One disadvantage of this approach is that we would have to cover all container adapters a we would try to match them but I humbly guess having covered the recognition of just jbosses, glassfishes and android adapters is pretty much ok for almost any user. This warning gets printed only in the case there are more then one container adapter on classpath since we have to make difference between them. When you are using only one container adapter (like Android), you do not have to add adapterImplClass since there is exact matching between container definition and class on classpath implementing DeployableContainer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira