Hi Stephen,
I'm not sure I'd classify it as a feature! :-)
This issue was actually reported a couple months back and I thought we had it all cleared up for the 0.9.6 release. I was not able to reproduce the problem on my Win XP box. So I'm guessing our logic for dealing with paths still has a problem under Unix/Linux platforms.
Can you open up a bug on this for tracking purposes. I currently don't have access to a linux machine, but I'll try and track down the problem or have Bruce look into it.
Thanks,
--Keith
Stephen Bash wrote:
This may be a "bug or feature" question... I tried load an XML mapping file from a full pathname, and got a FileNotFoundException... If I wrap the filename inside of an InputSource, it works... The FNFE is correct in that the FNFE reports the filename as (full-path)/(full-path)/filename.
I traced through the code, and the line throwing the exception is 257 of DTDResolver if that helps at all.
Is this a case where loadMapping( String ) should just be discouraged in favor of loadMapping( InputSource ), or is there some greater issue here?
Thanks for any help!
Stephen
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-user
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-user
