Just to follow up on my issue - it seems to work and shows Hello in my
list of content types. I think it could have been something really
simple like a mistyped filename.
├── org
│ └── apache
│ └── tika
│ ├── mime
│ │ └── custom-mimetypes.xml
│ └── parser
│ └── hello
│ ├── HelloParser.class
│ └── HelloParser.java
└── tika-server-1.11.jar
I ran tika-server-1.11.jar using "java -classpath .:tika-server-1.11.jar
org.apache.tika.server.TikaServerCli -h 0.0.0.0" and it shows:
*application/hello*
when I go to /mime-types.
To get my parser to be listed in Parsers do I need to add anything to my
java run script? I can see at the bottom of this page
https://tika.apache.org/1.11/parser_guide.html#Add_your_MIME-Type they
say to explicitly tell your AutoDetectParser to include the new parser
but I am unsure of how to do that.
James
On 02/02/2016 04:41 PM, James Brooking wrote:
That ran the server fine but when I access
http://localhost:9998/parsers HelloParser is not present. Still no
errors or any output regarding it.
On Tue, Feb 2, 2016 at 4:33 PM, Nick Burch <[email protected]
<mailto:[email protected]>> wrote:
On Tue, 2 Feb 2016, James Brooking wrote:
I tried to add a classpath attribute but that didn't seem to
change
anything:
java -classpath "." -jar tika-server-1.11.jar -h 0.0.0.0
The -jar and -classpath options are sadly mutually incompatible
Try with:
-classpath .:tika-server-1.11.jar
org.apache.tika.server.TikaServerCli -h 0.0.0.0
Nick
