This one time, at band camp, Dean Hiller said:
DH>I am trying to debug an Exception I am getting.
DH>
DH>I keep getting unknown source from org.exolab.castor.xml.UnmarshalHandler which
means my clsss files were not compiled with the debug option on. I look at the
src/build.xml file and debug is turned on in every call to javac. I ran the ant
target jar, and used the jars from the dist directory. This has to be some kind of
stupid mistake of mine.
DH>
DH>Can someone please tell me how to get debug on so it says the line number I am
getting the exception from?
DH>
DH>Or possibly could a developer put a line inUnmarshalHandler that throws a
RuntimeException and see if it prints the line of the exception for that specific
class?? I would just like to know if you have the same problem.
Dean,
In the Ant build descriptor, the jar target depends upon the main-opt
target which does not enable the debug tables. If you just execute
the build script with no arguments, the source that is generated in
build/classes does have the debug tables enabled. You could just jar it
up or simply point to $CASTOR_HOME/build/classes in your CLASSPATH.
Incidentally, it's quite easy to place statements in the Castor code
base yourself and then recompile it. Ahh, the beauty of Open Source!
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
