On 06/22/2012 03:26 PM, Rajith Attapattu wrote:
Actually the cpp binding implementation, in addition to the jni code, depends on common code and utility classes (for message codecs etc..). So I was not correct when I said the only dependency is the public API jar.
That is indeed a significant complication to the picture.
Then it's going to be no different from the current situation, infact a bit worse as the common code, utility classes can change quite frequently. The JNI jar is less volatile compared to the above. So the lesser of the two evils. To me the ideal solution seems to be, where the swig files (for the java side) are placed on the java tree and the code is generated during the java build. Unfortunately this would be a bit difficult... but not impossible. We currently rely on the spec file being in a particular location. Similarly we could rely on the location of the include files and the qpid.i file What do you think ?
So what jars would be produced? Would the JNI wrapper and API implementation that used that be included in the qpid-client jar? Or would it be split out?
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
