blocks|key|1468589|text|事实证明，我的堆栈跟踪还不够好，问题不是没有包含外部JAR。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1468590|问题是Android平台缺少javax.naming.*以及外部JAR依赖的许多其他包。|1468591|添加外部JAR文件，并在Eclipse中设置Order和Export，与Android项目的工作预期一样。|1468592|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Turns out I have not looked good enough at my stack trace, the problem is not that the external JAR is not included.

The problem is that Android platform is missing javax.naming.* and many other packages that the external JAR has dependencies too.

Adding external JAR files, and setting Order and Export in Eclipse works as expected with Android projects.

blocks|key|1253913|text|Android的Java+API不支持javax.naming.*和许多其他javax.*内容。您需要将依赖项作为单独的jars包含在内。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1253914|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Android's Java API does not support javax.naming.* and many other javax.* stuff. You need to include the dependencies as separate jars.

blocks|key|1253998|text|我目前使用的是SDK+20.0.3，之前的解决方案对我都不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1253999|hessdroid在hess失败的地方工作的原因是因为这两个jar文件包含为不同虚拟机编译的java。Java编译器创建的字节代码不能保证在Dalvik虚拟机上运行。不能保证Android编译器创建的字节代码可以在Java虚拟机上运行。|1254000|在我的例子中，我可以访问源代码，并能够使用我在这里描述的方法为它创建一个Android+jar文件：https://stackoverflow.com/a/13144382/545064|offset|length|1254001|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/13144382/545064^0|0|0|1E|17|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

I'm currently using SDK 20.0.3 and none of the previous solutions worked for me. 

The reason that hessdroid works where hess failed is because the two jar files contain java that is compiled for different virtual machines. The byte code created by the Java compiler is not guaranteed to run on the Dalvik virtual machine. The byte code created by the Android compiler is not guaranteed to run on the Java virtual machine.

In my case I had access to the source code and was able to create an Android jar file for it using the method that I described here: <a href="https://stackoverflow.com/a/13144382/545064">https://stackoverflow.com/a/13144382/545064</a>

blocks|key|1468747|text|在android+studio中(如果使用gradle|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1468748|将此内容添加到build.gradle|1468749|compile+fileTree(dir:+'libs',+include:+['*.jar'])|code-block|syntax|javascript|1468750|并将jar文件添加到libs文件夹|1468751|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

in android studio if using gradle

add this to build.gradle

<pre><code>compile fileTree(dir: 'libs', include: ['*.jar'])
</code></pre>

and add the jar file to libs folder

I have created an Android project and added an external JAR (hessian-4.0.1.jar) to my project. I then added the JAR to the build path and checked it off in Order and Export.

Order and Export is ignored it seems, and all classes from the external JAR are missing at runtime.

Is there a trick to properly include the needed classes from an external JAR when building an Android application using the Eclipse plugin? I do not want to use ant or Maven.

How can I use external JARs in an Android project?

虚拟机

编译器

Android

Eclipse

Java

我已经创建了一个Android项目，并在项目中添加了一个外部JAR (hessian 4.0.1.jar)。然后，我将JAR添加到构建路径中，并在Order和Export中将其选中。Order和Export似乎被忽略了，外部JAR中的所有类在运行时都会丢失。在使用Eclipse插件构建Android应用程序时，是否有一...

问如何在Android项目中使用外部JAR？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Android项目中使用外部JAR？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Android项目中使用外部JAR？
EN