Hia,
I've got a question regarding the use of existing XML files within EJB.
Since this is closely related to the "Writing files with EJBs" discussion, I
thought I throw it into the mailing list.
Right now I'm in the process of designing our upcoming system so I'm quite
interested in your opinion on the design decisions which led to my problem.
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.
Now what do you think about the approach outlined above and about the issue
of writing files? Please send your opinions!
.bbr
===========================================================================
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".
