[JBoss JIRA] (ARQ-1550) domain container - exception when connecting to existing domain without any servers
by Martin Simka (JIRA)
Martin Simka created ARQ-1550:
---------------------------------
Summary: domain container - exception when connecting to existing domain without any servers
Key: ARQ-1550
URL: https://issues.jboss.org/browse/ARQ-1550
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JBoss AS Containers
Affects Versions: 1.1.1.Final
Environment: remote domain without any servers
arquillian-bom 1.1.1.Final
jboss-as-arquillian-container-domain-remote 7.2.0.Final
Reporter: Martin Simka
{noformat}
(E) ManagerProcessing
(O) LoadableExtensionLoader.load
(E) ServiceLoader
(E) ManagerStarted
(O) ConfigurationRegistrar.loadConfiguration
(E) ArquillianDescriptor
(O) ContainerRegistryCreator.createRegistry
(E) ContainerRegistry
(O) ProtocolRegistryCreator.createRegistry
(E) ProtocolRegistry
(E) BeforeSuite
(I) TestContextHandler.createSuiteContext
(O) ContainerEventController.execute
(E) ContainerMultiControlEvent
(O) ContainerLifecycleController.setupContainers
(E) SetupContainer
(I) ContainerDeploymentContextHandler.createContainerContext
(O) ContainerLifecycleController.setupContainer
(E) BeforeSetup
(E) Container
(E) AfterSetup
(O) ClientContainerControllerCreator.createClientSideContainerController
(E) ContainerController
(O) ClientDeployerCreator.createClientSideDeployer
(E) Deployer
(E) ContainerMultiControlEvent
(O) ContainerLifecycleController.startSuiteContainers
(E) StartContainer
(I) ContainerDeploymentContextHandler.createContainerContext
(O) ContainerLifecycleController.startContainer
(E) BeforeStart
(E) ManagementClient
(E) ArchiveDeployer
(E) IllegalArgumentException
(E) IllegalArgumentException
(E) IllegalArgumentException
(E) IllegalArgumentException
(E) IllegalArgumentException
(E) IllegalArgumentException
java.lang.IllegalArgumentException: null
at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:124)
at org.jboss.dmr.ModelNode.keys(ModelNode.java:1194)
at org.jboss.as.arquillian.container.domain.ManagementClient.createDomain(ManagementClient.java:116)
at org.jboss.as.arquillian.container.domain.CommonDomainDeployableContainer.start(CommonDomainDeployableContainer.java:126)
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:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
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:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
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:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
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:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
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:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
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.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:159)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:87)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:95)
{noformat}
--
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
12 years, 5 months
[JBoss JIRA] (ARQ-1548) Be able to start parent activity of specified one for Droidium native
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1548?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic updated ARQ-1548:
-----------------------------------
Description:
Given:
I have activities which can be started via activity manager.
When:
I want to start some activity
Expect:
I can get the activity as string which is the parent of the specified one
Example:
{code}
ActivityManager manager = android.getActivityManagerProvider().getActivityManager();
String parentOfHome = manager.getParentOf("HomeScreenActivity");
manager.startActivity(parentOfHome);
{code}
Not every activity has its parent since the information about the parentship is parsed from aapt dump xmltree, in case there is not any parent activity found, return null or throw NotParentActivityFound runtime exception.
This could be also done other way around, when I have this information, I also know if some activity has some children
{code}
ActivityManager manager = android.getActivityManagerProvider().getActivityManager();
List<String> childrenActivities = manager.getChildrenOf("HomeScreenActivity");
manager.startActivity(childrenActivities.get(2)); // or whatever
{code}
was:
Given:
I have activities which can be started via activity manager.
When:
I want to start some activity
Expect:
I can get the activity as string which is the parent of the specified one
Example:
{code}
ActivityManager manager = android.getActivityManagerProvider().getActivityManager();
String parentOfHome = manager.getParentOf("HomeScreenActivity");
manager.startActivity(parentOfHome);
{code}
Not every activity has its parent since the information about the parentship is parsed from aapt dump xmltree, in case there is not any parent activity found, return null or throw NotParentActivityFound runtime exception.
> Be able to start parent activity of specified one for Droidium native
> ---------------------------------------------------------------------
>
> Key: ARQ-1548
> URL: https://issues.jboss.org/browse/ARQ-1548
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha2
> Reporter: Stefan Miklosovic
> Priority: Optional
>
> Given:
> I have activities which can be started via activity manager.
> When:
> I want to start some activity
> Expect:
> I can get the activity as string which is the parent of the specified one
> Example:
> {code}
> ActivityManager manager = android.getActivityManagerProvider().getActivityManager();
> String parentOfHome = manager.getParentOf("HomeScreenActivity");
> manager.startActivity(parentOfHome);
> {code}
> Not every activity has its parent since the information about the parentship is parsed from aapt dump xmltree, in case there is not any parent activity found, return null or throw NotParentActivityFound runtime exception.
> This could be also done other way around, when I have this information, I also know if some activity has some children
> {code}
> ActivityManager manager = android.getActivityManagerProvider().getActivityManager();
> List<String> childrenActivities = manager.getChildrenOf("HomeScreenActivity");
> manager.startActivity(childrenActivities.get(2)); // or whatever
> {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
12 years, 5 months
[JBoss JIRA] (ARQ-1548) Be able to start parent activity of specified one for Droidium native
by Stefan Miklosovic (JIRA)
Stefan Miklosovic created ARQ-1548:
--------------------------------------
Summary: Be able to start parent activity of specified one for Droidium native
Key: ARQ-1548
URL: https://issues.jboss.org/browse/ARQ-1548
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Droidium
Affects Versions: droidium_1.0.0.Alpha2
Reporter: Stefan Miklosovic
Priority: Optional
Given:
I have activities which can be started via activity manager.
When:
I want to start some activity
Expect:
I can get the activity as string which is the parent of the specified one
Example:
{code}
ActivityManager manager = android.getActivityManagerProvider().getActivityManager();
String parentOfHome = manager.getParentOf("HomeScreenActivity");
manager.startActivity(parentOfHome);
{code}
Not every activity has its parent since the information about the parentship is parsed from aapt dump xmltree, in case there is not any parent activity found, return null or throw NotParentActivityFound runtime exception.
--
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
12 years, 5 months
[JBoss JIRA] (ARQ-1547) Improve the parsing of activities from AndroidManifest.xml of AUT
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1547?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic commented on ARQ-1547:
----------------------------------------
wait for string "E: activity", then loop throught lines until "A: android:name" is found, parse the value, if it starts with dot, append it to parsed "A: package" value, otherwise add it as it is. Be sure to treat this case sensitively and filter out all other strings which contain "activity" string or some variation of it.
> Improve the parsing of activities from AndroidManifest.xml of AUT
> -----------------------------------------------------------------
>
> Key: ARQ-1547
> URL: https://issues.jboss.org/browse/ARQ-1547
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha2
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
>
> Current parsing of activities from AndroidManifest.xml during activity scanning is not sufficient. There are cases when parser gets lost like package contains "activity" string but parser relies on the appearance of that string somewhere else which ends up with IndexOutOfBoundException.
--
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
12 years, 5 months
[JBoss JIRA] (ARQ-1547) Improve the parsing of activities from AndroidManifest.xml of AUT
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1547?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic reassigned ARQ-1547:
--------------------------------------
Assignee: Stefan Miklosovic
> Improve the parsing of activities from AndroidManifest.xml of AUT
> -----------------------------------------------------------------
>
> Key: ARQ-1547
> URL: https://issues.jboss.org/browse/ARQ-1547
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha2
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
>
> Current parsing of activities from AndroidManifest.xml during activity scanning is not sufficient. There are cases when parser gets lost like package contains "activity" string but parser relies on the appearance of that string somewhere else which ends up with IndexOutOfBoundException.
--
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
12 years, 5 months