Re: Problem with Camel proxies and hashCode()

Here's an issue with a test case attached: https://issues.apache.org/jira/browse/CAMEL-5571 Best regards, Harald > 2012/9/5 Claus Ibsen : >> >> Yeah methods from java.lang.Object should be omitted to be remotely called. >> >> Do you have a stacktrace? And can you create a small unit test that >>

Re: Problem with Camel proxies and hashCode()

Ok, I'll try to write a self-contained test. Shouldn't be too hard, I see the same exception when calling proxy.hashCode() in my own methods. Best regards, Harald 2012/9/5 Claus Ibsen : > > Yeah methods from java.lang.Object should be omitted to be remotely called. > > Do you have a stacktrace? A

Re: Problem with Camel proxies and hashCode()

On Wed, Sep 5, 2012 at 10:43 AM, Harald Wellmann wrote: > In a Spring Web + JPA application running on Tomcat, I'm using > CamelProxyFactoryBean to create a proxy for a service interface, where > the actual service implementation is a remote JMS endpoint. The > service is @InOnly. > > When shuttin