Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/1414
@jdye64 The client dto package was designed to be simple POJOs and with no
dependencies to make it easy to consume for any clients of the REST API.
Unfortunately, along the way we ended up adding a dependency on the
documentation library (swagger).
This proposed change will add another dependency on a serialization library
that the client may or may not be using. We have left all serialization logic
to be specified via JAXB annotations to try to remain agnostic to whatever
serialization or REST library the client is using.
In you happen to be using Jackson, things should (de)serialize correctly by
just setting the (de)serializationConfig to use the JAXB annotation
introspector. Here's an example from the NiFi codebase [1].
[1]
https://github.com/apache/nifi/blob/master/nifi-commons/nifi-web-utils/src/main/java/org/apache/nifi/web/util/ObjectMapperResolver.java
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
