://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com/
http://www.noelios.com
_
De : Tal Liron [mailto:tal.li...@threecrickets.com]
Envoyé : dimanche 12 avril 2009 17:39
À : discuss@restlet.tigris.org
Objet : Re: ServerResource is currently incompatible with OSGi
Tim
...@gmail.com]
*De la part de* Tim Peierls
*Envoyé :* mercredi 8 avril 2009 00:23
*À :* discuss@restlet.tigris.org
*Objet :* Re: ServerResource is currently incompatible with OSGi
Why involve Context at all? The AnnotationInfo associated with a Class?
extends UniformResource does not depend on Context
Envoy: mercredi 8 avril 2009 00:23
: discuss@restlet.tigris.org
Objet: Re: ServerResource is currently incompatible
with
OSGi
Why involve Context at all? The AnnotationInfo associated with a
Class? extends UniformResource does not depend on Context
...@gmail.com]
*De la part de* Tim Peierls
*Envoyé :* mercredi 8 avril 2009 00:23
*À :* discuss@restlet.tigris.org
*Objet :* Re: ServerResource is currently incompatible with OSGi
Why involve Context at all? The AnnotationInfo associated with a Class?
extends UniformResource does not depend
On Wed, Apr 8, 2009 at 9:42 AM, Jerome Louvel jerome.lou...@noelios.comwrote:
Hi all,
Beautiful! This new solution is available in SVN trunk.
Thanks Dave for the report and Tim for the clever fix!
You're welcome. ;-)
This fix will do for now, but it could be made more robust. Having
tpeie...@gmail.com [mailto:tpeie...@gmail.com]
De la part de
Tim Peierls
Envoy: mercredi 8 avril 2009 00:23
: discuss@restlet.tigris.org
Objet: Re: ServerResource is currently incompatible with
OSGi
Why involve Context at all? The AnnotationInfo associated w
Why involve Context at all? The AnnotationInfo associated with a Class?
extends UniformResource does not depend on Context. You could just add a
method to AnnotationUtils:
public static AnnotationInfo getAnnotationDescriptor(Class?
extends UniformResource resourceClass) {
://www.noelios.com
http://www.noelios.com
_
De : tpeie...@gmail.com [mailto:tpeie...@gmail.com] De la part de Tim
Peierls
Envoyé : mercredi 8 avril 2009 00:23
À : discuss@restlet.tigris.org
Objet : Re: ServerResource is currently incompatible with OSGi
Why involve Context at all? The AnnotationInfo
De:
tpeie...@gmail.com [mailto:tpeie...@gmail.com] De la part de
Tim Peierls
Envoy: mercredi 8 avril 2009 00:23
: discuss@restlet.tigris.org
Objet: Re: ServerResource is currently incompatible with OSGi
Why involve Context at all? The AnnotationInfo associated with a
Class? extends UniformRes
Hi Tal-
I think what you suggested about appending a classloader id (perhaps
System.identityHashCode(cl) ?) would work.
Regarding the Restlet Context and this cache being cruft: You say
the Context is a reasonable place for information that applies to the
Application, but this doesn't have
There's a lot of precedent -- look at all the weird stuff that ends up in
System.properties() on startup of some JVMs, or the values hanging out in
ServletContext or PageContext in every JEE server I know. Doesn't mean it
thrills me.
Thanks for spotting this, David ... would have been a stopper
Ah, I can see your point now.
I would recommend, then, that a Context would have two separate
ConcurrentHashMaps, something like this:
1. Context.getConfiguration() -- this would be for the user
2. Context.getImplementationCache() -- this would be for things like
AnnotationUtils, and the
I've
noticed this, too, but couldn't immediately think of an application
where this would be a problem... thanks for bringing up OSGi.
An
immediate solution could be to append the class's ClassLoader instance
into the key:
org.restlet.resource.ServerResource.annotations.classloader
13 matches
Mail list logo
