Return-Path: X-Original-To: apmail-incubator-deltaspike-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-deltaspike-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 73FF395EE for ; Tue, 12 Jun 2012 07:50:46 +0000 (UTC) Received: (qmail 55194 invoked by uid 500); 12 Jun 2012 07:50:46 -0000 Delivered-To: apmail-incubator-deltaspike-dev-archive@incubator.apache.org Received: (qmail 54303 invoked by uid 500); 12 Jun 2012 07:50:44 -0000 Mailing-List: contact deltaspike-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: deltaspike-dev@incubator.apache.org Delivered-To: mailing list deltaspike-dev@incubator.apache.org Received: (qmail 54217 invoked by uid 99); 12 Jun 2012 07:50:44 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Jun 2012 07:50:44 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id EB86B1402B5 for ; Tue, 12 Jun 2012 07:50:43 +0000 (UTC) Date: Tue, 12 Jun 2012 07:50:43 +0000 (UTC) From: "Gerhard Petracek (JIRA)" To: deltaspike-dev@incubator.apache.org Message-ID: <401050002.6340.1339487443967.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1024037226.4051.1339445862594.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (DELTASPIKE-191) get rid of BeanManagerProvider#setTestMode() 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/DELTASPIKE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293420#comment-13293420 ] Gerhard Petracek commented on DELTASPIKE-191: --------------------------------------------- +1 to get rid of the workaround! however, the current draft will cause strange side-effects (in many cases not deterministic due to the unspecified order of observers), if users use #getBeanManager in a custom AfterDeploymentValidation observer. in case of weld it will finally store and return the bean-manager used for the latest bda (which isn't the bm exposed via jndi). > get rid of BeanManagerProvider#setTestMode() > -------------------------------------------- > > Key: DELTASPIKE-191 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-191 > Project: DeltaSpike > Issue Type: Bug > Components: Core > Affects Versions: 0.2-incubating > Reporter: Mark Struberg > Assignee: Mark Struberg > Fix For: 0.3-incubating > > > this is an absolute antipattern and we must remove it asap! > We also need to review all the RootBeanManagerProvider pattern. This seems like huge tons of code just to provide a workaround for a broken container. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira