[ https://issues.jboss.org/browse/AS7-2667?page=com.atlassian.jira.plugin.s... ] Stuart Douglas commented on AS7-2667: ------------------------------------- A simple way to fix this is to simply detect the presence of this property in the integration code, and manually create a binder service (and remove the prop from the configuration that is actually passed to hibernate). This approach will work for all global contexts, wether they are writable or not. -- 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

[ https://issues.jboss.org/browse/AS7-2667?page=com.atlassian.jira.plugin.s... ] Scott Marlow updated AS7-2667: ------------------------------ Description: Applications that expect to bind objects to JNDI, are currently broken. Related jira AS7-421 was marked as fixed, but its not clear what that means (with regard to applications being able to bind to jndi). Forum Reference: http://community.jboss.org/message/636747 (was: http://community.jboss.org/message/636747) -- 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

[ https://issues.jboss.org/browse/AS7-2667?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-2667: ----------------------------------- John suggested that I try wrapping the code that binds, with something like: {code} WritableServiceBasedNamingStore.pushOwner(context.getChildTarget()); try { jmsManager.createConnectionFactory(false, configuration, configuration.getBindings()); } finally { WritableServiceBasedNamingStore.popOwner(); } {code} John also mentioned that if it is in a valid component (ejb, war, etc.) it should already be fine. I'll take this jira back and try this. -- 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

[ https://issues.jboss.org/browse/AS7-2667?page=com.atlassian.jira.plugin.s... ] Scott Marlow reassigned AS7-2667: --------------------------------- Assignee: Scott Marlow (was: John Bailey) -- 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

[ https://issues.jboss.org/browse/AS7-2667?page=com.atlassian.jira.plugin.s... ] Scott Marlow closed AS7-2667. ----------------------------- -- 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

[ https://issues.jboss.org/browse/AS7-2667?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-2667: ----------------------------------- Its an internal class org.jboss.msc.service.StartContext that represents the service start lifecycle event. -- 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