You are viewing a plain text version of this content. The canonical link for it is here.

Posted to server-dev@james.apache.org by "Matthieu Baechler (JIRA)" <se...@james.apache.org> on 2017/05/05 10:01:04 UTC

[jira] [Created] (JAMES-2018) JMAP html extraction should not use tika but jsoup

Matthieu Baechler created JAMES-2018:
----------------------------------------

             Summary: JMAP html extraction should not use tika but jsoup
                 Key: JAMES-2018
                 URL: https://issues.apache.org/jira/browse/JAMES-2018
             Project: James Server
          Issue Type: Bug
          Components: JMAP
            Reporter: Matthieu Baechler
            Assignee: Antoine Duprat


It looks like we cannot use two TextExtractor at the same time and thus, html to text transformation, very common in jmap code, is done by tika.
It's obviously overkill when we have a jsoup based TextExtractor at hand that is probably much faster because it skips content type detection).
We should qualify TextExtractor with a @Named to be able to force jsoup usage for html transformation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org