[JBoss JIRA] (AG-110) Support non-standard transaction isolation levels
by Luis Barreiro (Jira)
[ https://issues.jboss.org/browse/AG-110?page=com.atlassian.jira.plugin.sys... ]
Luis Barreiro resolved AG-110.
------------------------------
Resolution: Done
The support for custom Tx isolation levels has been added to the library. It still requires changes to the Wildfly model.
> Support non-standard transaction isolation levels
> -------------------------------------------------
>
> Key: AG-110
> URL: https://issues.jboss.org/browse/AG-110
> Project: Agroal
> Issue Type: Enhancement
> Components: api
> Affects Versions: 1.4
> Reporter: Rich DiCroce
> Assignee: Luis Barreiro
> Priority: Major
> Fix For: 1.5
>
>
> Some databases support non-standard transaction isolation levels. For example, MS SQL Server has a SNAPSHOT isolation level. Agroal currently can't support this via the transaction isolation level config option because TransactionIsolation is an enum, so it can't have custom values. It would be nice if this were supported. WildFly's "old" datasources subsystem already supports non-standard isolation levels, so it would be nice if the Agroal subsystem had parity.
> There is a workaround, at least on MS SQL Server. initialSql (new-connection-sql in WildFly) can be used to execute "SET TRANSACTION ISOLATION LEVEL SNAPSHOT" when the connection is created.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3839) Implement import popup into Scenario
by Daniele Zonca (Jira)
Daniele Zonca created DROOLS-3839:
-------------------------------------
Summary: Implement import popup into Scenario
Key: DROOLS-3839
URL: https://issues.jboss.org/browse/DROOLS-3839
Project: Drools
Issue Type: Task
Components: Scenario Simulation and Testing
Reporter: Daniele Zonca
Assignee: Gabriele Cardosi
Implement a popup to import csv file into scenario and enable import feature
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-11870) abstract classes with @EJB annotation included in libraries will cause deployment failures
by Tomas Hofman (Jira)
[ https://issues.jboss.org/browse/WFLY-11870?page=com.atlassian.jira.plugin... ]
Tomas Hofman reassigned WFLY-11870:
-----------------------------------
Assignee: Tomas Hofman (was: Brian Stansberry)
> abstract classes with @EJB annotation included in libraries will cause deployment failures
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-11870
> URL: https://issues.jboss.org/browse/WFLY-11870
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Server
> Reporter: Wolf-Dieter Fink
> Assignee: Tomas Hofman
> Priority: Major
> Labels: Regression, deployment, injection
> Attachments: ReproducerInjection.zip
>
>
> If an archive include libraries with interfaces and abstract classes the deployment will fail if there are annotations for injection like @EJB.
> Only if the injected EJB is available within the deployed file (or any other deployment) it is possible to deploy it.
> As the abstract class can not cause any instance the failure does not make sense.
> Also former versions are deploying the same file correct and work fine.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month