Continue to discover and try new things. I've also determined that my unit
test works when the "proxy" and "export" beans are in different Spring
applicationContext(s).
So, still not sure why my real-world test fails (when the "proxy" and
"export" beans are in different web applications).
--
V
I am using Camel 2.12.1 for all components.
The test case (which works) is getting to line 128 of BeanProcessor, but I
don't understand the "if (sameBean)" logic/comments there. I would assume
it also returning from line 133.
My real-world WAR file deployment (which fails / calls wrong method)
And, in case the question pops up, my test case has the "proxy" and the
"export[er]" in *different* camel contexts (which is about as equivalent as
I can make it to how it is running inside tc Server).
Steve Ardis
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-proxy-C
I decided to try the "vm" transport, and as expected I received a
"HibernateException: Unable to locate current JTA transaction", but Iin the
stacktrace I can see that it invoked the wrong method as well (same method
as "direct-vm" transport). I also started a new transaction, and as
expected, it
A little more discovery here...
With my unit tests, it appears to be invoking the correct method(s).
However, when deployed into tc Server across separate web applications
(WARs), it is still invoking the wrong method.
Just as an FYI, I am using the "direct-vm" transport because it is across
d
When using Camel's Spring Remoting capability, it seems that the
"CamelBeanMethodName" should/could be automatically set, including with
support for overloaded methods by adding the parameter types.
I have an interface with several methods on it and am using the "direct-VM"
transport. The interfa
