Hello everybody
We have a project mixing JBoss Seam with GWT and we couldn't find why
it doesn't work in Google Chrome. The exception thrown there is:
Uncaught TypeError: Object #<a Document> has no method 'write'
It is on the third line here:
function computeScriptBase(){
var thisScript, markerId = $intern_8, markerScript;
$doc.write($intern_9 + markerId + $intern_10);
We're pretty sure it's not our code. But what is bothering us the
most, it works OK when the page is plain HTML like this:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://
www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" >
<html xmlns="http://www.w3.org/1999/xhtml";>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8" /
>
<meta name="gwt:property" content="locale=en" />
<title>Comasutra</title>
<link rel="stylesheet" type="text/css" href="style.css"
media="screen" />
<script type="text/javascript" language="javascript" src="cms/
cms.nocache.js"></script>
</head>
<body>
<iframe src="javascript:''" id="__gwt_historyFrame" tabIndex="-1"
style="position:absolute;width:0;height:0;border:0"></iframe>
<div class="top">
</div>
<div class="main">
<h1>Main page</h1>
<div>
<h2>Articles</h2>
<div id="cms-c1" class="article-list"></div>
</div>
</div>
</body>
</html>
If I generate THE SAME content with JSF (xhtml, Facelet, result of the
complete Seam request), it doesn't work. The only difference I can see
is in headers - these are the headers for plain HTML (displayed in
Firefox by Web Developer extension):
Server: Apache-Coyote/1.1
X-Powered-By: Servlet 2.5; JBoss-5.0/JBossWeb-2.1
Accept-Ranges: bytes
Etag: W/"823-1249470776734"
Last-Modified: Wed, 05 Aug 2009 11:12:56 GMT
Content-Type: text/html
Content-Length: 823
Date: Wed, 05 Aug 2009 11:23:50 GMT
200 OK
These are the headers after JSF request:
Server: Apache-Coyote/1.1
X-Powered-By: Servlet 2.5; JBoss-5.0/JBossWeb-2.1, JSF/1.2
Content-Type: text/html;charset=UTF-8
Content-Length: 823
Date: Wed, 05 Aug 2009 11:23:38 GMT
200 OK
We use JBoss Seam 2.2.0.CR1, JBoss AS 5.1.0.GA, GWT 1.7, ... well,
that's it. Windows XP SP 3, Google Chrome 2.0.172.39.
Is there any way how we can avoid this problem?
Thank you very much
Virgo
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
