Its caught always immediately after its thrown. The rough logic is:
// we have some system id at this point
URL urlTest;
try
{
urlTest.set(systemId);
// If no exception, its a URL
}
catch(const MalformedURLException&)
{
// We got an exception, so assume its a local file
}
All of the uses are in this form. So if you search for all places where
MalformedURLException is being caught, those are all the places where this
could happen.
----------------------------------------
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
[EMAIL PROTECTED]
Michael Burbidge <[EMAIL PROTECTED]> on 01/10/2000 11:58:36 AM
Please respond to [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
cc:
Subject: Re: DOCTYPE specification...
I took 1.0.1 and ported it to Machintosh. As a related issue, it would be
great to get my changes into the code base. Besides writing a very
brain-dead transcoder, it handles only roman, my changes are very simple
and
straight forward. I know someone port it to Mac before, but the changes
didn't get integrated into the code base. In addition they relied on ICU,
which is from IBM. IBM's license isn't as clear as Apache's. It's not clear
to me that ICU is open source.
If you could tell me where you expect the exception to be caught I could
look at my stack right before the exception is thrown...
Thanks,
Mike-
> From: [EMAIL PROTECTED]
> Reply-To: [EMAIL PROTECTED]
> Date: Mon, 10 Jan 2000 12:23:20 -0700
> To: [EMAIL PROTECTED]
> Subject: Re: DOCTYPE specification...
>
>
>
>
> What version of the code are you using and what OS are you on? We've had
> some trouble with some systems not correctly catching exceptions and
> letting them leak out. The MalformedURLException is expected in that
case,
> but it should never make it out. We've had an issue on Solaris where they
> leaked out because of a system bug. And we had an issue with VC++ 6.0 not
> catching them in earlier (2.x) releases, and we had to make the base
> XMLException class copy constructor public in order to make it work
> correctly.
>
> Are you in either of those scenarios?
>
> ----------------------------------------
> Dean Roddey
> Software Weenie
> IBM Center for Java Technology - Silicon Valley
> [EMAIL PROTECTED]
>
>
>
> Michael Burbidge <[EMAIL PROTECTED]> on 01/10/2000 09:26:52 AM
>
> Please respond to [EMAIL PROTECTED]
>
> To: <[EMAIL PROTECTED]>
> cc:
> Subject: DOCTYPE specification...
>
>
>
> I have the following DOCTYPE specification:
>
> <!DOCTYPE film-guide SYSTEM "film-guide.dtd">
>
> According to my understanding, this is a valid DOCTYPE specification, yet
> I'm failing when parsing the URL. The code throws a
> XML4CExcepts::URL_MalformedURL exception. When I traced through the code
I
> found that the method URL::findType was looking for a colon in the first
8
> characters. If it doesn't find one then it throws the exception.
>
> What's up? Why can't I specify a local file as in the above DOCTYPE?
>
> Thanks,
> Mike-
>
>
>
>
>
