Return-Path: X-Original-To: apmail-ignite-user-archive@minotaur.apache.org Delivered-To: apmail-ignite-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A6726196B5 for ; Fri, 15 Apr 2016 10:52:03 +0000 (UTC) Received: (qmail 38616 invoked by uid 500); 15 Apr 2016 10:52:03 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 38565 invoked by uid 500); 15 Apr 2016 10:52:03 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 38553 invoked by uid 99); 15 Apr 2016 10:52:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Apr 2016 10:52:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 19FADC023E for ; Fri, 15 Apr 2016 10:52:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.173 X-Spam-Level: ** X-Spam-Status: No, score=2.173 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id xKsKLDqaBTnO for ; Fri, 15 Apr 2016 10:52:01 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTP id C1A495F1E9 for ; Fri, 15 Apr 2016 10:52:00 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id 2BBB42549750 for ; Fri, 15 Apr 2016 03:39:02 -0700 (PDT) Date: Fri, 15 Apr 2016 03:38:07 -0700 (PDT) From: tomk To: user@ignite.apache.org Message-ID: <1460716687416-4219.post@n6.nabble.com> In-Reply-To: <1460714375297-4214.post@n6.nabble.com> References: <1460714375297-4214.post@n6.nabble.com> Subject: Re: It it possible to eleminate CacheConfiguration from code java ? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Ok, I will show this webconsole. When it comes to flow in my code - could you refert to this issue ? As you know- for example I don't know where should I create instance of Ignite class. PS xmls files allow me totally eleminate configuration cache from java code ? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/It-it-possible-to-eleminate-CacheConfiguration-from-code-java-tp4214p4219.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.