You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2010/05/04 18:09:03 UTC
[jira] Resolved: (TIKA-419) Allow parser lookup from a custom class
loader
[ https://issues.apache.org/jira/browse/TIKA-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved TIKA-419.
--------------------------------
Resolution: Fixed
Done in revision 940926.
> 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.
Re: [jira] Resolved: (TIKA-419) Allow parser lookup from a custom
class loader
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Nice, Jukka!
Cheers,
Chris
On 5/4/10 9:09 AM, "Jukka Zitting (JIRA)" <ji...@apache.org> wrote:
[ https://issues.apache.org/jira/browse/TIKA-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved TIKA-419.
--------------------------------
Resolution: Fixed
Done in revision 940926.
> 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.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: Chris.Mattmann@jpl.nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++