[ https://issues.jboss.org/browse/AS7-3560?page=com.atlassian.jira.plugin.s... ] Robert Reimann updated AS7-3560: -------------------------------- Environment: Affected versions: nightly build #486 and current HEAD Description: During the deployment the ConnectionFactory is not registered/bound for rar deployments inside an ear. See https://github.com/rreimann/jboss-as/commit/6c5868677e5079b573c6d2af2b5bd... for a testcase. Please notice: Although the [ra config|https://github.com/rreimann/jboss-as/blob/6c5868677e5079b573c6d2af...] contains "ear_packaged.ear#ear_packaged.rar" as archive name the resorce-adapter is created with just "ear_packaged.ear" as archive name. Disabling the tearDown and manually editing of the archive name doesn't change the result the ConnectionFactory is still not bound. Putting the exported ear and the corresponding ra config (ear_packaged.xml) into nightly build #431 works as expected. The first time i noticed this issue was while updating to nightly build #486. So it must be introduced between #431 and #486. was: During the deployment the ConnectionFactory is not registered/bound for rar deployments inside an ear. See https://github.com/rreimann/jboss-as/commit/6c5868677e5079b573c6d2af2b5bd... for a testcase. Please notice: Although the test config ear_packaged.xml contains "ear_packaged.ear#ear_packaged.rar" as archive name the resorce-adapter is created with just "ear_packaged.ear" as archive name. Disabling the tearDown and manually editing of the archive name doesn't change the result the ConnectionFactory is still not bound. Putting the exported ear and the corresponding ra config (ear_packaged.xml) into nightly build #431 works as expected. The first time i noticed this issue was while updating to nightly build #486. So it must be introduced between #431 and #486. Forum Reference: https://community.jboss.org/message/649670#649670 (was: https://community.jboss.org/message/649670#649670) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira