Ok that's a bit clearer. You guessed right, War/Ears's are deployments for java app servers, otherwise it's an executable jar.
See if this helps: http://stackoverflow.com/questions/2316445/how-to-use-and-package-a-jar-file-with-my-android-app Specifically the export part. You can use a tool like 7zip or winrar to open a jar file to confirm you jar has xstream in it (maybe class files, or the jar itself). I'm not sure what an android app looks like, but if you can't find xstream in your jar, neither can android. -----Original Message----- From: John [mailto:[email protected]] Sent: Friday, June 08, 2012 6:15 PM To: [email protected] Subject: [xstream-user] Re: Android / Eclipse XStream can't instantiate? Could not find class 'com.thoughtworks.xstream.XStream' Mark Herman <MHerman@...> writes: > > You're going to have to give more specifics on your execution > environment (jar?, war?, within ide?, app > server?, classpath?). It looks like xstream is on the class path at > compile time, but not on the classpath > when your code is running. > Ummm I'm not smart enough to give you all that info first time out (new to Java and Android from .Net). So I'm using Eclipse and trying to run the app on an android virtual machine for now. Not sure jar vs war but everything including my files compile jar so there's my guess. Classpath is what I have read on other posts as causing similiar behavior but I'm having trouble figuring out how to get it on the running classpath. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
