This week's book giveaway is in the OCMJEA forum. We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line! See this thread for details.
Hi all I am modifying a C++ application in order to expose a public interface to some of it's functionality. The clients using this public interface will be in C++ or Java. The options for the public interface which have been suggested to me are XML-RPC or SOAP CORBA (Orbacus orb which supports Java and C++ mappings) Can anyone give me some pros/cons for using both of these. The interface I'm exposing won't be anything complex but it does need to be secure, i.e. over SSL. Also I don't want to mandate that clients use particular ORBs etc, i.e. I want to avoid any interoperability issues. Also, would it be an option (or even a good idea) to use JNI on the server side - e.g. if I go with corba I would have a corba server implemented in java which maps the interface methods to the equivalent C++ functionaliyt using JNI. This would give me more options as to what I could use for the interface e.g. free Java ORB instead of Orbacus or even RMI (over IIOP to support potential C++ clients). Also the amount of C++ I would have to write would be minimal (I have v.little exp in C++ but lots in Java!). Can anyone give me their thoughts on this? I'd appreciate it! Alex