I know I have to be missing the obvious here but can't seem to put my finger on it. I have an application that uses the castor jar from the castor folks. It works perfectly on the development system. When I place all the jars and executable code on any other system, I get:
I have checked the classpath and the jar containing the MappingException class is definitely in the classpath. I have also put it in the system path - grasping at straws. I have run this with the -classpath switch pointing to the current directory where all the code resides. All generate the same error.
What am I missing here? [ November 01, 2004: Message edited by: Monkey Boy ]
Can we try setting the classpath to the current location?
like set classpath=%classpath%;. - with a dot at the end.
Joined: Nov 01, 2004
Thanks for all the help! I updated my profile.
Ramaswamy, I did have my classpath setup as you suggest - no luck there. Tried all of Pauls suggestions as well, still no luck.
One thing I did find in these forums was a reference to using the .class extension from the command line -- not allowed and caused a similar error as the one I have. I am not doing that but I did setup the jar file to run a specific class by default so I could use the -jar switch (java -jar myJar) instead of having it be the 'standard' command (java com.xxx.yyy.zzz.myClass). It made the command line a little cleaner and easier to use. That thread made me think this was a problem so I tried it with the longer 'standard' command and the application ran perfectly.
While this works on the development system, it fails on all other systems. Any ideas as to why that is?
[ November 02, 2004: Message edited by: Chris Michaels ] [ November 02, 2004: Message edited by: Chris Michaels ]