[jacorb-developer] Jacorb 3.x, RMI and Android

Nick Cross jacorb at goots.org
Wed May 29 16:04:49 CEST 2013


On 29/05/13 14:19, Emmanuel TAUREL wrote:
> Hi Nick,
>
> Thank's for your answer.
>
> On 29/05/2013 10:11, Nick Cross wrote:
>>
>> Hi,
>>
>> The org.jacorb.orb.Reference / no-rmi option was changed when early
>> JDK 1.3 template files were removed. JacORB now requires 1.6 or
>> greater to run.
>>
>> Saying that, while I have not tested JacORB on Android, I would be
>> happy to help with any issues.
>>
>> For your reference issue, would it be possible to create some dummy
>> stub classes
> I don't really understand what you mean here.

Write simple wrapper classes e.g.
package javax.rmi.CORBA
public class Stub extends ObjectImpl {}
etc etc

>> or to try obtaining the RMI classes from
>> http://www.gnu.org/software/classpath which might be sufficient for
>> your use-case?
> You mean getting all RMI related classes sources from here and add them
> to our Android apps? I don't know exactly how many classes are concerned
> here but I am afraid it's a bit heavy
 >
> But what about class org.jacorb.orb.Reference class simply inheriting
> from org.omg.CORBA.portable.ObjectImpl as it was in previous JacORB release
> when the no-rmi compilation option was supported?
> To start our application on the Android device,  this is what we did but
> manually and we are not sure that this is a 100 % sure fix.

This is the problem - we have not tested on Android and just briefly 
looking through the codebase I can see references to java.rmi.* and 
javax.rmi.* in several places. Just reverting a single file will not 
help you as such. While the ORB might start there is a possibility of 
hitting these code paths *depending on what you are doing*.

Regards

Nick

> Regards
>
> Emmanuel
>
>
>>
>> Regards
>>
>> Nick
>>
>>
>> On 28/05/13 09:10, Emmanuel TAUREL wrote:
>>> Hello all,
>>>
>>> We are using JacORB for one of our project that we would like to run on
>>> Android device.
>>> Unfortunately, on the Dalvik Java virtual machine, RMI classes are not
>>> available.
>>> With JacORB 2.X, we had the "no-rmi" option to compile JacORB. This
>>> allowed us to use JacORB 2.X on Android devices
>>> With JacORB 3.X, it seems that this compilation option is not available
>>> any more! As a consequence, we cannot run JacORB 3.X on Android device
>>> (class not found exception)
>>>
>>> After a look in JacORB 2.X about what this option no-rmi did, we have
>>> manually change the inheritance in class defined in file
>>> org/jacorb/orb/Reference.java.
>>> With this trick, we are able to run our application with JacORB 3.X an
>>> dit seems to work. But this is not a valuable solution.
>>>
>>> Is there any clean way to run JacORB 3.X on Android device?
>>> Is changing the inheritance in class defined in
>>> org/jacorb/orb/Reference.java the only required change to run JacORB on
>>> Android?
>>>
>>> Thank's in advance for your answers
>>>
>>> Emmanuel
>>>
>>> _______________________________________________
>>> jacorb-developer maillist  -
>>> jacorb-developer at lists.spline.inf.fu-berlin.de
>>> https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-developer
>>
>
>



More information about the jacorb-developer mailing list