[JBoss JIRA] (ARQ-1534) There is no way how to set server port of Android Debug Bridge
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1534?page=com.atlassian.jira.plugin.s... ]
Karel Piwko commented on ARQ-1534:
----------------------------------
Stefan,
there are plenty of examples where we provide a convenience setup in Arquillian for system/env property. For instance chromedriver binary is by default referenced by system property. You can easily grab a property from arquillian.xml, set a system/env property by Java code before executing the code that needs it and remove it later on. Asking people to work on CLI simply does not make sense here.
> There is no way how to set server port of Android Debug Bridge
> --------------------------------------------------------------
>
> Key: ARQ-1534
> URL: https://issues.jboss.org/browse/ARQ-1534
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Droidium
> Affects Versions: droidium_1.0.0.Alpha2
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
>
> *Given*:
> I have Android tooling installed in Eclipse/JBDS.
> *When:*
> I use Droidium in tests fro IDE.
> *Expect*:
> No having any errors in DDMS output in IDE.
> *Additional information*:
> It looks like that the problem is that Droidium does not allow to set android bridge server port and hence DDMS is already connected to given port. This leads to various errors logged, as DDMS is not prepared to handle external process changing it's environment on the fly.
> See AndroidDebugBridge.determineAndValidateAdbPort() method for more details. While Drodium allows you to change adbPort for running emulator, it always runs the bridge on default port 5037.
> We need a way how to change this server port in Droidium configuration.
--
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
11 years, 2 months
[JBoss JIRA] (ARQ-1473) JUnit @Before and @After cause nested transaction
by Bartosz Majsak (JIRA)
[ https://issues.jboss.org/browse/ARQ-1473?page=com.atlassian.jira.plugin.s... ]
Bartosz Majsak commented on ARQ-1473:
-------------------------------------
That said it's not really about @Before and @After. Many thanks for reporting and sharing the project!
> JUnit @Before and @After cause nested transaction
> -------------------------------------------------
>
> Key: ARQ-1473
> URL: https://issues.jboss.org/browse/ARQ-1473
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Transaction
> Affects Versions: 1.0.0.Alpha3
> Reporter: jieryn jieryn
> Assignee: Bartosz Majsak
> Priority: Minor
>
> @Before and @After methods on embedded containers cause a nested transaction, which are often not supported, leading to an exception.
> I confirmed this bug with aslak on IRC.
--
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
11 years, 2 months
[JBoss JIRA] (ARQ-1473) JUnit @Before and @After cause nested transaction
by Bartosz Majsak (JIRA)
[ https://issues.jboss.org/browse/ARQ-1473?page=com.atlassian.jira.plugin.s... ]
Bartosz Majsak commented on ARQ-1473:
-------------------------------------
By looking at events invocation calls this is what happens with the current implementation
(E) Before
(I) TestContextHandler.createSuiteContext
(I) TestContextHandler.createClassContext
(E) TestClass
(I) TestContextHandler.createTestContext
(I) ContainerEventController.createBeforeContext
(O) TransactionHandler.startTransactionBeforeTest
----------------------------> Starting transactiontestInject1
(E) BeforeTransactionStarted
(E) OpenEJBRuntimeException
(E) OpenEJBRuntimeException
(E) After
(I) TestContextHandler.createSuiteContext
(I) TestContextHandler.createClassContext
(E) TestClass
(I) TestContextHandler.createTestContext
(I) ContainerEventController.createAfterContext
(O) ClientBeforeAfterLifecycleEventExecuter.on
(E) NullPointerException
(E) NullPointerException
And end transaction is never called. Here's the [root cause of NPE|https://gist.github.com/bartoszmajsak/7205691] (most likely constraints on the data).
After changing precedence of the events (to have transactions start early enough) tests are green again. Side note: don't really like the idea of testing for EJBException but at least that shows us the problem :)
Fix on the way.
> JUnit @Before and @After cause nested transaction
> -------------------------------------------------
>
> Key: ARQ-1473
> URL: https://issues.jboss.org/browse/ARQ-1473
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Transaction
> Affects Versions: 1.0.0.Alpha3
> Reporter: jieryn jieryn
> Assignee: Bartosz Majsak
> Priority: Minor
>
> @Before and @After methods on embedded containers cause a nested transaction, which are often not supported, leading to an exception.
> I confirmed this bug with aslak on IRC.
--
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
11 years, 2 months
[JBoss JIRA] (ARQ-1554) Review and improve javadoc
by Bartosz Majsak (JIRA)
Bartosz Majsak created ARQ-1554:
-----------------------------------
Summary: Review and improve javadoc
Key: ARQ-1554
URL: https://issues.jboss.org/browse/ARQ-1554
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Transaction
Affects Versions: transaction_1.0.0.Alpha3
Reporter: Bartosz Majsak
Priority: Minor
Before release next major version javadoc needs to be reviewed and improved where necessary.
--
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
11 years, 2 months
[JBoss JIRA] (ARQ-1553) Warp: Diverge Proxy as independent extension to allow reuse by other extensions
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1553?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1553:
----------------------------
Summary: Warp: Diverge Proxy as independent extension to allow reuse by other extensions (was: Warp: Diverge Proxy to allow reuse by other extensions)
> Warp: Diverge Proxy as independent extension to allow reuse by other extensions
> -------------------------------------------------------------------------------
>
> Key: ARQ-1553
> URL: https://issues.jboss.org/browse/ARQ-1553
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha5
> Reporter: Lukáš Fryč
>
> Some extensions might reuse proxy between client and server to modify request/response or attach arbitrary data/payload.
> Some candidates to be part of this extension:
> * HTTP proxy - LittleProxy integration
> * OperationalContexts (might be rather part of core)
--
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
11 years, 2 months
[JBoss JIRA] (ARQ-1553) Warp: Diverge Proxy to allow reuse by other extensions
by Lukáš Fryč (JIRA)
Lukáš Fryč created ARQ-1553:
-------------------------------
Summary: Warp: Diverge Proxy to allow reuse by other extensions
Key: ARQ-1553
URL: https://issues.jboss.org/browse/ARQ-1553
Project: Arquillian
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Extension - Warp
Affects Versions: warp_1.0.0.Alpha5
Reporter: Lukáš Fryč
Some extensions might reuse proxy between client and server to modify request/response or attach arbitrary data/payload.
Some candidates to be part of this extension:
* HTTP proxy - LittleProxy integration
* OperationalContexts (might be rather part of core)
--
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
11 years, 2 months