Hi Adriano, It wasn't added, so I guess we still need to keep the class. Any other ideas? One thing I'm thinking of is to pass "--core-library" as an option to dex, even though the error message kinda of advices not to do so when building applications. Anyhow, I'll keep you posted on any progress.
On Wed, Aug 27, 2008 at 11:44 PM, Adriano Crestani < [EMAIL PROTECTED]> wrote: > Hi Oscar, > > Please, check if in the latest Android SDK the javax.xml.namespace.QName > was added. If it does, remove this class from the android-jdk-classes > project. > > Regards, > Adriano Crestani > > > On Wed, Aug 27, 2008 at 2:38 PM, Oscar Castaneda < > [EMAIL PROTECTED]> wrote: > >> Hi Luciano, >> >> Unfortunately, not yet. Sorry for the confusion, I should've mentioned >> that with the reduced set of modules calculator2 runs with no problems on a >> PC and not on Android. >> >> When testing with the new SDK the problem I'm facing is that when dex is >> processing the stax-api-1.0-2.jar it shows the errors shown below. I haven't >> found how to use the 'dx' utility from the SDK in such a way that I can pass >> "--core-library" as an option, and neither have I found how to do this >> through Eclipse. However, from the error message it seems like using this >> option would not be a good idea. Any thoughts or ideas on this are welcomed >> and appreciated. >> >> [2008-08-27 23:23:55 - calculator-android] >> trouble processing "javax/xml/namespace/QName$1.class": >> [2008-08-27 23:23:55 - calculator-android] >> Attempt to include a core VM class in something other than a core library. >> It is likely that you have attempted to include the core library from a >> desktop >> virtual machine into an application, which will most assuredly not work. >> If >> you really intend to build a core library -- which is only appropriate as >> part of creating a full virtual machine binary, as opposed to compiling an >> application -- then use the "--core-library" option to suppress this error >> message. If you go ahead and use "--core-library" but are in fact building >> an application, then please be aware that your build will still fail at >> some >> point; you will simply be denied the pleasure of reading this helpful >> error >> message. >> [2008-08-27 23:23:55 - calculator-android] 1 error; aborting >> [2008-08-27 23:23:55 - calculator-android] Conversion to Dalvik format >> failed with error 1 >> >> >> On Wed, Aug 27, 2008 at 10:23 PM, Luciano Resende <[EMAIL PROTECTED]>wrote: >> >>> Hey Oscar >>> >>> I was just looking into your latest updates in TUSCANY-2440, am I >>> reading it right that you were able to successfully run a calculator2 >>> in Android using the new SDK ? >>> >>> On Wed, Aug 27, 2008 at 12:07 PM, Oscar Castaneda >>> <[EMAIL PROTECTED]> wrote: >>> > 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 >>> > >>> >>> >>> >>> -- >>> Luciano Resende >>> Apache Tuscany Committer >>> http://people.apache.org/~lresende<http://people.apache.org/%7Elresende> >>> http://lresende.blogspot.com/ >>> >> >> >> >> -- >> best, >> -oscar >> >> Oscar Castañeda >> > > -- best, -oscar Oscar Castañeda
