"ozizka(a)redhat.com" wrote : legacy code which worked Actually, it might have not work, because the deployable name changed too, so it started throwing the ex. Anyway, I understand that the common case is that the developer expects the deployment to be in place rather than not, but even in that case, throwing an exception in case of no matches is easy enough to let it up to the caller, opposed to the handling of the exception. Or, a findMatchingDeploymentNames() alternative could be available. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262544#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...