Hi Mike, Thanks for your suggestion. I discussed it with Adriano and the problem we find is that even if we turn off introspection, either by using a <componentType/> side file or removing annotations, the Android SDK would still choke when encountering any code with annotations. Fortunately, however, Google recently released an updated version of the SDK. We have started testing it and have made some progress. I will continue helping Adriano in these efforts.
On Thu, Aug 14, 2008 at 6:05 PM, Mike Edwards < [EMAIL PROTECTED]> wrote: > Folks, > > One thing worth considering - if it is the introspection of the Java > implementation classes that is causing the problems, one possibility is to > turn off this introspection and instead to supply the equivalent information > as <componentType/> side files. Then everything just reads XML, which is > known to work. I think the main use of introspection is in the computation > of the componentType for the implementation classes. > > > Yours, Mike. > > Adriano Crestani wrote: > >> Good summary Oscar : ) >> >> Yes, I know we haven't solved the problem yet, but now we know what it is. >> Unfortunately we got back to the point before using retrotranslator, it >> worked for what it was supposed to, but it messed something up :S. >> >> Yes, lets try the Luciano's suggestion and comment/workaround every SCA >> code line that tries to use the Reflect API (please, check my last emails >> about that on this thread). I think it will not take too much time, run the >> app on the Android platform and when you get an error, just look at that >> Android console for exception stack trace and fix it. >> >> Let us know if you have any questions >> >> Regards, >> Adriano Crestani >> >> <snip> > -- best, -oscar Oscar Castañeda
