[ https://issues.jboss.org/browse/ARQ-985?page=com.atlassian.jira.plugin.sy... ] Jakub Narloch reassigned ARQ-985: --------------------------------- Assignee: Aslak Knutsen (was: Jakub Narloch) -- 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/ARQ-985?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-985: ------------------------------ Status: Open (was: Pull Request Sent) Git Pull Request: https://github.com/arquillian/arquillian-extension-spring/pull/3 (was: https://github.com/arquillian/arquillian-extension-spring/pull/3) jmnarloch: I'm going to reconsider this issue, I still see the need of registering the the context on client side, but in different form. I was thinking about introducing seperate annotations for configuring that e.g. @SpringClientConfiguration. -- 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/ARQ-985?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen commented on ARQ-985: ----------------------------------- food for thought: A Client side integration like this does make me wonder if there should be two 'containers' in play. One for the client and one for the server, the client testing the server. Basically two deployments targeting different containers. Similar to this is the Weld containers where it would be interesting to test a SE CDI Client against a Remote Server. Or even deploying JavaScript clients to a JavaScript Engine Container and test Ajax request against another container. -- 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/ARQ-985?page=com.atlassian.jira.plugin.sy... ] Jakub Narloch commented on ARQ-985: ----------------------------------- Now corect me if I'm wrong, but will this have any chance to work with embedded container? Assuming that the XmlClientApplicationContextProducer will create the instance of TestScopeApplicationContext and then the XmlRemoteApplicationContextProducer will be run and create in CDI context new TestScopeApplicationContext, will that completly overide the previouse one? -- 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/ARQ-985?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen commented on ARQ-985: ----------------------------------- *sigh* Seems the comment i made got lost in a jira black hole.. In a remote container there will be a client side TestScope and a DeploymentScope active as well as a container TestScope. With embedded the deployment generated ApplicationContext should be in DeploymentScope and the client ApplicationContext in TestScope, but the problem is that both of those are active during a TestMethod execution so it'll be 'random' which instance you get. In a remote container this is no problem since you would be executing in a different TestScope located in a different jvm. So while they will be technically contained in different scopes, you still don't have control over which to use. -- 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/ARQ-985?page=com.atlassian.jira.plugin.sy... ] Jakub Narloch edited comment on ARQ-985 at 8/9/12 1:59 PM: ----------------------------------------------------------- I should be able to overcome that with a custom ClientScope/RemoteScope that would be used within *ClientApplicationContextProducer/*RemoteApplicationContextProducer respectivly, right? Or maybe you have some better idea? was (Author: jmnarloch): I should be able to overcome that with a custom ClientScope/RemoteScope that would be used for *ClientApplicationContextProducer/*RemoteApplicationContextProducer, right? Or maybe you have some better idea? -- 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/ARQ-985?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-985: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done pushed upstream https://github.com/arquillian/arquillian-extension-spring/commit/7056ade4... -- 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/ARQ-985?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen closed ARQ-985. ----------------------------- -- 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