Monday, August 15, 2011

questions for Mule course

1. how pooling and singletons work together:
 <flow name="Test1">
  <vm:inbound-endpoint path="VMQ413" exchange-pattern="one-way"/>
  <component>
   <method-entry-point-resolver>
    <include-entry-point method="next"/>
   </method-entry-point-resolver>
   <spring-object bean="QM413"/>
  </component>
  <component>
   <method-entry-point-resolver>
    <include-entry-point method="update"/>
   </method-entry-point-resolver>
   <spring-object bean="QM413"/>
  </component>
        
    // will the previous 2 components be a synchronized entry point to this flow?  <filter ref="notNull"/>
  <pooled-component>
   <spring-object bean="QR413"/>
   <pooling-profile maxActive="10" maxIdle="5" maxWait="3" initialisationPolicy="INITIALISE_ALL"/>
  </pooled-component>
  <async>
// what does this do, for a vm queue insert?   <vm:outbound-endpoint path="VMQ413" exchange-pattern="one-way"/>
  </async>
 </flow>

2. deployment: we are worried about having lots of Java code in our bus. Are we going to hurt our performance as a web service proxy, by having all these applications inside the Mule JVM?


3. Exception handling. What kind of info gets into the exception message? Is there a way to indicate what we were doing at the time (eg. the message that was being processed?)


4. How to tell if we're using the EE or CE Mule?


Is it the same in Maven:



<dependency>
  <groupId>org.mule</groupId>
  <artifactId>mule</artifactId>
  <version>3.1.2</version>
  <type>pom</type>
</dependency>