I was finally able to capture the server when the issue presented itself, and it seems to have a broader effect than just the page in question.
The XPage I originally discussed is referenced on almost every site page, so I suppose that is why it displays the issues mos prevalently.
As soon as "the issue" (quoted, 'cause I have no idea where it's roots are!) presents itself, none of the XPages-based architecture on the site works as it should.
Submit buttons cease to do anything, the aforementioned errors are continually logged on the server console, and "Error 500" errors abound.
The only thing that seems to do the trick is to restart HTTP.
Suddenly, everything returns to absolute normal and the site works perfectly.
I took your advice Mark, and commented out absolutely all logic, and that had little effect.
I even plonked a return right at the beginning, and that did nothing as well.
I have reduced the page to the following code:
<?xml version="1.0" encoding="UTF-8"?>
<xp:view xmlns:xp="http://www.ibm.com/xsp/core" rendered="false" createForm="false">
<xp:this.afterRenderResponse><![CDATA[#{javascript:
try{
var exCon = facesContext.getExternalContext();
var writer = facesContext.getResponseWriter();
var response = exCon.getResponse();
writer.endDocument();
facesContext.responseComplete();
}catch(e){
writer.endDocument();
facesContext.responseComplete();
print("Page Error: "+e.toString);
return;
}
}]]></xp:this.afterRenderResponse>
</xp:view>
... and when the issue starts, Domino actually renders this page (I never see the results of the 'print' statement on the server console)!
I took a look at the source, and the following was presented back:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta HTTP-EQUIV="REFRESH" CONTENT="0; URL=javascript:void( window.top.location = 'http://www.abc.com.au' )">
<script language="JavaScript" type="text/javascript">
<!--
document._domino_target = "_self";
function _doClick(v, o, t) {
var returnValue = false;
var url="/web/shop.nsf?XPage&Click=" + v;
if (o.href != null) {
o.href = url;
returnValue = true;
} else {
if (t == null)
t = document._domino_target;
window.open(url, t);
}
return returnValue;
}
// -->
</script>
</head>
<body text="#000000" bgcolor="#FFFFFF">
<form action=""></form>
</body>
</html>
I am a little lost here - Why would Domino start rendering a page that clearly is defined to prevent such a thing?
I'm sure there's something happening out in left field that I am missing, but I honestly don't know where to start looking with this one.
It seems to be more server based, and less related to the page itself (given the necessary steps to resolve).
If anyone has some insight, I'd sure be grateful!
Cheers, T.