|
From: davidbeers <db...@gm...> - 2007-12-19 13:36:37
|
Thanks for the quick reply, Leif! I think I'm going to like using this software. :) There's no classpath specified in the manifest, but I'm glad to know about this for the future. The class file that isn't being found is the main class: "WrapperSimpleApp: Unable to locate the class com.pikesoft.TileServer: java.lang.ClassNotFoundException: com.pikesoft.TileServer" -David Leif Mortenson-2 wrote: > > > Does your jar's manifest file specify a classpath like the following? > Class-Path: log4j.jar > > If so, it is necessary to include all of those files in the classpath as > well. > > The next question is what is the file class that is not being found? > > Cheers, > Leif > > davidbeers wrote: >> I have an executable jar with a main class whose name I've verified from >> the >> manifest (I built the jar myself). Wrapper seems unable to execute it, >> issuing a ClassNotFoundException. I've looked my wrapper classpath over >> and >> can't see what the problem could be. The salient bits of my wrapper.conf >> look like this: >> >> wrapper.java.classpath.1=../lib/wrapper.jar >> wrapper.java.classpath.2=../lib/tileserver.jar >> >> wrapper.java.library.path.1=../lib >> >> wrapper.app.parameter.1=com.pikesoft.TileServer >> >> tileserver.jar is my executable jar, it's located in the lib directory as >> described, and com.pikesoft.TileServer is the fully qualified name of its >> main class. From the FAQ it seems like this is all as it should be, but >> I'm >> obviously missing something! > -- View this message in context: http://www.nabble.com/Executable-jar-ClassNotFoundException-tp14409676p14416910.html Sent from the Java Service Wrapper mailing list archive at Nabble.com. |