On Aug 12, 2008, at 9:18 AM, Tobias Hofer wrote:
>
> I'm involved in realizing a JAX-RS implementation for the OSGi Service
> Platform. But there are some barriers in the current JAX-RS
> Specification that hinders a seamless integration.
>
> One of them is the lack of a root resource service interface. I
> suggest
> to introduce an empty interface named 'javax.ws.rs.RootResource' or
> alike. This interface would allow an OSGi bundle to expose its
> resources
> using the OSGi service registry using interface that is part of the
> official API.
>
> A global class path scanning in OSGi is possible, but accessing
> instances of classes in bundles that do not explicitly expose them
> as a
> service would break the managed life cycle of bundle components.
>
I'm a complete OSGi novice but it seems like a big step backwards to
require root resource classes to implement an empty marker interface.
How are other annotation driven technologies (e.g. JAX-WS) supported
in OSGi ?
Marc.
> A second one is not really a barrier but a security issue concerning
> the
> static 'RuntimeDelegate.setInstance(RuntimeDelegate)' method. I
> recommend checking for an appropriate permission. This would allow to
> limit the invocation of that method to approved code only.
>
> Thanks in advance for considering this issues.
>
> Tobias Hofer
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jsr311.dev.java.net
> For additional commands, e-mail: dev-help_at_jsr311.dev.java.net
>
---
Marc Hadley <marc.hadley at sun.com>
CTO Office, Sun Microsystems.