Return-Path: X-Original-To: apmail-ignite-issues-archive@minotaur.apache.org Delivered-To: apmail-ignite-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E971C18384 for ; Mon, 7 Dec 2015 13:10:21 +0000 (UTC) Received: (qmail 62722 invoked by uid 500); 7 Dec 2015 13:10:11 -0000 Delivered-To: apmail-ignite-issues-archive@ignite.apache.org Received: (qmail 62503 invoked by uid 500); 7 Dec 2015 13:10:11 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 62269 invoked by uid 99); 7 Dec 2015 13:10:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Dec 2015 13:10:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 4B8162C1F85 for ; Mon, 7 Dec 2015 13:10:11 +0000 (UTC) Date: Mon, 7 Dec 2015 13:10:11 +0000 (UTC) From: "Artem Shutak (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (IGNITE-1864) Cannot configure jndiNames for CacheJndiTmLookup MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Shutak updated IGNITE-1864: --------------------------------- Fix Version/s: (was: 1.6) 1.5 > 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)