Regards,
Pankaj Patil
Originally posted by Ben Souther:
I believe the main intent of useBean, as well as EL and JSTL, is to provide a higher a level abstraction that allows JSP developers to move from scriptlets to scriptless JSPs.
In this and the two other threads that you started today, you're using the useBean tag but also mixing in scriptlet code that undermines or clashes with what useBean is trying to do, and then asking if the problem is a bug in Tomcat.
If you want to implement lower level Java coding in your JSPs, why not forgo the useBean tag altogether and go with 100% scriptlet code?
Better yet, move all of your complicated Java code into servlets and beans.
Then use let the JSPs handle nothing but the simple view tasks.
Duplicate id�s found in the same translation unit shall result in a fatal translation error.
Originally posted by Rohit Bhagwat:
I am not doing anything special.
I am just trying out the example given out by jsp specification. And I guess this a geniune doubt. You can visit the specification link which you have.
They have given the similar example and said that this is allowed and valid.
The same I tried out in tomcat and it didnt worked.
I guess there is no point in getting angry !!
And ofcourse this just tests how much thorough we are with the useBean tag.
Originally posted by Bear Bibeault:
Straight from the JSP Specification (section JSP.5.1):
Duplicate id�s found in the same translation unit shall result in a fatal translation error.
So regardless of what weird scoping contortions you place in the page, it is illegal to use the same id for more than one useBean action.
Originally posted by Rohit Bhagwat:
Bear. I appologize for using the word "Tomcat bug". Henceforth I will take care that I dont use such words.
This is the rule of jsp however dont you think that this violates the basic fundamentals of java that the life of a variable is limited to the scope/block in which it is declared ?.
This is my last post for this topic and I wont do any posts on this topic further as I guess people have started hateing me.
<%
// the variable customer is out of scope now but
// the object is still valid (and accessible via pageContext)
%>
Originally posted by Rohit Bhagwat:
This is my last post for this topic and I wont do any posts on this topic further as I guess people have started hateing me.
The future is here. It's just not evenly distributed yet. - William Gibson
Sonny Gill LinkedIn
Tweets
We're being followed by intergalactic spies! Quick! Take this tiny ad!
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
|