On Wed, Jun 2, 2021 at 10:57 PM marcello cappelli <kcell...@gmail.com> wrote:
>
> Thank you so much for your support.
> Unfortunately the result is the same.
>
> I don't understand where the answer gets lost.
> By enabling the trace, I see that the method is executed and returns the 
> result but Camel does not return it. I don't understand where I'm wrong
>

Can you tell us where in the source code you see the method executed
and the result coming back?
And maybe can you look at the unit tests and see if you can add a new
test for your use-case (or something close enough to trigger that
method)
so we can use that to track down and fix the bug.

> On 2021/06/02 04:21:39, Claus Ibsen <claus.ib...@gmail.com> wrote:
> > Try without the result type class parameter, and just get the object
> > as output and see what it looks like
> >
> > On Tue, Jun 1, 2021 at 10:20 PM marcello cappelli <kcell...@gmail.com> 
> > wrote:
> > >
> > > Hi,
> > > I get the same behavior even so:
> > >
> > > String  endpointUri     = 
> > > "milo-client:opc.tcp://milo.digitalpetri.com:62541/milo?node=RAW(ns=2;s=Methods)&method=RAW(ns=2;s=Methods/sqrt(x))&defaultAwaitWrites=true&overrideHost=true";
> > >
> > > Variant[] inputArguments  = new Variant[1];
> > > inputArguments[0] = new Variant((double) 25);
> > >
> > > Variant[] outputArguments = isoProducerTemplate.requestBody(endpointUri, 
> > > inputArguments, Variant[].class);
> > >
> > > The response should be a 1 element variant array with the result
> > >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Reply via email to