Hi, Shane, Thanks for your information.
This happens persistently on some pages when they are accessed normally but not on others. But there are no fundamental difference between these pages in this reagrd;-) Do you where is the ComponentContext set at the first place? Jianbo -----Original Message----- From: Bailey, Shane C. [mailto:[EMAIL PROTECTED] Sent: 12 August 2003 19:01 To: 'Struts Users Mailing List' Subject: RE: Error - tag useAttribute : no tiles context found. Here is the source code producing your problem: ComponentContext compContext = (ComponentContext)pageContext.getAttribute( ComponentConstants.COMPONENT_CONTEXT, pageContext.REQUEST_SCOPE); if( compContext == null ) throw new JspException ( "Error - tag useAttribute : no tiles context found." ); If this happens intermittently then maybe it is because a user is hitting the back button or a cached page or something like that which would cause the request to be missing the component context. Just a guess. -----Original Message----- From: Jianbo Mao [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 12, 2003 1:38 PM To: [EMAIL PROTECTED] Subject: Error - tag useAttribute : no tiles context found. I am using tiles:useAttribute tag to define a variable in request scope for the remaining page to reference like this: <tiles:useAttribute name="menuon" scope="request" ignore='true'/> The runtime complains about tiles context not found as follow: javax.servlet.jsp.JspException: Error - tag useAttribute : no tiles context found. at org.apache.struts.taglib.tiles.UseAttributeTag.doStartTag(UseAttributeTag.ja va:219) at jsp_servlet._common._layouts._classiclayout._jspService(_classiclayout.java: 85) at weblogic.servlet.jsp.JspBase.service(JspBase.java:27) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java :120) at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp l.java:915) at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp l.java:879) at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext Manager.java:269) at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365) at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129) The application works fine with intended functionalities, but this exception fills my log file all over. Any idea what could cause this? Jianbo --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
