2011/1/20 James Kosin <[email protected]>: > On 1/19/2011 6:09 PM, Jörn Kottmann wrote: >> If it is one the classpath it would be really easy to open an >> InputStream pointing >> to the real model. That InputStream can then be used as usual to >> initialize >> a component. >> >> Sounds like a nice solution for all the people which are using some kind >> of dependency management and want to try out OpenNLP quickly. >> >> For production deployments it seems not to be a nice solution, since >> it is >> more difficult to update the model while an application is running >> when it is loaded from >> the classpath. >> >> +1 for doing that >> >> Jörn >> > Jorn, > > May not be as difficult as you think. We may have a default, pointing > to the classpath. Then if provided, say on the CLI interface we could > overwrite that default with the new, non-class path route. And the > library method should already have hooks for specifying the model. > Only difficulty then would be supporting the languages and etc from the > same interface.... OUCH!
I am not asking to change the OpenNLP CLI interface. I am just hinting that models packaged as maven artifacts will help people working with opennlp as a 3rd party library. -- Olivier http://twitter.com/ogrisel - http://github.com/ogrisel
