This page is meant to detail blocking issues with Android. At the start of the project the main issue related to Android was its lack of support of Annotations. A suggested workaround for issues related to Annotations was to use retrotranslator. After succesfully translating the SCA modules and modified Android modules with retrotranslator the Annotation related errors ceased. These errors are mainly related to lack of RMI support. This will be the first blocking issue on the list. As issues are resolved they will be scratched off and any new issues that arise will be added.

Issues:

1. ClassNotFound errors for java.rmi.Remote
2. ClassNotFound errors for java.beans.Introspector

Suggested workarounds:

1. Three workarounds have been suggested.

• Comment out all the code that uses the RMI API

• Get rid of java.rmi.Remote replacing it with java.lang.Cloneable using the folowing Retrotranslator option:

-backport java.rmi.Remote:java.lang.Cloneable

But in case there is important code using the java.rmi package, an alternative is to take sources of java.rmi from Apache Harmony. Then move the sources into another package, for example mypack.java.rmi, which should be compiled and put into a JAR. After that use it with Retrotranslator:

-backport mypack -classpath mypack.jar

But this approach works only if the sources don't employ native code

• Removing RMI should be as simple as removing the tuscany-binding-rmi
  dependency from host-android.

JIRA tickets:

1. Created JIRA ticket for issues 1 and 2.

https://issues.apache.org/jira/browse/TUSCANY-2440