Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: pass (athena.apache.org: domain of bimargulies@gmail.com
 designates 209.85.132.242 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=URJLi9UN2pyH+hXJekX79uxCO41bueNLjqtqHOGJ7ymE5H80/0Y+ycQ69RE8yyFqj3g13KT8sCFdt+OpiQEGYmds2v5jWv12BxpxnjWHK750LEL1+AvUy9dmCCv528FURG8q1xHAIqeOFs4M8iozTqWzN3TaBFbXpA8PNGztUxw=
Message-ID: <61b5d9410805161458r664d4ab8oc0f6c0714d214fab@mail.gmail.com>
Date: Fri, 16 May 2008 17:58:21 -0400
From: "Benson Margulies" <bimargulies@gmail.com>
To: dev@cxf.apache.org
Subject: Re: On startup performance.....
In-Reply-To: <3E35C239-96C1-4951-92C0-2B7C83501123@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <3E35C239-96C1-4951-92C0-2B7C83501123@apache.org>

I'm not sure that the per-bean overhead of spring is significant
compared to the overall background noise of using Spring at all, or at
least of using Spring with XML. I was thinking about how hard it would
be to go to zero-xml -- have our own factory that didn't read xml, not
even from fastinfoset, for the core configuration.

We could use cascading contexts: we could have a context that
'springs' into life with the core, always-the-same, beans, and then a
normal XML context that cascades to it for the optional items.

I could be wrong here: it could be that moving more initialization
from beans declared in Spring to ordinary objects created by the
default bus would in fact be a win.