cleo in jetty without maven

[Siva]

Hi
I am new to java and maven.
Though I could run cleo successfully with maven installed in my local setup, in production how do I take the war file and deploy it within jetty?

Thanks,
Siva

[Siva]

To be more specific, when I run jetty9 with a maven generated cleo-primer-1.0.war (as in the example without any config changes), I get the following trace when I try to
post nasdaq-google.xml elements:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><exception><class>java.lang.NullPointerException</class><stack-trace>java.lang.NullPointerException
    at cleo.primer.ElementDAO.getElementStore(ElementDAO.java:63)
    at cleo.primer.ElementDAO.insertElement(ElementDAO.java:124)
    at cleo.primer.rest.resources.ElementsResource.addElement(ElementsResource.java:101)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
    at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)

Please let me know if I am missing anything obvious.

Thanks,
Siva

[Brian Tingle]

I observed the same behavior in tomcat.

I fixed it by setting the java properties required by cleo using this on the java command used to start tomcat

-Dcleo.instance.name=Company -Dcleo.instance.type=cleo.primer.GenericTypeaheadInstance -Dcleo.instance.conf=/the/full/absolute/path/to/cleo-primer/src/main/resources/config/generic-typeahead

I did this by setting JAVA_OPTS in bin/setenv.sh in tomcat