After I finish off learning what I need to know about felix I want to tackle
writing a OSGi HTTP Service bundle. But I have a few questions about what
can be included in this bundle if I want to contribute it to Felix:
1) Can it contain out side code? In particular I'm thinking about Grizzly (
htt
nt from my Treo(r) smartphone
-Original Message-
From: "richard jackson" <[EMAIL PROTECTED]>
Date: Thursday, Sep 4, 2008 6:08 am
Subject: OSGi HTTP Service (FELIX-538) Question
To: "dev@felix.apache.org" Reply-To:
"dev@felix.apache.org"
After I finish off lea
richard jackson wrote:
After I finish off learning what I need to know about felix I want to tackle
writing a OSGi HTTP Service bundle. But I have a few questions about what
can be included in this bundle if I want to contribute it to Felix:
1) Can it contain out side code? In particular I'm thi
p.s. One thing I should point out, since you reference FELIX-538, is
that this issue is for a "really lightweight" HTTP Service. So, all of
the stuff you are discussing (i.e., iPOJO, Grizzly, Servlet 2.5, plus
extensions) does not really fit into this definition; however, that
doesn't mean that
richard jackson wrote:
> After I finish off learning what I need to know about felix I want to tackle
> writing a OSGi HTTP Service bundle. But I have a few questions about what
> can be included in this bundle if I want to contribute it to Felix:
>
> 1) Can it contain out side code? In particular
See below
On Thu, Sep 4, 2008 at 8:12 AM, Richard S. Hall <[EMAIL PROTECTED]>wrote:
> richard jackson wrote:
>
>> After I finish off learning what I need to know about felix I want to
>> tackle
>> writing a OSGi HTTP Service bundle. But I have a few questions about what
>> can be included in this
On Thu, Sep 4, 2008 at 8:35 AM, Jean-Cédric Desrochers <
[EMAIL PROTECTED]> wrote:
>
> richard jackson wrote:
> > After I finish off learning what I need to know about felix I want to
> tackle
> > writing a OSGi HTTP Service bundle. But I have a few questions about what
> > can be included in this
I guess I read it more as we don't really need all the extra stuff that a
normal Servlet container has (class loading, war file deployments ect...).
Basicly only support bundles and bundles only. But then again I also want
filters and such as well. But anyways what I'm more thinking about is a
real
richard jackson wrote:
I guess I read it more as we don't really need all the extra stuff that a
normal Servlet container has (class loading, war file deployments ect...).
Basicly only support bundles and bundles only. But then again I also want
filters and such as well. But anyways what I'm more
On Thu, Sep 4, 2008 at 4:35 PM, Richard S. Hall <[EMAIL PROTECTED]> wrote:
> richard jackson wrote:
>>
>> I guess I read it more as we don't really need all the extra stuff that a
>> normal Servlet container has (class loading, war file deployments ect...).
>> Basicly only support bundles and bundl
All I can say is Cool. A Really great idea. Now I just need to check the
code out and play with it :) I use tomcat all the time now but I really want
to replace it with OSGi and that really looks promising. And it looks like
tomcat-light may already be working :) And in reality that would be all we
11 matches
Mail list logo
