在Android应用程序与Jersey服务器应用程序之间共享类

Question

I'm building an Android application that will talk to a web service built in Java and Jersey.

I've currently organized three projects:

• core (common) is a simple set of POJOs for my domain models
• client (android) is the Android application
• server (jersey) is a Jersey application storing data in MongoDB and relying on the Morphia library for persistence.

The core library is a project dependency for each of the other two.

The problem is that I've created my set of entity classes in "core", but those classes are configured for Morphia using annotations. This means Morphia in turn becomes a dependency on my Android application, which I don't particularly like.

Ideally, Morphia would allow configuration via flat files but it only supports configuring entity classes via annotations.

Should I suck up the ugly dependency of 'core' relying on Morphia, or is there a better way to organize my classes that I'm not thinking of?

Note: I have tried removing the Morphia annotations from the core classes, and created new classes in the "server" project that inherit the "core" classes and add the Morphia annotations. However, if my Jersey application returns classes from the server project, then the Android client can't use those classes with the Jersey client.

Thanks

Answer 1

I did end up switching to a different POJO mapper. I've decided to go with Kundera. This effectively creates only one dependency on javax-persistence in my core project (for JPA annotations).

Answer 2

You could switch from Morphia to another MongoDB pojo mapper that uses Jackson annotations such as mongo-jackson-mapper or bson4jackson . This way your Android project would have dependencies on Jackson instead of Morphia.