You kept me very busy reading all the citations, but I do now agree that the
OSGi edition approach would have a multiplicative effect on the number of
editions ... I think your action plan is a good one.
On Sat, Aug 22, 2009 at 10:26 AM, Jerome Louvel
wrote:
> The action plan I propose is:
> 1) L
De : webp...@tigris.org [mailto:webp...@tigris.org]
Envoyé : mercredi 12 août 2009 17:06
À : discuss@restlet.tigris.org
Objet : RE: Re: OSGi vs. Service Provider patterns
Felix' support for fragments should be good in 1.8.x and is actually passing
the TCK in the trunk build...I won't cl
Felix' support for fragments should be good in 1.8.x and is actually passing
the TCK in the trunk build...I won't claim it is without bugs, though. :-)
I am not convinced the fragments are the best way to do this, but I agree that
it is a workable approach.
Using META-INF/services is not great
oelios Technologies ~ Co-founder ~ <http://www.noelios.com/>
http://www.noelios.com
De : Rob Heittman [mailto:rob.heitt...@solertium.com]
Envoyé : lundi 17 août 2009 19:24
À : discuss@restlet.tigris.org
Objet : Re: OSGi vs. Service Provider patterns
The trouble with getting caugh
The trouble with getting caught up on mail is that everybody just piles on,
once they see you're responding ;-)
On Mon, Aug 17, 2009 at 1:18 PM, David Fogel wrote:
> Hi all-
>
> Jerome, any chance you'd like to weigh in with your current plans for
> resolving OSGi deployment strategy for Restle
Hi all-
Jerome, any chance you'd like to weigh in with your current plans for
resolving OSGi deployment strategy for Restlet 2.0?
-Dave Fogel
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2384450
David,
You are right. I've just taken a look at the Activator code. I did not
look at every jar, but only org.restlet.jar seems to have an Activator. It
seems to scan bundles looking for CLIENTS, SERVERS or AUTHENTICATORS
registering them as helpers as appropriate. ( I like the small class
Robin-
To be clear, (and it's important to note that I haven't tried this
approach recently), the current restlet core module does come with a
BundleActivator registered in the manifest, you can see the code at
org.restlet.engine.internal.Activator.java, and it's designed to do
roughly what it see
Hi David, Rob
I have not used bundle fragments personally, but I can see how it is a clever
solution. Presumably, the fragments get hitched to the core bundle and thus
share its loader so that all other bundles see it as one bundle on one loader?
In my own code, I decided to put all the osgi se
The other thing I have been thinking about (wish list item) is how to expose
the Restlet Http Server as a OSGi HttpService.
I mentioned to Rob the possiblity of doing it the other way around, but I
suspect that OSGi HttpService does not expose enough of the stuff that an
HttpConnector might nee
Hi Rob-
That's interesting- I guess I never thought to check if the other OSGi
containers supported fragments. But it's been forever since I've
played with any of them besides equinox- I guess I can look around on
mailing lists or something.
I guess another option for Restlet-OSGi strategy would
Hi,
On Aug 11, 2009, at 10:42 AM, Rob Heittman wrote:
> At one point I was given to understand that Equinox was the only
> OSGi framework that yet understood fragments. I'd be worried about
> going the fragment route if that's still true. But if KF and Felix
> and friends now grok fragmen
At one point I was given to understand that Equinox was the only OSGi
framework that yet understood fragments. I'd be worried about going the
fragment route if that's still true. But if KF and Felix and friends now
grok fragments (or will soon), I think that would be a lovely way to
repackage all
Hi Robin, Rob-
Robin, the problem with expecting the Restlet project to use the OSGi
service registry to support their extension architecture deplopyed in
a OSGi container is that there's no "halfway" when talking about OSGi
services. As you probably know, OSGi really means two things: #1)
classl
The additional dependency on the OSGi API in core (even though it is minor),
and the ripple of this across the Restlet ecosystem, were what made this a
non-starter before. I really think using the new conditional compilation
support (editions) is the way to go.
Dave, if you're still listening, do
Isn't the solution to making things work under OSGi to use the tools that OSGi
provides?
When a new extension bundle comes on line it implements RestletExtension then
registers:
bc.registerService( RestletExtension.class.getName(),null,null);
When something wants to find it, it uses:
(something
27;origine-
De : David Fogel [mailto:carrotsa...@gmail.com]
Envoyé : mercredi 18 mars 2009 08:01
À : discuss@restlet.tigris.org
Objet : RE: OSGi vs. Service Provider patterns
Hi Jerome, Rob-
I've been thinking about Restlet's osgi deployment issues, and experimenting
with a few thin
Hi Jerome, Rob-
I've been thinking about Restlet's osgi deployment issues, and experimenting
with a few things. (Jerome, please let me know if this sort of post is more
appropriate for the restlet.code list than the restlet.discuss one- I'm happy to
post to either...)
If Restlet is commited to u
evant overlapping issue from
that blog comment was related to OSGi+SPI. I'll be interested to see what
solution develops here.
--
View this message in context:
http://n2.nabble.com/OSGi-vs.-Service-Provider-patterns-tp2478338p2488348.html
Sent from the Restlet Discuss mailin
I've been searching for answers to the same questions.
I commented on this blog entry:
http://www.sonatype.com/people/2009/03/the-future-of-maven-osgi-join-the-tycho-users-mailing-list/
--
View this message in context:
http://n2.nabble.com/OSGi-vs.-Service-Provider-patterns-tp2478338p24
: Rob Heittman [mailto:rob.heitt...@solertium.com]
Envoyé : lundi 16 mars 2009 13:37
À : discuss@restlet.tigris.org
Objet : Re: OSGi vs. Service Provider patterns
Thanks for that really thorough response. At this point, mentally I'm
breaking the problem into two categories:
1) Libraries/projects who ar
Thanks for that really thorough response. At this point, mentally I'm
breaking the problem into two categories:
1) Libraries/projects who are receptive to OSGi compatibility and are
interested in supporting OSGi. Restlet is one of these. Here we can work
with/within the project to include better
Hi Rob-
I've been struggling with the same problem.
In fact, I'm guessing that this Service Provider classpath/classloader
hackery (made into a crazy best-practice by its inclusion in JDK 6 as
the java.util.ServiceLoader) is one of the main reasons why OSGi isn't
as widely adopted as it should be
Now that I'm drinking the OSGi Kool-Aid, one of the main problems my
projects face is component reliance on the Java Service Provider model
(META-INF/services/... discovery) to find available bits. My Google-fu is
apparently weak, because I haven't found any good, rational treatment of
what the he
24 matches
Mail list logo
