[JBoss JIRA] (ARQ-986) Add more advanced exception matching logic in @ShouldThrowException
by Ivan St. Ivanov (JIRA)
[ https://issues.jboss.org/browse/ARQ-986?page=com.atlassian.jira.plugin.sy... ]
Work on ARQ-986 started by Ivan St. Ivanov.
> Add more advanced exception matching logic in @ShouldThrowException
> -------------------------------------------------------------------
>
> Key: ARQ-986
> URL: https://issues.jboss.org/browse/ARQ-986
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Deployable Containers SPI
> Reporter: Dan Allen
> Assignee: Ivan St. Ivanov
> Priority: Minor
> Fix For: 2.0.0.Beta1
>
>
> The @ShouldThrowException assertion for a deployment should support more intelligent exception matching similar to what was implemented for Seam Catch. A single exception class compared to the outer most exception often isn't sufficient. If nothing else, we should unwrap the exception and try the match for each exception in the stack.
--
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, 3 months
[JBoss JIRA] (ARQ-986) Add more advanced exception matching logic in @ShouldThrowException
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-986?page=com.atlassian.jira.plugin.sy... ]
Aslak Knutsen updated ARQ-986:
------------------------------
Assignee: Ivan St. Ivanov
> Add more advanced exception matching logic in @ShouldThrowException
> -------------------------------------------------------------------
>
> Key: ARQ-986
> URL: https://issues.jboss.org/browse/ARQ-986
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Deployable Containers SPI
> Reporter: Dan Allen
> Assignee: Ivan St. Ivanov
> Priority: Minor
> Fix For: 2.0.0.Beta1
>
>
> The @ShouldThrowException assertion for a deployment should support more intelligent exception matching similar to what was implemented for Seam Catch. A single exception class compared to the outer most exception often isn't sufficient. If nothing else, we should unwrap the exception and try the match for each exception in the stack.
--
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, 3 months
[JBoss JIRA] (ARQ-1488) CDI Injection not working in WebSphere Containers
by Gerhard Poul (JIRA)
[ https://issues.jboss.org/browse/ARQ-1488?page=com.atlassian.jira.plugin.s... ]
Gerhard Poul commented on ARQ-1488:
-----------------------------------
Tested this on a Windows test machine and it works with an instance that has the following features enabled:
<!-- Enable features -->
<featureManager>
<feature>jsp-2.2</feature>
<feature>localConnector-1.0</feature>
<feature>cdi-1.0</feature>
<feature>ejbLite-3.1</feature>
</featureManager>
will test on Linux and then document what features might be required or further investigate the root cause.
> CDI Injection not working in WebSphere Containers
> -------------------------------------------------
>
> Key: ARQ-1488
> URL: https://issues.jboss.org/browse/ARQ-1488
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: WebSphere Containers
> Affects Versions: was_1.0.0.Alpha1
> Reporter: Gerhard Poul
> Assignee: Gerhard Poul
> Priority: Critical
> Fix For: was_1.0.0.next
>
>
> On all WAS containers that support CDI Injection the @Inject annotation in test classes is not working.
--
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, 3 months
[JBoss JIRA] (ARQ-1444) Oracle does not support query delimiter inside statements
by Josef Schauer (JIRA)
[ https://issues.jboss.org/browse/ARQ-1444?page=com.atlassian.jira.plugin.s... ]
Josef Schauer commented on ARQ-1444:
------------------------------------
We try the same for db2 and get an error, too.
It's the same reason like the error in oracle.
Caused by: org.jboss.arquillian.test.spi.ArquillianProxyException: com.ibm.db2.jcc.am.SqlSyntaxErrorException : DB2 SQL Error: SQLCODE=-104, SQLSTATE=42601, SQLERRMC=;;DELETE FROM ADDRESS;END-OF-STATEMENT, DRIVER=3.65.77 [Proxied because : Original exception not deserilizable, ClassNotFoundException]
> Oracle does not support query delimiter inside statements
> ---------------------------------------------------------
>
> Key: ARQ-1444
> URL: https://issues.jboss.org/browse/ARQ-1444
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Persistence
> Affects Versions: persistence_1.0.0.Alpha6
> Environment: Oracle Database.
> Reporter: Michel Graciano
> Assignee: Bartosz Majsak
>
> When we try to use @ApplyScriptBefore and the script file has more than one statement, we use ; as delimiter. The problem is that the delimiter is not removed from the statement before run it, so Oracle database return the following exception:
> Caused by: java.sql.SQLSyntaxErrorException: ORA-00911: invalid character
--
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, 3 months