I am not sure what the exact problem is, but it has to do with the way that browser_debug.js gets processed. One would think that this file would only get pulled in when the head tag attribute debug=true, but one would be wrong in that situation.
The "correct" way to fix this bug is to supply your own template for the head tag which will make the dojo attribute debugAtAllCosts respect the head debug flag.
To do this,
1. create a file named head.ftl in your simple templates directory. ( ie $classpath/template/simple/head.ftl)
2. Paste this text into it:
<script language="JavaScript" type="text/javascript">
// Dojo configuration
djConfig = {
baseRelativePath: "<@s.url includeParams='none' value='/struts/dojo' includeParams="none" encode='false'/>",
isDebug: ${parameters.debug?default(false)},
bindEncoding: "${parameters.encoding}",
debugAtAllCosts: ${parameters.debug?default(false)}, // not needed, but allows the Venkman debugger to work with the includes
};
</script>
<script language="JavaScript" type="text/javascript"
src="<@s.url includeParams='none' value='/struts/dojo/dojo.js' includeParams="none" encode='false'/>"></script>
<script language="JavaScript" type="text/javascript"
src="<@s.url includeParams='none' value='/struts/simple/dojoRequire.js' includeParams="none" encode='false'/>"></script>
3. Refresh your page, the bug should be gone as long as the struts head tag does not have debug set to true.
Of course, you will have to turn debugging on to get firebug happy, but I believe that that is an acceptable compromise.
[Message sent by forum member 'summerspittman' (summerspittman)]
http://forums.java.net/jive/thread.jspa?messageID=288767