Open
Description
Hi guys,
I’m developing a REST client, which interacts with Jersey RESTful ws, which is use DTOs with JAXB annotations. And I need to make that client embeddable to server-side applications and to Android platform as well.
When I write a simple client for the server-side than everything is ok. But there is an issue with Android. After some research I founded a few limitations of Android platform:
- It won’t let you add a jar which includes classes in the
javax.xmlnamespace (which is where the JAXB API lives). - JAXB uses JAXP 1.3 DatatypeFactory, but Android doesn’t provide it.
- JAXB uses
javax.activation.DataHandler - It doesn’t support package level annotations (which JAXB uses).
So I don’t know maybe Restlet Framework has some work around to make all this stuff less painful.
Here is my example of usage of Restlet on Android:
https://gist.github.com/Krasnyanskiy/a1563996829ba2f05f6b
And my error:
Error:Execution failed for task ':app:preDexDebug'.
> com.android.ide.common.internal.LoggedErrorException: Failed to run command:
/Applications/Android Studio.app/sdk/build-tools/21.0.2/dx --dex --output /Users/krasnyaskiy/AndroidStudioProjects/client-poc/app/build/intermediates/pre-dexed/debug/stax-api-1.0-2-423956290996cba5c5243bbc25620fb74a9a3abd.jar /Users/krasnyaskiy/.gradle/caches/modules-2/files-2.1/javax.xml.stream/stax-api/1.0-2/d6337b0de8b25e53e81b922352fbea9f9f57ba0b/stax-api-1.0-2.jar
Error Code:
1
Output:
trouble processing "javax/xml/stream/EventFilter.class":
Ill-advised or mistaken usage of a core class (java.* or javax.*)
when not building a core library.
This is often due to inadvertently including a core library file
in your application's project, when using an IDE (such as
Eclipse). If you are sure you're not intentionally defining a
core class, then this is the most likely explanation of what's
going on.
However, you might actually be trying to define a class in a core
namespace, the source of which you may have taken, for example,
from a non-Android virtual machine project. This will most
assuredly not work. At a minimum, it jeopardizes the
compatibility of your app with future versions of the platform.
It is also often of questionable legality.
If you really intend to build a core library -- which is only
appropriate as part of creating a full virtual machine
distribution, 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 be forewarned that your application
will still fail to build or run, at some point. Please be
prepared for angry customers who find, for example, that your
application ceases to function once they upgrade their operating
system. You will be to blame for this problem.
If you are legitimately using some code that happens to be in a
core package, then the easiest safe alternative you have is to
repackage that code. That is, move the classes in question into
your own package namespace. This means that they will never be in
conflict with core system classes. JarJar is a tool that may help
you in this endeavor. If you find that you cannot do this, then
that is an indication that the path you are on will ultimately
lead to pain, suffering, grief, and lamentation.
1 error; aborting