ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Semen Boikov (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-1864) Cannot configure jndiNames for CacheJndiTmLookup
Date Wed, 09 Dec 2015 08:26:11 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048278#comment-15048278
] 

Semen Boikov edited comment on IGNITE-1864 at 12/9/15 8:25 AM:
---------------------------------------------------------------

I have minor comments: CacheJndiTmLookup.getTm should throw exception if failed to find tm,
also please fix CacheJndiTmLookup test to restore modified system properties.


was (Author: sboikov):
I have minor comments: CacheJndiTmLookup.getTm should throw exception if failed to find tm,
also please fix CacheJndiTmLookup test to resotore modified system properties.

> Cannot configure jndiNames for CacheJndiTmLookup 
> -------------------------------------------------
>
>                 Key: IGNITE-1864
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1864
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>            Reporter: Yakov Zhdanov
>            Assignee: Artem Shutak
>            Priority: Critical
>             Fix For: 1.5
>
>
> Since user have an ability to configure only lookup class name via org.apache.ignite.configuration.TransactionConfiguration#getTxManagerLookupClassName,
he lacks ability to properly configure all of its properties.
> This seems to be a general problem for this approach



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message