Ok, it definitely seems the docType issue is Mac JDK5 specific. I downloaded SE6 and ran the exact same code and this error is fixed:

JSE5:

<!DOCTYPE HTML PUBLIC "http://www.w3.org/TR/xhtml1/DTD/xhtml1- strict.dtd""-//W3C//DTD XHTML 1.0 Strict//EN">
<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>My text</body>
</html>

JSE6:

<!DOCTYPE html PUBLIC "http://www.w3.org/TR/xhtml1/DTD/xhtml1- strict.dtd" "-//W3C//DTD XHTML 1.0 Strict//EN">
<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>My text</body>
</html>

However, we STILL have the same META tag issue. It's bad enough that this unspecified tag is getting added somewhere along the path without my consent - but it's unbelievable to me that javax packages would actually output xml that is not well formed by default! As it turns out this tag is probably something i would have added anyway, but it's useless if it doesn't validate. Any idea where this tag may be getting added?

-Elliot

On 9 Mar 2008, at 15:10, Elliot Long wrote:

On 9 Mar 2008, at 04:09, Rob Heittman wrote:

Well, I'm stumped.

The attached file cleanly reproduces the malformed doctype breakage on my OS X 10.4, Java 5 MacBook, without any dependencies loaded, just plain old Java. But I can't find any mention of this bug via Google. This can't be the first time anybody's noticed ... ? I'd check on something other than my Mac, but the power is out here due to windstorms and about all I can do is email and web via Bluetooth to my cell =)


Hi Rob.

Thanks for looking into this - I'm glad to see I'm not the only one! I was also pretty surprised that something like this would be occurring (with no results to speak of on google), but even more so that it could be with TRAX rather than RESTlets. Incidentally, I'm using a MacBook too (10.5, jdk5), and since the DocumentBuilder is part of the JDK which apple develops, perhaps it's a platform- specific issue? Any Windows/Linux users out there who can reproduce this? Also could be a good excuse for me to try out the developer preview of JavaSE6 to see if there's any change...

-Elliot















Reply via email to