Raj-
James Mitchell suggested you force the include from your action via
RequestDispatcher call
Did you try that?
Are you able to tracert to the url?
More importantly what do the tomcat logs say when you invoke your
<bean:include
Martin-
----- Original Message -----
From: "Raj Tilak" <[EMAIL PROTECTED]>
To: <user@struts.apache.org>
Sent: Tuesday, May 24, 2005 8:21 PM
Subject: bean:include on public domain
<bean:include id="absContent" page="<%=valueUrl%>" /><bean:write
name="absContent" filter="false" />
this works locally but not when deployed on public domain, would it be a
network issue?
jsp:include works fine everywhere
Please let me know if anyone has encountered it.
since we used bean:include from the begining, could easily replace with
jsp:include
but it had some other side-effects,
so lemme know, I had asked this question earlier, but didn't get a
concrete answer.
thanks
Panchasheel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
