Re: JAXRS client proxy and HTTP Conduits

[Sergey Beryozkin]

Hi

On 18/06/14 14:56, gquintana wrote:
Thanks for your answer Sergey,

Sergey Beryozkin wrote
It is difficult to figure out what is going wrong.

I agree, how can I debug how Conduits and Clients get associated together?

I think you can put a breakpoint in

org.apache.cxf.transport.http.HttpTransportFactory.getConduit

Is it possible to explicitly bind a Conduit to a Client and not repeat the
URL? Something like:

AFAIK the more open the pattern is the more chances a given conduit has 
to match a given URI


Sergey Beryozkin wrote
It is strange that in
your original post one HTTPConduit configuration works and the other
does not, what is the actual difference between the two conduit names,
after the substitution is done ?

The value is the same (other.url=http://otherserver.com/otherapp/). The only
difference is how the property is replaces, manually in code editor in the
first example, dynamically by Spring property placeholder in the second. I
may have a problem with property placeholder, but it 's behaving properly
everywhere else.


Sergey Beryozkin wrote
By the way, in the latest example a combination of double "{" and "}" is
used.

I am trying to render



Sergey Beryozkin wrote
The other thing to try is to have the second name (in the original
example) introduce a wildcard, may be you have a longer URI wich does
not match the name pattern.

Is this matching rule correct?
For JAXRS
<jaxrs:client   address=&quot;_THE_URL_*&quot; ...
&lt;http-conf:conduit name=&quot;_THE_URL_&quot; ...

For JAXWS
&lt;jaxws:client    address=&quot;_THE_URL_&quot;
serviceClass=&quot;_THE_PORT_CLASS_&quot; ...
&lt;http-conf:conduit name=&quot;{_THE_URL_}_THE_PORT_.http-conduit&quot;>
or
<jaxws:client    address="_THE_URL_" serviceClass="_THE_PORT_CLASS_" ...
<http-conf:conduit name="{_THE_URL_}*.http-conduit">
or
<jaxws:client   address="_THE_URL_" serviceClass="_THE_PORT_CLASS_" ...
<http-conf:conduit name="_THE_URL_">

This won;t likely work well for JAX-RS - it does not have to be the 
exact match, the conduit name should have something like 
"http://myhost/*";, etc

Cheers, Sergey


Gérald




--
View this message in context: 
http://cxf.547215.n5.nabble.com/JAXRS-client-proxy-and-HTTP-Conduits-tp5745021p5745318.html
Sent from the cxf-user mailing list archive at Nabble.com.