Yes, this is nice. Thanks to all who took the time to post.
-S
From: osgi-dev-boun...@mail.osgi.org [mailto:osgi-dev-boun...@mail.osgi.org] On
Behalf Of Dennis Geurts
Sent: Thursday, January 08, 2009 4:43 PM
To: OSGi Developer Mail List
Subject: Re: [osgi-dev] Servlet design pattern
I
I usually do it like this:
1) make Activator extend the DependencyActivatorBase (from the Dependency
manager (from apache felix))
you'll be required to implement (a.o.) an init() method; The following would be
a good start:
public void init(BundleContext context, DependencyManager ma
CTO of the OSGi Alliance
hargr...@us.ibm.com
office: +1 386 848 1781
mobile: +1 386 848 3788
From:
"Pruitt, Byron S"
To:
OSGi Developer Mail List
Date:
2009/01/08 15:13
Subject:
RE: [osgi-dev] Servlet design pattern
Sent by:
osgi-dev-boun...@mail.osgi.org
I use the OSGi Ht
tend to prefer the first approach but admit I have times used the static
stash approach on occassion.
-Simon
- Original Message -
From: "Pruitt, Byron S"
To: "OSGi Developer Mail List"
Sent: Thursday, January 08, 2009 2:55 PM
Subject: RE: [osgi-dev] Servlet design
.
-S
-Original Message-
From: osgi-dev-boun...@mail.osgi.org [mailto:osgi-dev-boun...@mail.osgi.org] On
Behalf Of Niclas Hedhman
Sent: Wednesday, January 07, 2009 9:02 PM
To: OSGi Developer Mail List
Subject: Re: [osgi-dev] Servlet design pattern
On Thu, Jan 8, 2009 at 2:45 AM, Pruitt, Byron S
On Thu, Jan 8, 2009 at 2:45 AM, Pruitt, Byron S wrote:
> I'm developing an application with several bundles. Some of them use the
> http service as the api for the outside world.
> I haven't found a good pattern for integrating Servlets with the rest of the
> OSGi framework. After a request is
