Hi,
using the following auto-generated classes (Class1, Class2) causes an
AmbiguousMethodCallException in a unit test, although the mentioned methods are
not ambiguous. Class1 looks like this:
@javax.annotation.Generated…
public class Class1 {
@JsonProperty("data")
priv
iew this message in context:
http://camel.465427.n5.nabble.com/AmbiguousMethodCallException-on-evaluating-simple-expression-tp5779082.html
Sent from the Camel - Users mailing list archive at Nabble.com.
;exactly" matches the content of the Exchange's
body and invocation occurs without an error.
Just takes a good night of sleep.
-AP_
--
View this message in context:
http://camel.465427.n5.nabble.com/AmbiguousMethodCallException-but-both-methods-are-the-same-tp5766545p5766552.html
S
s perfectly fine
when syncHandle is executed, but breaks with this exception when asyncHandle
is executed.
Thanks.
-AP_
--
View this message in context:
http://camel.465427.n5.nabble.com/AmbiguousMethodCallException-but-both-methods-are-the-same-tp5766545.html
Sent from the Camel - Users mailing list archive at Nabble.com.
lic
> java.lang.Object CollectionTransformer.transform(java.util.Collection)].
> Exchange[Message: java.lang.String@21faa3c5]
>
> How can I get this to choose the subclass method?
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/AmbiguousMethodCallException-on-override-methods-tp5720931.html
> Sent from the Camel - Users mailing list archive at Nabble.com
> (http://Nabble.com).
hange[Message: java.lang.String@21faa3c5]
How can I get this to choose the subclass method?
--
View this message in context:
http://camel.465427.n5.nabble.com/AmbiguousMethodCallException-on-override-methods-tp5720931.html
Sent from the Camel - Users mailing list archive at Nabble.com.
gt; https://issues.apache.org/activemq/browse/CAMEL-
>>>
>>> Feel free to create a small sample application that demonstrates this
>>> issue. That can be used to help fix it and as an unit test for the
>>> future.
>>>
>>>
>> --
>> View
test for the
>> future.
>>
>>
> --
> View this message in context:
> http://old.nabble.com/AmbiguousMethodCallException-on-transactional-spring-bean-tp26496269p26496798.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
--
Claus Ibsen
Ap
nstrates this
> issue. That can be used to help fix it and as an unit test for the
> future.
>
>
--
View this message in context:
http://old.nabble.com/AmbiguousMethodCallException-on-transactional-spring-bean-tp26496269p26496798.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I have configured a spring bean as a consumer of a message queue. It contains
> one method, annotated @Transactional.
>
> Camel throws an AmbiguousMethodCallException. "Ambiguous method invocations
> possible [..] public final void
> com..TransactionService$$EnhancerByCGLIB$$273a5
On Tue, Nov 24, 2009 at 2:54 PM, Kees de Kooter wrote:
>
> I have configured a spring bean as a consumer of a message queue. It contains
> one method, annotated @Transactional.
>
> Camel throws an AmbiguousMethodCallException. "Ambiguous method invocations
> possible [..]
I have configured a spring bean as a consumer of a message queue. It contains
one method, annotated @Transactional.
Camel throws an AmbiguousMethodCallException. "Ambiguous method invocations
possible [..] public final void
com..TransactionService$$EnhancerByCGLIB$$273a5668.setPrefil
> >>
>> >>
>> from("activemq:queue:purchaseorder:externalId").beanRef("purchaseOrderService",
>> >> "getByExternalId(String)");
>> >> }
>> >>
>> >>
>> >>
>>
anRef("purchaseOrderService",
> >> "getByExternalId(String)");
> >> }
> >>
> >>
> >>
> >> and I call it using:
> >>
> >> PurchaseOrder po = (PurchaseOrder)
> >> camelTemplate.sendBody(&qu
>> "getByExternalId(String)");
>> }
>>
>>
>>
>> and I call it using:
>>
>> PurchaseOrder po = (PurchaseOrder)
>> camelTemplate.sendBody("activemq:queue:purchaseorder:transid",
>> ExchangePattern.InOut, p
String)");
> }
>
>
>
> and I call it using:
>
> PurchaseOrder po = (PurchaseOrder)
> camelTemplate.sendBody("activemq:queue:purchaseorder:transid",
> ExchangePattern.InOut, poid);
> Sys
System.out.println("POID: " + po.getTranId());
The server throws and AmbiguousMethodCallException. I thought the
activemq:queue:purchaseorder:transid route would differentiate the method
call from activemq:queue:purchaseorder:externalId. Am I going about this the
wrong way?
-
Buzzterrier
http:/
17 matches
Mail list logo