Yes correct.
I have two servlets - one for jax-ws, one for jax-rs, the latter with two
jaxrsServerFactories.
Den tir. 30. okt. 2018 kl. 22:41 skrev Scott Lewis :
> On 10/30/2018 12:53 PM, David Karlsen wrote:
> > I register several jaxrsServerFactoryBean beans with the same but - under
> >
On 10/30/2018 12:53 PM, David Karlsen wrote:
I register several jaxrsServerFactoryBean beans with the same but - under
different addresses - which works fine
So that I understand: you register multiple beans with the same
instance of CXFNonSpringServlet...with different aliases (e.g. '/foo'
I register several jaxrsServerFactoryBean beans with the same but - under
different addresses - which works fine
Den tir. 30. okt. 2018 kl. 16:56 skrev Scott Lewis :
>
> Separate bus instances are created for the CXFNonSpringServlets init,
> but what apparently blows up is the create/use/start
Separate bus instances are created for the CXFNonSpringServlets init,
but what apparently blows up is the create/use/start of more than one
org.apache.cxf.endpoint.ServerImpl instance at: at
org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:123).
Any insights on how to avoid/work
Hello!
Request header:
xmlns="http://www.w3.org/2005/08/addressing;>urn:hl7-org:v3:PRPA_IN201305UV02
xmlns="http://www.w3.org/2005/08/addressing;>urn:uuid:acdd5cd4-1b7d-4027-b8a5-5b269c488d56
What do the request and response messages look like?
Colm.
On Tue, Oct 30, 2018 at 1:11 PM Tóth Csaba
wrote:
> Hello!
>
> I tried to write a we client. I need to send addressing info (its
> already working), but it cant parse the response:
> the error:
> WARN
Hello!
I tried to write a we client. I need to send addressing info (its
already working), but it cant parse the response:
the error:
WARN org.apache.cxf.ws.addressing.soap.MAPCodec - Failed to
correlate message, aborting dispatch.
And the proxy response object is become null.
At the
