[JBoss JIRA] (ARQGRA-214) Support for enriching by Page Objects and Page Fragments declared as nested classes
by Juraj Húska (JIRA)
Juraj Húska created ARQGRA-214:
----------------------------------
Summary: Support for enriching by Page Objects and Page Fragments declared as nested classes
Key: ARQGRA-214
URL: https://issues.jboss.org/browse/ARQGRA-214
Project: Arquillian Graphene
Issue Type: Feature Request
Components: core, ftest
Affects Versions: 2.0.0.Alpha2
Reporter: Juraj Húska
Assignee: Juraj Húska
This approach can be used for inner classes:
{code}
Class<?> outerClass = declaredClass.getDeclaringClass();
// check whether declared page object is not nested class
if (outerClass != null) {
Constructor<?> construtor = declaredClass.getDeclaredConstructor(new Class[] { outerClass });
page = construtor.newInstance(new Object[] { outerClass.newInstance() });
} else {
page = declaredClass.newInstance();
}
{code}
There is need for finding way of initializing static nested classes.
It has to be done both for Page Objects and Page Fragments initialization.
--
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, 2 months
[JBoss JIRA] (ARQGRA-195) Page Fragment Enricher fail with no context to where
by Aslak Knutsen (JIRA)
Aslak Knutsen created ARQGRA-195:
------------------------------------
Summary: Page Fragment Enricher fail with no context to where
Key: ARQGRA-195
URL: https://issues.jboss.org/browse/ARQGRA-195
Project: Arquillian Graphene
Issue Type: Enhancement
Components: core
Affects Versions: 2.0.0.Alpha2
Reporter: Aslak Knutsen
{code}
@FindBy(xpath = "//a[@id='name']")
private String name;
{code}
casue:
{code}
java.lang.IllegalStateException: cannot set referenced element!
at org.jboss.arquillian.graphene.enricher.Factory.initializePageFragment(Factory.java:106)
at org.jboss.arquillian.graphene.enricher.PageFragmentsEnricher.initPageFragmentsFields(PageFragmentsEnricher.java:163)
at org.jboss.arquillian.graphene.enricher.PageFragmentsEnricher.initFieldsAnnotatedByFindBy(PageFragmentsEnricher.java:78)
at org.jboss.arquillian.graphene.enricher.PageFragmentsEnricher.enrich(PageFragmentsEnricher.java:57)
at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52)
....
{code}
The exception should contain which Field was attempted injected and of what type
--
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, 2 months
[JBoss JIRA] (ARQ-1175) Prepare Transaction Alpha2
by Aslak Knutsen (JIRA)
Aslak Knutsen created ARQ-1175:
----------------------------------
Summary: Prepare Transaction Alpha2
Key: ARQ-1175
URL: https://issues.jboss.org/browse/ARQ-1175
Project: Arquillian
Issue Type: Release
Security Level: Public (Everyone can see)
Components: Extension - Transaction
Reporter: Aslak Knutsen
Assignee: Aslak Knutsen
Fix For: transaction_1.0.0.Alpha2
--
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, 2 months
[JBoss JIRA] (ARQ-1137) Provide a way to alter logic determining if transaction support is required
by Bartosz Majsak (JIRA)
Bartosz Majsak created ARQ-1137:
-----------------------------------
Summary: Provide a way to alter logic determining if transaction support is required
Key: ARQ-1137
URL: https://issues.jboss.org/browse/ARQ-1137
Project: Arquillian
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Extension - Transaction
Affects Versions: transaction_1.0.0.Alpha1
Reporter: Bartosz Majsak
Assignee: Bartosz Majsak
Fix For: transaction_1.0.0.next
APE don't explicitly require @Transactional annotation to be present in order to wrap tests in the transaction, but it is apparentely required by new implementation. Therefore I think we can provide optional SPI called
TransactionEnabler or sth like that where we can alter this behaviour and if it's not present we simply used to the current implementation defined in the method.
--
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, 2 months
[JBoss JIRA] (ARQ-1155) Make JNDI transaction name configurable
by Bartosz Majsak (JIRA)
Bartosz Majsak created ARQ-1155:
-----------------------------------
Summary: Make JNDI transaction name configurable
Key: ARQ-1155
URL: https://issues.jboss.org/browse/ARQ-1155
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Transaction
Reporter: Bartosz Majsak
Assignee: Bartosz Majsak
Fix For: transaction_1.0.0.next
JTA transaction jndi should be configurable through arquillian.xml as it is currently done in Persistence Extension.
--
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, 2 months
[JBoss JIRA] (ARQ-1074) TransactionProvider should be supported on client side
by Aslak Knutsen (JIRA)
Aslak Knutsen created ARQ-1074:
----------------------------------
Summary: TransactionProvider should be supported on client side
Key: ARQ-1074
URL: https://issues.jboss.org/browse/ARQ-1074
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Transaction
Affects Versions: transaction_1.0.0.Alpha1
Reporter: Aslak Knutsen
Fix For: transaction_1.0.0.next
We should support automating TransactionManagement for the Client side as well as for in container.
A TransactionProvider could register it self to be in Client context. This will allow for embedded service containers to provide their own hooks without reloading the AuxiliaryArchives as it's done by Remote Containers.
--
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
12 years, 2 months