Hi James,
On 3/20/2018 5:15 PM, James Carman wrote:
Mainly you just need to make sure it uses the same Bus, I believe.
Any pointers on how to do that with CXFNonSpringJaxrsServlet or other
servlet class?
What
OSGi container? Why are you registering the server yourself?
Because I'm not
Mainly you just need to make sure it uses the same Bus, I believe. What
OSGi container? Why are you registering the server yourself? CXF has good
support for OSGi already.
On Tue, Mar 20, 2018 at 2:37 PM Scott Lewis wrote:
> Thanks James,
>
> I'm using the OSGi
Hi Carlos,
Thanks for the pointers. This is great.
What is the timeframe for release of Aries impl of jax-rs-whiteboard?
Thanks,
Scott
On 3/20/2018 11:33 AM, Carlos Sierra Andrés wrote:
You could also entertain https://github.com/apache/aries-jax-rs-whiteboard
it is an implementation of a
Thanks James,
I'm using the OSGi HttpService and registering a
CXFNonSpringJaxrsServlet instance at runtime. I don't quite understand
how to use the JaxrsServerBeanFactory with the HttpService/servlet. By
chance do you have an example of that in Microbule? Is there
another/better CXF
You could also entertain https://github.com/apache/aries-jax-rs-whiteboard
it is an implementation of a whiteboard for JAX-RS applications. It is
specified how to register applications and extensions just like the ones
you need. It is based upon CXF but you only need to use JAX-RS and OSGi
API.
You can use JaxrsServerBeanFactory in OSGi just fine. With that, you can
add all the providers you want. You can check out Microbule for inspiration:
https://github.com/Microbule/microbule
On Tue, Mar 20, 2018 at 1:34 PM Scott Lewis wrote:
> I'm programmatically using cxf
I'm programmatically using cxf in an osgi environment. I'm using the
servlet class: org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet,
and want to create and an impl of javax.ws.rs.core.Configurable to
register extensions (e.g. json support, etc).
Is there a cxf jaxrs impl of
I think it will read the global CA configuration anyway first, but then use
the conduit keystore configuration. If you enable SSL debug logging can you
see the certs stored in your truststore being loaded? Do you still see the
same error?
Colm.
On Tue, Mar 20, 2018 at 1:42 PM, Tóth Csaba
Hello!
the
https://localhost:.*;>
not worked (same error), so I try to dig deeper, and find out, the
keystore definition was wrong. I fix it, and its read the
"*.http-conduit"
too, but when I try to test, its read the global keystore again and not
what I defined in the conduit:
...
What if you use something like this instead?
https://localhost:.*;>
If that doesn't work (with the correct domain name) then it looks like the
config is not getting picked up properly.
Colm.
On Mon, Mar 19, 2018 at 4:56 PM, Tóth Csaba wrote:
> Hello!
>
> I'd like call
For:
> PortType port = service.getPort(portQName, PortType.class);
you need to specify your service endpoint interface here instead of
javax.wsdl.PortType. You could take a look at one of the following CXF
examples to see how it's done:
11 matches
Mail list logo