If it is configuration information that is important to the whole
application, I personally would probably read it in once and store it as
session variables. This will also prevent problems if someone modifies the
configuration file while the application is open. If you read the
configuration each time you need the information, you could end up with half
your application variables being before the change and the other half after.
Better to take a snapshot.



-----Original Message-----
From: Philip M. Meier [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 09, 2002 2:08 PM
To: [EMAIL PROTECTED]
Subject: XML-Parsing


Hello List,

I've a problem parsing xml-data! When should I read in the data stored in
the xml-file? At every query the data is needed or once when the application
is started for the first time and at every restart of the container? When
using the second possibility where to store the data inside the application
after the data were read in? The data I want to read in is basicly
configuration data, which is important for the whole application!

Thanks in advance,

Philip

===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST
DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:

 http://archives.java.sun.com/jsp-interest.html
 http://java.sun.com/products/jsp/faq.html
 http://www.esperanto.org.nz/jsp/jspfaq.jsp
 http://www.jguru.com/faq/index.jsp
 http://www.jspinsider.com

===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:

 http://archives.java.sun.com/jsp-interest.html
 http://java.sun.com/products/jsp/faq.html
 http://www.esperanto.org.nz/jsp/jspfaq.jsp
 http://www.jguru.com/faq/index.jsp
 http://www.jspinsider.com

Reply via email to