Hi, Any thoughts on this: Our OSGI service API and the DTOs used within this API are currently reused as DTO for the JSON REST endpoints. Therefore, developers add JSON annotation to the API DTOs, which a) adds a 3rd party library dependency and b) pollutes the DTOs with a specific technology implementation choice. Both I don’t like, but maintaining two identical DTOs that’s only difference is the JSON annotation is kind of annoying to the developer.
Any thoughts/best practices? How is this done in other projects. Thanks in advance Frank
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
