Haven't used any arguments. From the source code I looked at, the only optional arg is port.
I started looking at the services exposed, especially TikaResource, but I got busy with some other work. I think either exposing an xhtml resource, or modifying the existing to use accept-headers to identify the requested return format would be valuable. Also adding something similar to the metadata service to return in json or xml. -Aaron "Mattmann, Chris A (388J)" <[email protected]> wrote: >Hi AJ, > >What command are you running the start the server? > >Cheers, >Chris > >On 1/31/13 12:01 PM, "AJ Weber" <[email protected]> wrote: > >>Me again, decided to start a new thread with an appropriate subject. >> >>Having trouble getting the WS Server to start. Just trying to run it >>with the defaults, using the latest CXF (2.7.2), Java6. >> >>Obviously I'm a newbie to this code, so if it looks familiar to >anyone, >>I would very much appreciate the pointers. >> >>Thanks, >>AJ >> >> >>Jan 31, 2013 2:55:42 PM org.eclipse.jetty.server.AbstractConnector >doStart >>INFO: Started SelectChannelConnector@localhost:9998 >>Jan 31, 2013 2:55:51 PM org.apache.tika.server.TikaServerCli main >>SEVERE: Can't start >>org.apache.cxf.service.factory.ServiceConstructionException >> at >>org.apache.cxf.jaxrs.JAXRSServerFactoryBean.create(JAXRSServerFactoryBean. >>java:201) >> at >org.apache.tika.server.TikaServerCli.main(TikaServerCli.java:96) >>Caused by: java.lang.NullPointerException >> at >>org.apache.cxf.ws.discovery.listeners.WSDiscoveryServerListener.getService >>QName(WSDiscoveryServerListener.java:89) >> at >>org.apache.cxf.ws.discovery.listeners.WSDiscoveryServerListener.startServe >>r(WSDiscoveryServerListener.java:68) >> at >>org.apache.cxf.bus.managers.ServerLifeCycleManagerImpl.startServer(ServerL >>ifeCycleManagerImpl.java:61) >> at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:146) >> at >>org.apache.cxf.jaxrs.JAXRSServerFactoryBean.create(JAXRSServerFactoryBean. >>java:192) >> ... 1 more
