How to Nullifying the Arraylist Object?..

[edwardmraj]

hi all

How to Nullifying the ArrayList Object in JSP .

For Eg.

I declared an ArrayList as below in the Code. Beacause i am going to add an object in to Arraylist using while loop.

-------JSP File Code ---------------
<! ArrayList alTest = new ArrayList(); >

while(condition)
{

<jsp:usebean id="test" class="com.beanclass" scope="request">
<jsp:setproperty name="test" property="strCCNO1" param="textCCNo1"/>
<jsp:setproperty name="test" property="strCCNO2" param="textCCNo2"/>
<jsp:setproperty name="test" property="strCCNO3" param="textCCNo3"/>
</jsp:usebean>

<%
alTest.add(test); //Object of the Bean
%>

<%
request.setAttribute("lis","alTest");
}
%>

<jsp:forward page="servlet" />

---------------------End Code----------------

Thro refreshing the page i'm entering the value in the textboxs and setting the values using methods in <jsp:usebean> . Then i am adding the usebean object to arraylist.

it working fine . no problem.....

Here the Arraylist declared as global<%! Arraylist al= new ArrayList()%>, so what's happening , if more than one user try to access the page and do the same thing, that's also added in the same arraylist object.


Also when i try to declare that AL as in local ie <% Arraylist al= new ArrayList()%> it's every time refresh and create new object. so i con't store that bean objects in loop.



So How to solve this problem???? Is possible to have the arraylist as global and acheive this task? or else

If any one give the solution for this really it will help me lot!!

Thanks in Advance......

EDward

[Belisarius]

You could declare it locally, and then store it in session scope. That will let it survive a reload, but make it individual to each session. You'll just have to check and see if it exists before creating a new one.

*edit* Ah, this is linked to your last post, isn't it? So that rules out using the session object. Well, you're using beans (so I'm not really sure why you can't use the session object), so why don't you shove it in there to keep it's state?

You're going to need to use some sort of session-based mechanism if you want it to survive a reload.