Win a copy of Pro Spring MVC with WebFlux: Web Development in Spring Framework 5 and Spring Boot 2 this week in the Spring forum!

Devi Taruni

Greenhorn
+ Follow
since Sep 03, 2008
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Devi Taruni

Hello,

I wanted to know are there any cases where when you click on browser back/forward button it makes a call to the server? I am really surprised to see the page submission happening whenever browser back/forward button is hit in our application.

I am working on an application which has been implemented in Struts(DispatchAction concept), Tiles. As far as my knowledge is concerned, browser buttons never make a call to the server, instead all the visited pages are just pulled from cache and displayed but my application is behaving quite opposite way, it makes a call to the server on every hit on browser-back/forward buttons and results in an inconsistent behaviour.
After searching for quite sometime, i found these lines :
Another issue is caching pages when browsers navigate backwards --
browsers are more likely to silently re-submit a form request with a GET method than with a POST request.

source:
http://lists.nyphp.org/pipermail/talk/2003-February/002327.html

Do you think the problem is with the request submission or in usuage of Struts Dispatch Action?

Can someone help?
TIA
12 years ago
JSP
Hello Bear,

I apologize for my posting which you meant was inappropriate. May be it was an oversight not mentioning which html tag I was refering to. Thanks for correcting.
Hello Bear Bibeault,
I was actually talking about the attribute 'disabled' from struts-html tag library.
eg:
<html:text property="xProperty" disabled="${myBean.disabled}" />


where disabled attribute takes an expression which should result in a boolean value. Hope this makes things clear.
[Response removed. Please see your private messages.]
[ September 19, 2008: Message edited by: Bear Bibeault ]
12 years ago
JSP
Try using "disabled" attribute, which takes boolean value in the respective html tag.

try searching for examples on this, you will get many.
[ September 19, 2008: Message edited by: Bear Bibeault ]
You are welcome
12 years ago
JSP
Hey did you copy the tld as it is??
I could see the problem with your tld file to be

<rtexprevalue>true</rtexprevalue>, whereas the available tag is <rtexprvalue>

check the spelling!!!
12 years ago
JSP
try this :

<c:out value= "${pageContext.request.String1}"/>
12 years ago
JSP
Don't you think the requirement is too odd to imagine.
What makes me laugh is all tabs(1-5) data are validated in the 6th tab and you carry the fields data in session without any confirmation that it is the valid one. Oh man you are wasting your resources unnecessarily. My suggestion is dont risk your resources unless you are sure about its authenticity.
I suggest you to try this one -
While in tab1 allow the user to enter the data in your fields once he is to move on tab2, validate the data entered in tab1 and incase of errors display them in the same page to which the fields belongs, just make sure that the user is allowed to move onto next tab only when he is done everything right in the current tab.

Hope you understand what i am trying to explain. :thumb:
12 years ago
JSP
How do you think the jsp compiler will identify the variable declared in your javascript???

In your js file :

var myString = document.findElementByID("TxBox1").value;
document.findElementByID("TxBox2").value = myString;

is this what you are looking for??
12 years ago
A page directive session attribute's default value is true, now.. it means the predefined variable session should be bound to the existing session if one exists, otherwise a new session should be created and bound to it.

I think this must depend on the application server. I have JSPs running on Jetty 6.1 where no session is created if I set <@page session="false">.



I totally disagree with your statement because the session is created no matter whichever application server you use.
with <@page session="false"> you just mean that no sessions will be used, and attempts to access the variable session will result in errors.

You can't do this...

<% if (something) {
session.setAttribute(...); // use session here
} else {
// code that does NOT use session here
}
%>
12 years ago
JSP