Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing a Class mediator with WSO2 ESB
    primarykey
    data
    text
    <p>I'm trying to use a class mediator with the WSO2 ESB.</p> <p>Following is my mediator class.</p> <pre><code>package samples.mediators; import org.apache.synapse.MessageContext; import org.apache.synapse.mediators.AbstractMediator; public class SiriBankMediator extends AbstractMediator { @Override public boolean mediate(MessageContext messageContext) { System.out.println("Hurraaaayyyy!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!"); return false; } } </code></pre> <p>As suggested by <a href="http://docs.wso2.org/wiki/display/ESB450/Writing+a+WSO2+ESB+Mediator" rel="nofollow noreferrer">Writing a WSO2 ESB Mediator</a>, I tried the "Easier Way", created a jar with synapse-core_2.1.0.wso2v8.jar included in class path.</p> <p>MANIFEST.MF is as follows</p> <pre><code>Manifest-Version: 1.0 Class-Path: synapse-core_2.1.0.wso2v8.jar Created-By: 1.7.0_07 (Oracle Corporation) </code></pre> <p>And then as article suggested, dropped the jar to repository/components/lib in the ESB.</p> <p>But after ESB restart when I try to <a href="http://docs.wso2.org/wiki/display/ESB450/Class+Mediator" rel="nofollow noreferrer">load class</a> it gives the error <strong>Class not found in the path</strong> <img src="https://i.stack.imgur.com/w1945.png" alt="Class not found in the path"></p> <p>Jar file used is shared at <a href="http://www.4shared.com/file/bDZbhKvs/siri.html" rel="nofollow noreferrer">siri.jar</a></p> <p>Wonder what is missing in the steps I followed. </p> <p>Thank you in advance.</p> <p>Note: I used <em>WSO2 Enterprise Service Bus 4.5.1</em></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload