Hi, Let me add some more goods and bads here:
Good: With all the goods points I have mentioned on this thread, we will need to modify almost nothing of tuscany sca code to get it running on android (I expect) Bad: When android converts included eclipse project, jars and etc to the android format, it includes everything in the same .apk file. So, if there are more than one class with the same package and name there will be a conflict, anyway, I dont think this is a problem, the java packages exists to solve this kind of problem. The problem is with the non .class files. Like, for example, if you have more than one org/apache/tuscany/sca/binding/sca/definitions.xml, each one in different modules or jars, the convertion will fail, because there cannot be 2 files with the same name and in the same folder in the .apk file. It's possible on a JVM because each definitions.xml file will have a different class loader, but on the android platform, there is only one class loader for the entire apk. Anyway, we can think about it in future when we get tuscany android running fine in an IDE : ) Adriano Crestani On Wed, Oct 8, 2008 at 10:36 PM, Adriano Crestani < [EMAIL PROTECTED]> wrote: > Hi all, > > I've been testing the latest android SDK version (1.0-rc1). > > Android improvements: > > - Annotations are finally working...they finally implemented the native > method for the emulator, on the old version we had only the native methods > > - Now the android is including the resources (non class files), those > defined in the android project and in its included projects, in its package > and not ignoring as it used to do. It's really good, because we don't need > to adapt the way Android SCA looks for resouces anymore. > > - The android plugin is finally including the android included projects > dependencies. On old versions, any dependency included in any included > project needed to be also included in the android project. > > Bad news: > > - android sdk still doesn't contain many JDK classes, mainly the ones that > tuscany uses a lot, like xml api, just few classes from this api is in the > actual android sdk : ( > > - android .class converter is by default failing when it tries to convert a > .class file that are JDK classes...even if this is not included in the > android SDK. I can force the converter using the --core-library argument, > but unfortunatelly there is no option to set this option on android builder. > The only way I could convert was using an ant build. But debugging on the > emulator using command line is really painful. I have tried to generate the > .apk file (the android executable file) and place it on the eclipse android > project and I tried to run it from eclipse, but I get an error saying that > the .apk is not found. I think when the .apk is generated by the android > builder, it also register the .apk on the emulator, I'm not sure, but I will > work on that. > > > The last bad issue is a problem, because I need to add a lot of xml classes > from jdk and it's not being possible. These classes are used by stax api and > some other tuscany classes. > > Oscar and me have already complained about these bad issues on android ML, > but unfortunately android developers are not good at answering questions as > tuscany's : ) > > I think that's it : ) > > Comments, suggestions and critics are welcome :-) > > Adriano Crestani > >
