[jira] Commented: (TUSCANY-2440) ClassNotFoundException on calculator-android after translating SCA and mobile-android code with Retrotranslator

["Adriano Crestani (JIRA)" <de...@tuscany.apache.org>]

    [ https://issues.apache.org/jira/browse/TUSCANY-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627187#action_12627187 ] 

Adriano Crestani commented on TUSCANY-2440:
-------------------------------------------

Hi Oscar,

I'm not getting the reason you cannot create a patch.

Are you sending all these files because you want me to commit all of them or just check which you modified?

Regards,
Adriano Crestani

> ClassNotFoundException on calculator-android after translating SCA and mobile-android code with Retrotranslator
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-2440
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2440
>             Project: Tuscany
>          Issue Type: Improvement
>          Components: Java SCA Core Runtime
>    Affects Versions: Java-SCA-1.2
>         Environment: Mac OS X 10.5, Maven version: 2.0.6, java version "1.5.0_13", Apache Ant version 1.7.0
>            Reporter: Oscar Castaneda
>            Priority: Minor
>             Fix For: Java-SCA-Next
>
>         Attachments: patchfile25Jun2008, patchfile27Jun2008, retrotranslator_readme, tuscany_modules_reduced.tar.gz
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> The current Android SDK does not support Annotations, as a result calculator-android runs with Annotation related errors. A suggested workaround [1] for issues related to Annotations is to translate source code with Retrotranslator [1]. After succesfully translating the SCA modules and modified Android modules with Retrotranslator the Annotation related errors cease. However, running calculator-android results in ClassNotFound errors for java.rmi.Remote in the first test (Patch from 25Jun2008) and java.beans.Introspector in a more recent test (Patch from 27Jun2008). The difference between both tests being uncommented/commented code, respectively, in JavaRuntimeModuleActivator.java (org.apache.tuscany.sca.implementation.java.module). 
> Three workarounds have been suggested:
> 1) Comment out all the code that uses the RMI API
> 2) Follow suggestions in [3] to either replace java.rmi.Remote with java.lang.Cloneable (as the result of using a retrotranslator option) or taking the RMI source from Apache Harmony and putting it in a retrotranslated JAR.
> 3) Removing RMI should be as simple as removing the tuscany-binding-rmi
> dependency from host-android.
> Upon failure of these workarounds the alternative is to minimize the number of component types supported (java) and bindings (default sca binding) and then try to run the calculator sample application. When calculator-android runs successfully further steps will be discussed on dev-list.
> A blocking-issues [4] and a porting limitations page [5] have been setup tracking these efforts.
> [1] http://code.google.com/p/android/issues/detail?id=29
> [2] http://retrotranslator.sourceforge.net/#android
> [3] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/18Jun2008-2
> [4] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Blocking+issues
> [5] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Limitation+on+porting+SCA+to+Android+platform

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.