[
https://issues.apache.org/jira/browse/TIKA-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871132#comment-17871132
]
Tilman Hausherr commented on TIKA-4294:
---------------------------------------
What I mean is that if its name is equal to the superclass, then the result is
the superclass. Else if not equal, then the class is created from the
superclass name and again, the result is the superclass.
{code}
Class superClazz = Class.forName(superClassName);
{code}
would be the same.
After writing this I googled... seems that yes it does take time, then your
code should stay that way
https://stackoverflow.com/questions/18231991/class-forname-caching
https://stackoverflow.com/questions/25967441/difference-between-calling-a-class-constructor-and-using-class-forname-newinst
> Simplify serialization/deserialization of ParseContext
> ------------------------------------------------------
>
> Key: TIKA-4294
> URL: https://issues.apache.org/jira/browse/TIKA-4294
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Trivial
> Fix For: 3.0.0
>
>
> Via [~dimirsen] (?) and [~tilman]'s ping on TIKA-4252, we should simplify the
> serialization and deserialization of ParseContext to avoid redundancy of the
> superclass.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
