Mailing-List: contact users-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@felix.apache.org
Received-SPF: pass (athena.apache.org: domain of ildella@gmail.com designates
 209.85.214.49 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:from:date
         :x-google-sender-auth:message-id:subject:to:content-type;
        b=NUAJ1WE7ZcA5iRhZOl32mVmr1mGtHb+HFudVKTgIztgVESH/i+YNoPh0VjZbsY74BY
         n/ADgSO5tgJSRdReSCZGC4YKpDLxEegvEbko+ABmEzq2Jb+hB7Du4UtbIm6HREU1Hu6q
         hRX/9PKRzP3fi301G/luf0GjwyipE12SnQLRU=
MIME-Version: 1.0
Sender: ildella@gmail.com
In-Reply-To: 
 <1784276911.142369.1305044609551.JavaMail.root@sz0116a.westchester.pa.mail.comcast.net>
References: <BANLkTikA=in_peV9OOZZrkUf7NKH6dZXeQ@mail.gmail.com>
 <1784276911.142369.1305044609551.JavaMail.root@sz0116a.westchester.pa.mail.comcast.net>
From: Daniele Dellafiore <daniele@dellafiore.net>
Date: Tue, 10 May 2011 19:30:31 +0200
Message-ID: <BANLkTimz0tA-dXOxgedxJsO9jmtKedRSvw@mail.gmail.com>
Subject: Re: A better life: quick webapp deploy
To: users@felix.apache.org
Content-Type: multipart/alternative; boundary=0016e6db5be848015704a2ef515c

--0016e6db5be848015704a2ef515c
Content-Type: text/plain; charset=ISO-8859-1

On Tue, May 10, 2011 at 6:23 PM, <mvangeertruy@comcast.net> wrote:

>
>
> Danielle,
>
>
>
> We had similar issues with spring xml files, and you're correct, you cannot
> access spring.xml files between bundles. To be clear though, are you
> referring to the xml files in META-INF/spring or are you referring to the
> .xsd files spring uses in its namespaces?
>

to the xml files in META-INF/spring

also, the xml I'd like to load, i'd rather not put them in that folder cause
xml in that folder is automatically loaded by spring-dm.
What I'm thinking about are some xml used as resources, not started by
spring-dm in any way, that can be included in the spring context of another
bundle just as like I can instantiate a class from an imported bundle.

Included not with some custom code (not only at least) but with some
mechanism like import classpath*: that loads from dependent jars.

--0016e6db5be848015704a2ef515c--