Mule
  1. Mule
  2. MULE-5614

"vm://path?method=foo" syntax not work in Mule 3.1.2

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major 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:
      Hide

      <spring:bean id="methodTestComponent" class="MethodTestComponent" />

      <flow name="methodTestFlow">
      <vm:inbound-endpoint path="methodTest" exchange-pattern="request-response" />

      <component>
      <spring-object bean="methodTestComponent" />
      </component>
      </flow>

      Show
      <spring:bean id="methodTestComponent" class="MethodTestComponent" /> <flow name="methodTestFlow"> <vm:inbound-endpoint path="methodTest" exchange-pattern="request-response" /> <component> <spring-object bean="methodTestComponent" /> </component> </flow>
    • Similar Issues:
      MULE-2429Mule 1.4.X depends on Woodstox 3.2.1 this is not a stable release, 3.1.2 is.
      MULE-6892Forcing soapversion 1.2 on MULE 3.1.2
      MULE-6461Multiple flow startup very slow after upgrading from 3.1.2 to 3.3.0
      MULE-1027Simplify the "mule -config my-config.xml" syntax
      MULE-6479-O override property syntax creates invalid system properties
      MULE-6270mulesoft.org documentation links (HTML) does not work.
      MULE-1236Unable to start Mule server
      MULE-7356New Database: Improve metadata generation for ".?" syntax
      MULE-7355New Database: Improve metadata generation for ".?" syntax
      MULE-3076FunctionalTestCase does not work without mule-test-exclusions.txt

      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"; }

      }

        Activity

        Hide
        Pablo Kraan added a comment -

        Mike, did you have any update on this issue?

        Show
        Pablo Kraan added a comment - Mike, did you have any update on this issue?
        Hide
        Mike Schilling added a comment -

        I was unable to fix it at the time with any reasonable amount of effort.

        Show
        Mike Schilling added a comment - I was unable to fix it at the time with any reasonable amount of effort.

          People

          • Assignee:
            Unassigned
            Reporter:
            Steve Markoff
          • Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:

              Development