Additionally, we cannot provide good javax.ws.rs.Path annotations because
our OSGi service interfaces are used to generate different
services dynamically. for instance, given this interface:
@Path("/")
public interface DynamicService {
@Path("/methodA")
public Object methodA();
}
Different services are registered using the same interface, then
different "org.apache.cxf.rs.address"
properties are generated to differentiate each service like "/serviceA" and
"/serviceB". Both services have same interface, but different instances.
On 2 May 2013 09:24, Julio Carlos Barrera Juez <
[email protected]> wrote:
> Hi!
>
> We have a ServiceMix app with multiple bundles. We want to export our OSGi
> service interfaces using DOSGi. We annotate our service interfaces
> with javax.ws.rs.Path, javax.ws.rs.GET,
> javax.ws.rs.POST, javax.ws.rs.Consumes and javax.ws.rs.Produces. Then we
> register our OSGi services using Apache Aries Blueprint or Java code
> adding different CXF properties.
>
> At the beginning we used "org.apache.cxf.rs.address" property with
> absolute URLs, using Jetty standalone instance. But now we want to use
> relative address to use HTTP service. If we don't
> specify "org.apache.cxf.rs.httpservice.context" property, our service seems
> to be not registered at all. I we specify this property with same value for
> all services there are some errors when registering services ("alias in use
> or another context..."). If we specify different values for each
> registration there are no errors, but there are a mix of methods in each
> service (looking at WADL).
>
> How we must set both properties to achieve having different services
> registered with relative paths?
>
