Hi Daniel,
Many thanks for your insights !
Regarding the in-efficiency of approach taken, i completely agree. However, i
dont see any other solution, i will tell you my complete problem that i am
trying to solve.
May be you could advise for a better solution.
Problem :
Post CXF upgrade to 3.2
Thank you Andy!
Regards!
On Tue, Mar 5, 2019, 1:47 PM Andy McCright
wrote:
> Hi Pablo,
>
> If you use the MicroProfile Rest Client 1.2 APIs and CXF 3.3, there are
> some new features that will make this scenario a little simpler.
>
> First, you can now get the java.lang.reflect.Method of the cl
Thank you James!
Best regards!
On Tue, Mar 5, 2019, 8:59 AM James Carman
wrote:
> Those may not work on the client side. If that’s the case, I’d scrap using
> client proxies and I’d just use the JAX-RS client api directly, unless
> you’re using this as a tinkering opportunity.
>
> On Tue, Mar
Well, my first thought is that for what you are trying to do, you are doing it
in a very in-efficient manner. :)
For the most part, you would be better off adding an interceptor to the
beginning of the PRE_PROTOCOL phase. At that point, you could do:
((SoapMessage)message).getHeaders()
To
Hi Pablo,
If you use the MicroProfile Rest Client 1.2 APIs and CXF 3.3, there are
some new features that will make this scenario a little simpler.
First, you can now get the java.lang.reflect.Method of the client interface
being invoked using a ClientRequestFilter - there is an example from the
T
Hi guys,
Can anyone advise on the below queries, please ?
I really want to understand if my understanding is flawed ☹
Many thanks !
Warm Regards,
Varun SINGHAL
From: Varun Singhal
Sent: Tuesday, March 5, 2019 12:09:24 AM
To: users@cxf.apache.org
Subject: [Readi
Hi all,
I have a wsdl that contains one service with many one-way operations. I'm
using CXF v3.3.0 to handle the heavy duty and wsdl2java to generate the
JAX-WS server side code. I publish my endpoint at the *"/ip"* path.
The situation:
1. SOAP message is signed with a custom certificate and en
Those may not work on the client side. If that’s the case, I’d scrap using
client proxies and I’d just use the JAX-RS client api directly, unless
you’re using this as a tinkering opportunity.
On Tue, Mar 5, 2019 at 6:46 AM James Carman
wrote:
> Did you try using @HeaderParam and @DefaultValue?
Did you try using @HeaderParam and @DefaultValue?
On Tue, Mar 5, 2019 at 1:40 AM Pablo Caballero wrote:
> Hi folks!
>
> I'm writing a REST client to interact with a service exposed by my home
> router (*1).
>
> The service consist of a set of operations exposed in a unique URI (
> https://xxx.xxx
