tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ken Krugler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TIKA-419) Allow parser lookup from a custom class loader
Date Sun, 12 Sep 2010 19:17:33 GMT

    [ https://issues.apache.org/jira/browse/TIKA-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908530#action_12908530
] 

Ken Krugler commented on TIKA-419:
----------------------------------

>From the most recent comments on [SOLR-1902], it appears that Bad's issue (from the preceding
comment) has been resolved, at least in Solr-trunk, 1.4.2 (or later), and 3.x.


> Allow parser lookup from a custom class loader
> ----------------------------------------------
>
>                 Key: TIKA-419
>                 URL: https://issues.apache.org/jira/browse/TIKA-419
>             Project: Tika
>          Issue Type: Improvement
>          Components: config
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 0.8
>
>
> Since TIKA-317 we've used the javax.imageio.spi.ServiceRegistry.lookupProviders(Class<?>)
method to look up all the currently available Parser implementations. This method uses the
context class loader of the current thread for looking up Parser classes.
> As seen in NUTCH-810 and discussed on tika-users@, this is troublesome for applications
with more complex class loading mechanisms. To solve the issue, it would be good to allow
the client to optionally specify an explicit class loader instance from which parsers are
to be looked up.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message