Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 3.1.2
-
Fix Version/s: None
-
Component/s: Transport: VM
-
Labels:None
-
Environment:
Windows 7, JDK 1.6.0_26
-
User impact:Medium
-
Effort points:1
-
Configuration:
-
Similar Issues:None
Description
I realize there are other ways of setting the method property than using the syntax "vm://path?method=foo"
but we find this extremely convenient, and after upgrading to Mule 3.1.2 (from Mule 2.1.2) this does not work!
Here is the Java code (Component class + unit test class) for my test case (and see config section also for config):
public class MethodTestComponent {
public String method1(String s) { return "method1 called"; }
public String method2(String s) {
return "method2 called";
}
}
public class MethodTestCase extends FunctionalTestCase {
@Test
public void test() throws Exception {
LocalMuleClient client = muleContext.getClient();
MuleMessage reply = client.send("vm://methodTest?method=method2", "dummy msg", null);
String result = (String) reply.getPayload();
String msg = "result ";
assertTrue(msg, result.equals("method2 called"));
}
@Override
protected String getConfigResources() {
return "src/main/app/mule-config.xml";
}
}