Hi Tatu,
Thanks. Plus thanks Sahoo for reminding me of this too.
I think we need to review what we can do for utilizing Jersey outside
of the GF OSGi enabled container. Richard, would you be interested in
helping out?
Paul.
On Dec 2, 2008, at 7:45 PM, Tatu Saloranta wrote:
> --- On Tue, 12/2/08, Paul Sandoz <Paul.Sandoz_at_Sun.COM> wrote:
>
> ...
>> OK. I will ping the list when we have the modules correctly
>> OSGI aligned and we can start experimenting. I suspect that
>> we may into issues with META-INF/services.
>
> Paul, for what it's worth, META-INF/services approach has indeed
> been considered problematic with other JAX* APIs.
> I am most familiar with Stax.
>
> There has been discussion on best ways to deal with the problem,
> inspired by this blog entry:
>
> http://gnodet.blogspot.com/2008/05/jee-specs-in-osgi.html
>
> On positive note, given that it is a general problem, there may be a
> general solution to it as well. Solution suggested above is not the
> only possibility, but other approaches suffer a bit from impedance
> between the way OSGi services are to work, and how services-
> introspection is designed to work (at least for Stax, where factory
> instance provided is not a singleton).
>
> -+ Tatu +-
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>