Never missed that, but might be interesting. Can anybody provide a real-world use case describing the need for this (just to make me understand the benefit)?
> -----Original Message-----
> From: Bill Burke [mailto:bburke_at_redhat.com]
> Sent: Mittwoch, 9. März 2011 22:47
> To: jsr339-experts_at_jax-rs-spec.java.net
> Subject: [jsr339-experts] Re: Fwd: Re: [Resteasy-developers] JAX-RS 2.0
> features you want?
>
>
>
> On 3/9/11 2:35 PM, Roberto Chinnici wrote:
> > We're not voting on anything yet.
> >
> > I'd like to request a clarification re "MetaData API so that
> extensions
> > to RESTEasy can browse through the JAX-RS resources defined".
> >
> > Are we talking about a Java API so that an extension (a piece of Java
> > code that is either part of the same application or deployed as a
> shared
> > library somehow) can discover/enumerate/inspect the resources that
> exist
> > in the application itself? Or are we talking about an HTTP client
> > remotely accessing the application to discover its resources?
> >
>
> I think its to be able to programmatically browse deployed resources.
>
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com