On Sep 11, 2010, at 1:17pm, Ken Krugler wrote:
On Fri, Sep 10, 2010 at 10:31 PM, Nick Burch
wrote:
Quite a lot of OfficeParser does depend on poifs code though, as
well as a
few bits that depend on some of the less common POI text extractors.
It looks like a number of our other new parse
There are the situations, I could think about, where you would like to
implement customized classloader:
1. You need different hierarchy to load classes, as OSGi for instance.
Hollywood principle if you like.
2. When you need to run different versions of classes or jars. For example,
you want to lo
Hi,
On Sun, Sep 12, 2010 at 5:46 PM, Ken Krugler
wrote:
> But that also seems clunky. Any other suggestions?
A simpler approach would be to simply pass a list of already
instantiated Parser objects to AutoDetectParser, like this:
public AutoDetectParser(Detector detector, Parser... parsers)
[
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 appear
Hi Jukka,
On Sun, Sep 12, 2010 at 5:46 PM, Ken Krugler
wrote:
But that also seems clunky. Any other suggestions?
A simpler approach would be to simply pass a list of already
instantiated Parser objects to AutoDetectParser, like this:
public AutoDetectParser(Detector detector, Parser... p
