cancel
Showing results for 
Search instead for 
Did you mean: 

CustDB Sample for Android fails to run in Eclipse 3.7; Android 4.1

Former Member
0 Kudos
2,352

I recently installed Eclipse - Indigo Service Release 2 - version 3.7.2. The installed JREs are: jdk1.7.0_04 and fre6. The Android 4.1 and Google APIs are installed - both API Level 16. I am running on a Windows 7 Pro 64-bit PC with latest updates.

The CustDB Sample for Android that comes with SQLAnywhere 12 won't compile when I do the following steps:

  1. Locate the sample folders and change the directory names all to lowercase as instructed by the readme.txt file that exists in the CustDB main sample folder.
  2. Run setup.bat to copy the UltraLiteJNI12.jar file to the CustDBlibs folder and the libultralitej12.so file to the CustDBlibsarmeabi folder.
  3. Confirmed that the files were copied successfully.
  4. Instead of following the instructions provided in the SQL Anywhere 12.0.1 help file under the heading "Tutorial: Building an Android Application", "Lesson 1: Setup a new Android project, I am selecting File-Import-Android-Existing Android Code Into Workspace.
  5. I Browse to the CustDB sample folder and select it as the Root Directory.
  6. I check the "Copy projects into workspace" checkbox.
  7. In the Projects list, the project com.sybase.custdb.CustDBMain appears along with the full path to this project.
  8. Immediately a "Problem Occurred" dialog appears indicating that "Marker id 321 not found. The console indicates two lines, both state: com.sybase.custdb.CustDBMain] Unable to resolve target 'android-8'
  9. I click Ok on the dialog and then right-click the new com.sybase.custdb.CustDBMain project in the Project Explorer and select Properties. I select the Java Build Path and go to the Libraries tab. The UltraliteJNI12.jar file indicates that it is missing, so I highlight the entry and click the "Edit" button. The dialog correctly points to the correct ..libs folder, so I highlight the .jar file and click "Open". I click "Ok" and then select "Project-Clean" to build attempt to build the project again.
  10. 31 Errors are listed along with 20 Warnings. All of the errors are resource related due to the fact that the import process duplicated the drawable_hdpi, drawable_ldpi, and drawable_mdpi folders. I move the icon.png files from the offending folders into the auto-generated folders of the same name and Clean the project again.
  11. This time there are no Errors in the Problems tab, but there are still 20 Warnings related to dead code, deprecated methods, and Vector type issues.

At this point, if I try to run the project, this is the FATAL error that is shown:

FATAL [main] Main - No embedded stylesheet instruction for file: file:/E:/Documents/Eclipse%20Workspace/com.sybase.custdb.CustDBMain/AndroidManifest.xml org.eclipse.wst.xsl.jaxp.debug.invoker.TransformationException: No embedded stylesheet instruction for file: file:/E:/Documents/Eclipse%20Workspace/com.sybase.custdb.CustDBMain/AndroidManifest.xml at org.eclipse.wst.xsl.jaxp.debug.invoker.internal.JAXPSAXProcessorInvoker.transform(JAXPSAXProcessorInvoker.java:225) at org.eclipse.wst.xsl.jaxp.debug.invoker.internal.JAXPSAXProcessorInvoker.transform(JAXPSAXProcessorInvoker.java:186) at org.eclipse.wst.xsl.jaxp.debug.invoker.internal.Main.main(Main.java:73) Caused by: org.eclipse.wst.xsl.jaxp.debug.invoker.TransformationException: No embedded stylesheet instruction for file: file:/E:/Documents/Eclipse%20Workspace/com.sybase.custdb.CustDBMain/AndroidManifest.xml at org.eclipse.wst.xsl.jaxp.debug.invoker.internal.JAXPSAXProcessorInvoker.transform(JAXPSAXProcessorInvoker.java:214)

I am relatively new to Eclipse and Android, but have been a C# programmer for a number of years now, as well as VB.

Any help would be GREATLY appreciated.

MarkR

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member

The sample was originally developed with Eclipse 3.6.2 and targetted for Android 2.2, but it should work with Android 4.1. I believe that the Android Dalvik JVM only supports JDK 1.6 byte code, so I would recommend configuring your Eclipse with JDK 1.6.

Former Member
0 Kudos

Thank you for your suggestion. I installed the Android 2.2 ADK and set the project to build to that version and it worked.

MarkR