Hi Devs

Since several days I'm trying to build a proper application, using the 
andes-client.jar. Because I'm not so deep familiar with all this packaging 
mechanisms, classloader in WebContainer/ApplicationServer and library 
conflicts, I want to ask you Devs directly and hope to get some hints from some 
of you.


What I need to do:

For a customer I need to implement a WSO2 client into our software for 
connecting to a WSO2 MessageBroker.


What I've done:

I've downloaded the WSO2 Message Broker 3.1.0 and installed it on a virtual 
machine. According to the 'Samples' documentation of the MB, I copied the 
andes-client-3.1.1.jar into our application. Everything works fine so far. I 
can connect to the Message Broker and can read the sent messages.


My environment:

At the moment I'm using a WildFly 10 application server (we will switch back to 
a simple servlet container like Tomcat in near future. For that reason we have 
prepared our deployment to have only a .war file. No .ear files anymore). But 
for now, I've created a server module for activating the andes-client. 
Activating and using of this 'WSO2' module works perfectly together with my MB 
virtual machine.


My problem:

Connecting to a WSO2 MB is just a small part of our software. Another small 
part of our application is connecting to a directory server (LDAP, a.s.o.) For 
doing that, I use the Apache's directory api. And here my problem begins...

Apache's directory api uses the Apache mina artifact (version 2.0.9). The 
artifact is referenced through a maven dependency.

Your andes-client-3.1.1.jar bundle includes the Apache's mina package in 
version 1.1.7.


The package structure and class naming of the different mina versions seems to 
be completely incompatible, so each artifact (andes-client and directory) needs 
the coresponding mina version. Otherwise those artifacts does not work proper.


What do you recommend me to solve this problem? Could you give me some hints / 
key points, how to avoid this library conflicts? I'm not sure if OSGi would be 
the right way (I don't have any knowledge about OSGi and to be honest, the 
documentation is so extremely large that I really don't know where to begin to 
read). Also I thought about relocating the org.apache.mina to 
org.wso2.apache.mina inside the andes-client.jar. Would this be a reasonable 
way? Or is it planned in near future that the mina artifact would be replaced 
with a newer version?


Thank you very much for some hints. I would be glad to hear from you!

If you need more clarifying information from me, feel free to ask


Greets, Michael
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to