Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to reference this mediator? #1

Open
bratislav opened this issue Jul 5, 2016 · 4 comments
Open

How to reference this mediator? #1

bratislav opened this issue Jul 5, 2016 · 4 comments

Comments

@bratislav
Copy link

bratislav commented Jul 5, 2016

Hi mephist,

I've built your custom mediator and placed the JAR file into dropins, but I'm not sure now how to use it in my proxy. Here's what I'm trying to do :

<?xml version="1.0" encoding="UTF-8"?>
<api context="/testapi" name="db" xmlns="http://ws.apache.org/ns/synapse" xmlns:a="http://esb.agava.net/mediators/db/dbselect">
  <resource methods="GET" protocol="http">
    <inSequence>
      <log/>
      <a:dbselect>
        <a:connection>
          <a:pool>
            <a:password>1234</a:password>
            <a:driver>net.sourceforge.jtds.jdbc.Driver</a:driver>
            <a:url>jdbc:jtds:sqlserver://server\\sql2008r2;database=DB_M1</a:url>
            <a:user>sa</a:user>
          </a:pool>
        </a:connection>
        <a:statement>
          <a:sql><![CDATA[select * from Accounts where Currency = 'eur']]></a:sql>
        </a:statement>
      </a:dbselect>
      <log/>
...

First, I cannot save this file anymore in the Eclipse, but when I force saving and deploy I'm getting the following error :

Caused by: org.apache.synapse.SynapseException: Unknown mediator referenced by configuration element : {http://esb.agava.net/mediators/db/dbselect}dbselect
    at org.apache.synapse.config.xml.MediatorFactoryFinder.getMediator(MediatorFactoryFinder.java:219) 

Thanx in advance.

@etrvala
Copy link

etrvala commented Dec 8, 2016

Hi,
Have you succeeded to use it?
Thanks!

@victorviola
Copy link

@etrvala
Hi there, I have the same issue mentioned above and I couldn't fix. @bratislav Have you fixed it?

Thank you all.

@bratislav
Copy link
Author

I think I did, but can't remember how, it was 5 months ago...we eventually decided to drop wso2 just because the documentation and the community was horrible and decided to move to Mule ESB

@victorviola
Copy link

victorviola commented Dec 27, 2016

Thank you for your reply. I have been using WSO2 for 1 year and had successful applications running at the moment. Although, I must agree with you. The WSO2 community is a little bit small.

I dropped out this mediator and I did one by myself =)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants