[ https://jira.jboss.org/jira/browse/ARQ-53?page=com.atlassian.jira.plugin.... ] Aslak Knutsen updated ARQ-53: ----------------------------- Component/s: Core -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/ARQ-53?page=com.atlassian.jira.plugin.syste... ] Aslak Knutsen updated ARQ-53: ----------------------------- Fix Version/s: 1.0.0.Beta1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ARQ-53?page=com.atlassian.jira.plugin.sys... ] Aslak Knutsen updated ARQ-53: ----------------------------- Fix Version/s: 1.1.0.CR1 (was: 1.0.0.Beta1) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ARQ-53?page=com.atlassian.jira.plugin.sys... ] Vineet Reynolds edited comment on ARQ-53 at 10/9/11 5:57 AM: ------------------------------------------------------------- Support for this is possibly dependent on the container. For example, building support for this feature in Glassfish, might be easy, as the existing Arquillian integration for remote Glassfish uses the REST. The Glassfish REST interface allows for retrieval of the domain log file contents using the view-log (Log Viewer) resource (exposed at http://adminhost:adminport/management/domain/view-log , in the case of a Glassfish domain containing only a DAS). It also allows for log file deltas to be fetched using the "X-Text-Append-Next" header. Likewise, similar features must exist in other containers operated in remote mode, so that the container log contents during test execution can be reproduced at the client. This might not be necessary for embedded containers (definitely not for embeddded Glassfish), as they typically operate in the same JVM as the client. was (Author: vineet.reynolds): Support for this is possibly dependent on the container. For example, building support for this feature in Glassfish, might be easy, as the existing Arquillian integration for remote Glassfish uses the REST. The Glassfish REST interface allows for retrieval of the domain log file contents using the view-log (Log Viewer) resource (exposed at http://adminhost:adminpost/management/domain/view-log , in the case of a Glassfish domain containing only a DAS). It also allows for log file deltas to be fetched using the "X-Text-Append-Next" header. Likewise, similar features must exist in other containers operated in remote mode, so that the container log contents during test execution can be reproduced at the client. This might not be necessary for embedded containers (definitely not for embeddded Glassfish), as they typically operate in the same JVM as the client. -- 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