EL Messages on JSP page - jsp-tags

i have some server side validations and am displaying validation messages in JSP using EL like
${requestScope.validatemessage} where validatemessage is the message i set in Java file
its working fine
But the problem the message is still displaying even if i refresh the page
how to disappear this message on refresh?
plz let me know asap
thanks in advance,
anu

Is your browser caching the page? Try Ctrl-F5.
Are you running this on Tomcat? Try shutting down Tomcat and deleting its /work drectory.
That will get rid of Tomcat's cached copy.

Related

error 500 http web server: command not handled exception

I think this topic a lot of ppl post it already. I also look for lot of thread in stack overflow and some ibm page. They do give some comment of how to solve this problem. But i still facing the same problem, it still give this error.
Case start :
Actually one of my customer, they have facing this error during running on webpages and also notes ~
error 500 http web server: command not handled exception
Action taken but not solve:
The user id signing/creating the XPages allowed to run XPages in the
server document?
Do project clean, build automatically on designer
Do testing on creating new xpages page with simple lable " hello world" , this one can run successfully only.
Try to reload the http server by
tell http quit
load http
After do this the problem still same give the same error. May i know got any other way to solve it?
"Unresolved compilation errors: java.lang.String" points to a failed install as here. A class in java.lang or java.util should always be resolved. Ensure all services and any processes for Notes / Domino are stopped before the relevant install, jar files can get locked once used. Xpages can't load, Error 500; java.util cannot be resolved
Switch on "Display XPage runtime error page" in application's XSP Properties then you'll see a detailed error message which probably will lead you to the issue:
I frequently get this error when there is a mismatch/problem with access rights or the user login has expired and the app/database doesn't redirect to the login page. I suggest you double check the security basics first. (Might also explain why the app works locally, but not on the server).

Meteor error message client-side

I'm using the framework Meteor (Node.js).
I get this error message in my web browser when my project page is loaded:
The connection to ws://localhost:3000/sockjs/622/u2zaukpp/websocket was interrupted while the page was loading.
Why is it occuring?
It happens every single time you reload the page or it gets reloaded by the server.
Basically the page is constantly receiving data from the server (collections data, methods, or simply a ping). Since it is constantly open and Meteor forces a reload on code change (or you did force one by reloading the page), your browser freaks out and shows you this error.
It can also happen if the Meteor process is killed.
Thus, expect to see this error a lot during development, you don't have to worry about it.

How do you figure out where com.ibm.xsp.exception.EvaluationExceptionEx happens?

HTTP JVM: com.ibm.xsp.exception.EvaluationExceptionEx: Error while executing JavaScript action expression
We are using beans and expression language on our XPage and we get the above error from time to time, can anyone tell us if there is an easy way to find out which page is causing this and more importantly where in code? We are having to use trial and error methods and having to resort to remove code from page in order to find out where the problem is, which is not the most efficient way to do this.
Please check the XPages log files in the IBM_Technical_Support folder in the data directory in order to get more details on the error such as what xpage gave the error and specific details on the error.
If you can not get to the XPages log files on the server directly, then use XPages Log File Reader from OpenNTF to get easy access to the log files from a browser.
Like Fredrik Norling I will also recommend the XPages OpenLog Logger by Paul Withers as a solution to generating error log files automatically.
I would implement Paul Withers XPages Openlog implementation with the phase listening bean and error page.
That will help you find the problem. And if you deploy it as an osgi then you only have to set the error page, some xsp properties and add the bean to the faces config file on each database to point it to a central openlog error database.
http://www.openntf.org/Internal/home.nsf/project.xsp?action=openDocument&name=XPages%20OpenLog%20Logger
http://www.openntf.org/Internal/home.nsf/project.xsp?action=openDocument&name=OpenLog

JSF CommandLink with get request

Currently I have serious problems with my webapp, because it has strange behavior behind a web proxy ISA Server 2006. I found the problem was because I was using h:links to call some pages and ISA makes cache from that. I change the h:link to h:commandLink but the cache is the same. Doing debug of the request with firebug I find this:
POST currentPage
GET nextPage
The first is the page where i made click and the second one is the page I want to go. 1. I don't understand why there are 2 request? 2. I dont know why the command is sending a GET request?
Can anybody help me.... ????

How can i make errorpages in jsf?

Everytime something gets wrong .. i got to see this.
How can i make a simple Errorpage with stacktrace in jsf ?
If you use Facelets (which is almost mandatory if you want to develop JSF webapps), an error page is automatically created. You can see an example here.
More generally, you can customize your web.xml in order to redirect the user when an error occurs.

Resources