George thanks for the help bu I could not figure out why I am getting
this error when declaring taglib on top of JSP (<%@ taglib prefix="c"
uri="http://java.sun.com/jsp/jstl/core"; %>), I have jstl.jar and
standard.jar in WEB-INF/lib folder.
Error 500--Internal Server Error
java.lang.NoClassDefFoundError:
javax/servlet/jsp/jstl/core/ConditionalTagSupport
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at
weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericCla
ssLoader.java:480)
at
weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoa
der.java:182)
at
weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAware
ClassLoader.java:61)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at
weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoa
der.java:224)
at
weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAware
ClassLoader.java:41)
at
weblogic.servlet.jsp.StandardTagLib.parseTagDD(StandardTagLib.java:1325)
at
weblogic.servlet.jsp.StandardTagLib.parseDD(StandardTagLib.java:1269)
at weblogic.servlet.jsp.StandardTagLib.(StandardTagLib.java:292)
at
weblogic.servlet.jsp.TagLibHelper.loadTagLib(TagLibHelper.java:314)
at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:145)
at
weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5053)
at
weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4891)
at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4737)
at
weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2147)
at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1933)
at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1806)
at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963)
at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106)
at weblogic.servlet.jsp.JspParser.parse(JspParser.java:234)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125)
at
weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:388)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:238)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:188)
at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.jav
a:535)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
java:373)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
java:463)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
java:315)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatche
rImpl.java:322)
at
org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.jav
a:1063)
at
org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProc
essor.java:263)
at
org.apache.struts.action.RequestProcessor.processForwardConfig(RequestPr
ocessor.java:386)
at
org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(Tiles
RequestProcessor.java:318)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:
229)
at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194)
at
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Se
rvletStubImpl.java:1006)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
java:419)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
java:315)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.r
un(WebAppServletContext.java:6718)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
bject.java:321)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServl
etContext.java:3764)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.
java:2644)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Monday, August 07, 2006 1:06 PM
To: user@struts.apache.org
Subject: RE: Browser History by HTTP-REFERER
I would suggest that a servlet filter is a better choice than depending
on the inclusion of a particular tile.
> -----Original Message-----
> From: Thomas Joseph [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 07, 2006 2:36 AM
> To: Struts Users Mailing List
> Subject: Re: Browser History by HTTP-REFERER
>
>
> Try this:
> 1. Include a common JSP page (say like the company logo) in every
> other JSP page (using tiles is perfect) that will check for a user
> object (say username or user credential or something else) in session
> that is created only on Login. 2.
> If the object is not found, redirect to the login page.
>
> There can be more streamlined versions of the same logic.
>
> Thanks and Regards,
> Thomas Joseph
>
> Kott Software Pvt. Ltd. | Vallamattom Estate | M.G.Road |
> Cochin-682015 | India
> www.kottsoftware.com
> --------------------------------------------------------------
> ------------------
> This email (including any attachments) is subject to copyright, the
> information in it is confidential, and it is legally privileged. Use
> of this email or of any information in it other than by the addressee
> is unauthorized and unlawful. If you are not the intended recipient of
> the mail, kindly intimate the author of the mail and delete the same.
> --------------------------------------------------------------
> ------------------
> It doesn't matter how you were, but rather how you are that decides
> your future. A right attitude will get you to Success.
> ----- Original Message -----
> From: Raghuveer
> To: 'Thomas Joseph'
> Cc: user@struts.apache.org
> Sent: Monday, August 07, 2006 10:54 AM
> Subject: RE: Browser History by HTTP-REFERER
>
>
> Yes ,I am trying to restrict users only after login.
> Like banking applications
> -----Original Message-----
> From: Thomas Joseph [mailto:[EMAIL PROTECTED]
> Sent: Saturday, August 05, 2006 9:53 AM
> To: Struts Users Mailing List; [EMAIL PROTECTED]
> Subject: Re: Browser History by HTTP-REFERER
>
>
> Can you please specify in more broad terms, what are you trying to
> do
> (especially with the referrer code)? Are you trying to restrict user
> to
> access pages only after login or something like that?
>
> Thanks and Regards,
> Thomas Joseph
>
> Kott Software Pvt. Ltd. | Vallamattom Estate | M.G.Road |
> Cochin-682015 |
> India
> www.kottsoftware.com
>
> --------------------------------------------------------------
> --------------
> --
> This email (including any attachments) is subject to copyright,
> the
> information in it is confidential, and it is legally privileged. Use
> of this
> email or of any information in it other than by the addressee is
> unauthorized and unlawful. If you are not the intended recipient of
> the
> mail, kindly intimate the author of the mail and delete the same.
>
> --------------------------------------------------------------
> --------------
> --
> It doesn't matter how you were, but rather how you are that
> decides your
> future. A right attitude will get you to Success.
> ----- Original Message -----
> From: Raghuveer
>
>
> In my Struts Web application
> i need to restict the user accessing pages from Browser History.
> When i access any page from Browser History i get
> http-referer=null
>
> So,
> I am checking this by below code on Server side in All my
> execute method
> in
> Struts Action File .
> if(request.getHeader("REFERER")==null){
>
> throw new Exception("Invalid operation");
> }
>
> Is this Correct way of handling ?
>
>
---------------------------------------------------------------------
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]
