B E N J A M I N | BROLL wrote:
>
> In our system we will have to make several settings available to a client
> (possibly an EJB, JSP page, Servlet, ...). Now we decided to store these
> settings in XML files, which should be read by a stateless session bean and
> thus be available through several business methods of the bean.
>
> But as you can see this directly involves the use of the file system to
> retrieve and parse the documents. I thought about building a utility class
> (put into the system directory of the App Server) which parses the documents
> from the file system and which in turn offers them to the stateless session
> bean.
>
> In my opinion this would be a quite reasonable approach and I would build
> the system this way because it is just a read-only utility class which has
> to serve the XML documents and it does not involve changing the files.
>
> _But_ there is another task the system should accomplish. Since the settings
> should be remotely administratable, ie. also storing changed documents, the
> utility would no longer be read-only but would as well create output to the
> file system.
B E N J A M I N,
Those Utility classes have already been written for you. They are called a DBMS.
Much better performance than opening, reading and closing files - automatic
caching, automatic synchronisation of updates, etc etc.
Ian McCallion
Alexis Systems Limited
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
