[
https://issues.apache.org/jira/browse/TIKA-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18030672#comment-18030672
]
Tim Allison edited comment on TIKA-4512 at 10/17/25 3:38 PM:
-------------------------------------------------------------
One problem with json everywhere is that we'll have jackson-databind
everywhere, but that means that we can eventually get rid of our own homegrown
serialization code which would be amazing.
Another problem is that we'll either have jackson annotations everywhere or
have to code in a serialization-friendly way: getters and setters have to
match, no final member variables etc.
What else do we add to the cons list?
was (Author: [email protected]):
One problem with json everywhere is that we'll have jackson-databind
everywhere, but that means that we can eventually get rid of our own homegrown
serialization code which would be amazing.
> Experiment with pf4j for tika-pipes
> -----------------------------------
>
> Key: TIKA-4512
> URL: https://issues.apache.org/jira/browse/TIKA-4512
> Project: Tika
> Issue Type: Sub-task
> Reporter: Tim Allison
> Priority: Major
>
> This is proof of concept work based on [~ndipiazza] 's TIKA-4272-docker
> branch.
> I really like a lot of that work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
