Best way to handle XML data

Question

I was hoping someone could tell me if I'm doing something stupid or a much harder way then needed.
I have some data that is stored in an xml file. Probably 150 items (will stay around this number) with less then a dozen attributes per item.
The name of each of these will be loaded into a list on a jsp. When clicking on an item the details will be displayed on the page below it.
Right now my plan is to:
!. read the file in on application startup and store the items in a collection of beans in the session, or maybe at application scope.
2. Then in the jsp use AJAX and pass the items ID to a servlet.
3. The servlet pulls the collection out of session or application scope and find the correct item and sends it back as xml.
4. Then either parse the xml or use JSON to convert it to an object.
5. Populate the fields on the jsp.
I'm just worried that I'm doing something incredibly inefficient or stupid.
With only 150 items would I be better served just loading all the items into a multi dimensional javascript array on loading the page and just get rid of AJAX all together?

Answer 1

Comments are shown below preceeded by *******:
I was hoping someone could tell me if I'm doing something stupid or a much harder way then needed.
**** Yes, I think its much harder than it needs to be.
I have some data that is stored in an xml file. Probably 150 items (will stay around this number) with less then a dozen attributes per item.
****** Normally, such data is stored in a database table (no xml involved). However, you can store them in a file if you want.
****** If you store it in a file, I suggest not using xml. Its an advanced topic. I suggest using a tab delimited file (you can use a text editor to create it).
The name of each of these will be loaded into a list on a jsp. When clicking on an item the details will be displayed on the page below it.
***** ok, so far
Right now my plan is to:
!. read the file in on application startup and store the items in a collection of beans in the session, or maybe at application scope.
****** Your options are:
***** request scope: need to read the file each time the user needs the data. Not efficient.
****** session scope: data lasts as long as user is logged on. Good idea.
****** application scope: data lasts after the user logs off. Bad idea. takes up memory permidently. Must remove it from application scope when last user logs off.
****** Store it in a database: best idea, but takes time to learn.
2. Then in the jsp use AJAX and pass the items ID to a servlet.
****** Dont use AJAX, its an advanced topic. Learn JSP and XHTML first.
3. The servlet pulls the collection out of session or application scope and find the correct item and sends it back as xml.
****** send it back via request.setAttribute() and read it on the JSP via <useBean>. xml is not the way to go.
4. Then either parse the xml or use JSON to convert it to an object.
****** dont use xml.
5. Populate the fields on the jsp.
***** Yes. Note JSP should not contain business logic. Business logic should be done in a servlet. The servlet should put data in request scope
for the JSP to populate itself. The data objects put in request scope should contain just data, no business logic functionality.
I'm just worried that I'm doing something incredibly inefficient or stupid.
***** Best way to learn is to try stuff out and make your next project better than the previous.
With only 150 items would I be better served just loading all the items into a multi dimensional javascript array on loading the page and just get rid of AJAX all together?
******** Javascript is an advanced topic. Its main purpose on the JSP is to handle simple onclick events from html tags and to do some basic client side validation.
***** I believe a book on JSP would be very helpful.