[JBoss JIRA] (ARQGRA-408) Provide SPI for custom @Location resolution
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-408?page=com.atlassian.jira.plugin... ]
Lukáš Fryč commented on ARQGRA-408:
-----------------------------------
Stefan, if you implement that SPI, we can surely include it in a 2.1 alpha release.
> Provide SPI for custom @Location resolution
> -------------------------------------------
>
> Key: ARQGRA-408
> URL: https://issues.jboss.org/browse/ARQGRA-408
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Reporter: Stefan Miklosovic
> Priority: Minor
> Fix For: 2.1-Tracking
>
>
> While working with page fragments in Arquillian Droidium for ftesting on Android, I am quite close to be able to use proper page objects with @Location annotations on activities and that in turn means that I could use @InitialPage for native Android activities as well.
> Right now, I am starting Android activities like this (1) however I would like to encapsulate activity as the abstraction of a web page like this (2) into @Page and use @Location of it so that activity will be automatically open for me when I do @InitialPage so I get rid of that manual starting of the activity as seen in (1) and I just more stick to Graphene way of doing things.
> The problem is that an activity is started differently, to be concrete, I need to call something like
> {code}
> browser.get("and-activity://activityName");
> {code}
> and I need to do some internal matching of activities to WebDrivers.
> To be concrete, follow the link (3).
> From what I understood, that whole @Location logic is implemented in LocationEnricher the resolution of that url is in getURLFromLocation method. Since it would be theoretically possible to use @Location("and-activity://someActivity"), I would like to see SPI for doing of these things out of Graphene where I could add custom schemes to already existing ones or I could supress the standard behaviour so I can resolve and open locations according to my needs.
> (1)
> https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidi...
> (2) https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidi...
> (3) https://github.com/arquillian/arquillian-droidium/blob/master/droidium-na...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (ARQGRA-408) Provide SPI for custom @Location resolution
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-408?page=com.atlassian.jira.plugin... ]
Lukáš Fryč updated ARQGRA-408:
------------------------------
Fix Version/s: 2.1-Tracking
> Provide SPI for custom @Location resolution
> -------------------------------------------
>
> Key: ARQGRA-408
> URL: https://issues.jboss.org/browse/ARQGRA-408
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Reporter: Stefan Miklosovic
> Priority: Minor
> Fix For: 2.1-Tracking
>
>
> While working with page fragments in Arquillian Droidium for ftesting on Android, I am quite close to be able to use proper page objects with @Location annotations on activities and that in turn means that I could use @InitialPage for native Android activities as well.
> Right now, I am starting Android activities like this (1) however I would like to encapsulate activity as the abstraction of a web page like this (2) into @Page and use @Location of it so that activity will be automatically open for me when I do @InitialPage so I get rid of that manual starting of the activity as seen in (1) and I just more stick to Graphene way of doing things.
> The problem is that an activity is started differently, to be concrete, I need to call something like
> {code}
> browser.get("and-activity://activityName");
> {code}
> and I need to do some internal matching of activities to WebDrivers.
> To be concrete, follow the link (3).
> From what I understood, that whole @Location logic is implemented in LocationEnricher the resolution of that url is in getURLFromLocation method. Since it would be theoretically possible to use @Location("and-activity://someActivity"), I would like to see SPI for doing of these things out of Graphene where I could add custom schemes to already existing ones or I could supress the standard behaviour so I can resolve and open locations according to my needs.
> (1)
> https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidi...
> (2) https://github.com/kpiwko/arquillian-safari/blob/master/arquillian-droidi...
> (3) https://github.com/arquillian/arquillian-droidium/blob/master/droidium-na...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (ARQGRA-409) Support for Ember.js
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-409?page=com.atlassian.jira.plugin... ]
Lukáš Fryč commented on ARQGRA-409:
-----------------------------------
Karel, I don't get the whole idea, you are saying Graphene could inject IDs, but afaik you would need to hook into Ember.js internal processes like creating View objects in order to be able assign ID.
It's certainly achievable with Graphene Page Extensions, however the right approach is an question. In my opinion, linked StackOverflow threads doesn't provide the answer.
----
Such framework specific extensions should be released separately,.not as part of a core.
+1 AngularJS extension, please create a separate issue if you are interested
> Support for Ember.js
> --------------------
>
> Key: ARQGRA-409
> URL: https://issues.jboss.org/browse/ARQGRA-409
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Components: core
> Affects Versions: 2.0.0.Final
> Reporter: Karel Piwko
>
> Ember.js dynamically updates view based on various action. This makes usage of locators and guards pretty complicated.
> It would be great it Graphene could provide:
> * A way how to stability ids for elements in DOM generated as a part of view
> * Guards that are able to guard DOM update without any request.
> [~smikloso] can provide more details, additional discussions at:
> http://stackoverflow.com/questions/12933422/ember-best-practices-with-sel...
> http://stackoverflow.com/questions/16639384/how-to-test-a-javascript-base...
> I believe that such tools might be handy for angular.js testing as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (ARQ-1555) Rest Extension clients should be decoupled from RestEasy
by John Ament (JIRA)
[ https://issues.jboss.org/browse/ARQ-1555?page=com.atlassian.jira.plugin.s... ]
John Ament commented on ARQ-1555:
---------------------------------
Actually, I think there's a bigger issue.
In order to use ArquillianResource, need to implement a ResourceProvider. However, the lookup method doesn't give you access to the class that was requested. For static resources, this works fine because you know the type expected. In this case, we use dynamic type invocation.
So, I think we need a core change to indicate the class to provide.
> Rest Extension clients should be decoupled from RestEasy
> --------------------------------------------------------
>
> Key: ARQ-1555
> URL: https://issues.jboss.org/browse/ARQ-1555
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - REST
> Reporter: John Ament
> Priority: Minor
>
> Currently, the annotation marking a REST client is "ArquillianResteasyResource", this implies that the client framework can only ever work with RestEasy. I would like to propose renaming this annotation ArquillianRestClient, which clearily identifies it as being useful to any Rest Client framework, and make it's clearer that it's a client API (not the resource itself).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (ARQ-1555) Rest Extension clients should be decoupled from RestEasy
by John Ament (JIRA)
[ https://issues.jboss.org/browse/ARQ-1555?page=com.atlassian.jira.plugin.s... ]
John Ament commented on ARQ-1555:
---------------------------------
The one issue I'm seeing is that they use produces/consumes annotations from JAX-RS to load the resource for dynamic producer/consumer strategies. These annotations cannot be placed on method parameters, only methods and types.
I can move these to a RestContext annotation.
> Rest Extension clients should be decoupled from RestEasy
> --------------------------------------------------------
>
> Key: ARQ-1555
> URL: https://issues.jboss.org/browse/ARQ-1555
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - REST
> Reporter: John Ament
> Priority: Minor
>
> Currently, the annotation marking a REST client is "ArquillianResteasyResource", this implies that the client framework can only ever work with RestEasy. I would like to propose renaming this annotation ArquillianRestClient, which clearily identifies it as being useful to any Rest Client framework, and make it's clearer that it's a client API (not the resource itself).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (ARQ-1565) "Falied to connect" with WebLogic included libraries
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/ARQ-1565?page=com.atlassian.jira.plugin.s... ]
Vineet Reynolds commented on ARQ-1565:
--------------------------------------
This looks like a classpath issue. The WebLogic Server libraries are leaking into the test classpath from the looks of it. I'm not sure why a communication error is encountered; probably some class is unavailable in the WebLogic library that would have usually been provided by the WL client JARs in WL_HOME.
> "Falied to connect" with WebLogic included libraries
> ----------------------------------------------------
>
> Key: ARQ-1565
> URL: https://issues.jboss.org/browse/ARQ-1565
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: WebLogic Containers
> Affects Versions: wls_1.0.0.Alpha2
> Environment: windows 7 64bits
> Reporter: Valtoni Boaventura
> Assignee: Vineet Reynolds
>
> In Wls 10.3.5, project working 100% without weblogic libraries in eclipse .
> Version: Kepler Release
> Build id: 20130614-0229
> With weblogic libraries, this connection error occur:
> {code}
> org.jboss.arquillian.container.spi.client.container.LifecycleException: Failed to obtain a connection to the MBean Server.
> at org.jboss.arquillian.container.wls.WebLogicJMXClient.createConnection(WebLogicJMXClient.java:485)
> at org.jboss.arquillian.container.wls.WebLogicJMXClient.<init>(WebLogicJMXClient.java:290)
> at org.jboss.arquillian.container.wls.remote_10_3.WebLogicContainer.start(WebLogicContainer.java:58)
> at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:256)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:167)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:68)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:78)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:80)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:68)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:69)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:97)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:684)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:391)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> Caused by: java.io.IOException
> at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:196)
> at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)
> at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)
> at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
> at org.jboss.arquillian.container.wls.WebLogicJMXClient.createConnection(WebLogicJMXClient.java:480)
> at org.jboss.arquillian.container.wls.WebLogicJMXClient.<init>(WebLogicJMXClient.java:290)
> at org.jboss.arquillian.container.wls.remote_10_3.WebLogicContainer.start(WebLogicContainer.java:58)
> at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:77)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:69)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:86)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:68)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:97)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> ... 1 more
> Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
> java.io.EOFException]
> at weblogic.jrmp.Context.lookup(Context.java:189)
> at weblogic.jrmp.Context.lookup(Context.java:195)
> at javax.naming.InitialContext.lookup(InitialContext.java:392)
> at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:179)
> ... 67 more
> Caused by: java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
> java.io.EOFException
> at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:286)
> at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
> at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322)
> at weblogic.jrmp.BaseRemoteRef.invoke(BaseRemoteRef.java:221)
> at weblogic.jrmp.RegistryImpl_Stub.lookup(Unknown Source)
> at weblogic.jrmp.Context.lookup(Context.java:185)
> at weblogic.jrmp.Context.lookup(Context.java:195)
> at javax.naming.InitialContext.lookup(InitialContext.java:392)
> at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:179)
> at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)
> at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)
> at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
> at org.jboss.arquillian.container.wls.WebLogicJMXClient.createConnection(WebLogicJMXClient.java:480)
> at org.jboss.arquillian.container.wls.WebLogicJMXClient.<init>(WebLogicJMXClient.java:290)
> at org.jboss.arquillian.container.wls.remote_10_3.WebLogicContainer.start(WebLogicContainer.java:58)
> at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:256)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:167)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:68)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:78)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$2.perform(ContainerLifecycleController.java:70)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forEachSuiteContainer(ContainerLifecycleController.java:221)
> at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startSuiteContainers(ContainerLifecycleController.java:80)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:68)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:69)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:97)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:684)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:391)
> ... 1 more
> Caused by: java.io.EOFException
> at java.io.DataInputStream.readByte(DataInputStream.java:250)
> at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:228)
> ... 75 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months