Andy, If you happen to *know* what file is being parsed (processed), the line number should be sufficient to pin down the problem area. If not, I think we should try to improve the error message .. ;-) . What's the complete stack trace (just for me to get an idea where the problem code might be rootet) ?
Regards Werner Andy Buckley wrote: > Andy Buckley wrote: >> Werner Guttmann wrote: >>> Andy, >>> >>> can you please create a new issue at >>> >>> http://jira.codehaus.org/browse/CASTOR >>> >>> and attach all relevant files, i.e. mapping file, JUnit test case, XML >>> instance, domain objects, etc. I think it's time to have a more detailed >>> look .. ;-). >> Sure, I'll do it asap... there'll just be a short delay while I get a >> minimal test case together. Thanks for the help, by the way :-) > > I've made a minimal test case, but can't reproduce the problem: it must be due > to something other than the class name. I'll keep trying and let you know when > I find out what's going wrong. > > Any suggestions on how I can pin down these exceptions that just return > "null{file: [not available]; line: 38; column: 9}", by the way? > > Andy > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
