[ https://issues.jboss.org/browse/AS7-3287?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen reassigned AS7-3287: ------------------------------------ Assignee: Stefano Maestri (was: Jesper Pedersen) Looks like the wrong description is returned for the operation -- 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-3287?page=com.atlassian.jira.plugin.s... ] Jan Martiska commented on AS7-3287: ----------------------------------- I mean deployment through the UI of admin console. After you create a deployment through the UI, it doesn't appear in JNDI naming list (in the console).. and viewing its runtime metrics (also in the console) will cause an error: "failure-description" => "JBAS014739: No handler for read-resource at address [ (\"subsystem\" => \"datasources\"), (\"data-source\" => \"testdatasource\"), (\"statistics\" => \"jdbc\") the only way to fix it is to trigger a server reload. -- 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-3287?page=com.atlassian.jira.plugin.s... ] Stefano Maestri edited comment on AS7-3287 at 1/19/12 5:16 AM: --------------------------------------------------------------- No, there is another solution: call :enable on the datasource. DS are created disabled, but can be enabled w/o server reload calling the :enable operation that is designed exactly for this purpose. Note also that editing an existing ds require a reload if you edit an enabled ds. You can call :disable on a ds, edit it (w/o reload) and the re-enable it (w/o reload) calling :enable I'll investigate why read-resource give an error and/or if it's possible to catch it and return a more descriptive message. Note also that an automatic enable can't be triggered because the user may need to add connection-properties subresource (and HAVE TO add xa-datasource-properties for xa ds) before the ds can be enabled. enable and disable operation have been designed exactly to avoid a full server reload to add and edit DSes I'll keep the jira open only for investigation about error returned by read-resource, not to change the behavior and changing the priority to minor was (Author: maeste): No, there is another solution: call :enable on the datasource. DS are created disabled, but can be enabled w/o server reload calling the :enable operation that is designed exactly for this purpose. Note also that editing an existing ds require a reload if you edit an enabled ds. You can call :disable on a ds, edit it (w/o reload) and the re-enable it (w/o reload) calling :enable -- 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-3287?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-3287: ----------------------------- Assignee: Heiko Braun (was: Stefano Maestri) Fix Version/s: 7.1.0.Final -- 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-3287?page=com.atlassian.jira.plugin.s... ] Jan Martiska closed AS7-3287. ----------------------------- -- 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