Mailing-List: contact felix-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: felix-dev@incubator.apache.org
Received-SPF: pass (hermes.apache.org: domain of chris.custine@gmail.com
 designates 66.249.82.225 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=aJsZM4ivv1j5l37Nz0xxFLBkxBMzkjMEP1upJgXEaJnMxqtdVylDvJbZTqHl3gfFJ3R1vQBOJPUijf3/2qCSmxfH3JBmWeo6GVTukFBBmWw5iXlPyY6lVsqwcifqRgTQVXjgXCaXGutKK1OdN8b5Nyf3+IhIsn7dx9vRuzVHh3A=
Message-ID: <43b026c70610080930p76119100pd375ffeec3cb976c@mail.gmail.com>
Date: Sun, 8 Oct 2006 12:30:11 -0400
From: "Chris Custine" <chris.custine@gmail.com>
To: felix-dev@incubator.apache.org, simon.willnauer@gmail.com
Subject: Re: Work with Felix but how?!
In-Reply-To: <f18c9dde0610070609s33e784cbw63cabc3227211134@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_169969_11643943.1160325011060"
References: <f18c9dde0610060044r164fb2cep23e0c621bce79606@mail.gmail.com>
	 <9D8522AD-9992-433D-AECF-819E3B0C43D5@luminis.nl>
	 <f18c9dde0610070609s33e784cbw63cabc3227211134@mail.gmail.com>

------=_Part_169969_11643943.1160325011060
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

This is an interesting question that I have been pondering as well.  At
first it seemed like re-packaging my app into bundles and utilizing the OSGi
/ Felix framework was the way to go, but as I started down that path I
realized that I was going to spend a lot of time "bundling" my own
components that would never be used outside of my core application.
Instead, what I really want is to utilize the OSGi framework for managing
"plugins" (ie Bundles) within my application so that we can package
functionality seperately and allow users to extend it as well.

I also started thinking about managing the bundles within my app so I
started writing an Ajax based admin page similar to the ones in the Oscar
repository.  I originally thought I would write it as a Bundle, but all of
our apps are using Spring and Spring MVC and I couldn't figure out how to
include all of that in a standalone Bundle using the http or servlet
bundles.  Like you said, there doesn't appear to be any way to deploy a full
blown web app with SCL's and request listeners (web.xml) using the built in
HTTP and servlet bundles.

Sorry to respond without an answer, but I wanted to register my interest in
these questions as well.  I am going to use Felix for bundle management in
at least a couple of applications (one web, one middleware/messaging) and I
am starting from scratch, so I think these initial decisions / questions are
going to be common for any new developer.  I am considering documenting the
thought process and outcome of these choices from a new user standpoint if
the Felix team is interested in adding something like that to the docs.

Chris

On 10/7/06, Simon Willnauer <simon.willnauer@googlemail.com> wrote:
>
> > Also, feel free to ask more questions on this list.
> >
> > There we go.. I guess I got the idea of OSGi / Felix and build a nice
> simple example adding bundles and using them. The application I wanna
> refactor to make extensive use of felix basically runs in a
> servletcontainer
> and is shipped as a warfile. It seems a bit weak to me to use the osgi
> HttpService as a lot of configurations for the container are not visible
> as
> far as I can see. So anyway I'm interested in a "best practice" way to
> integrate felix. Is it as simple as I think it would be just starting up a
> new Felix instance (Felix f = new Felix() ... bla bla) within a context
> listener and register several servlets in the web.xml which make use of
> services provided by felix?
>
> Am I on the wrong way with this approach?
>
> best regards simon
>
>

------=_Part_169969_11643943.1160325011060--