If these XML files are not read-only, you're really asking for trouble. "XML Database" is a flashy buzzword in the project management magazines. We had this "enlightened" management guy straight out of Dilbert who walked around and told everyone: "Our software is crap. Users are not buying it. What we really need is XML Database" and he almost got his way too.
I would go with a well-designed RDBMS Schema for 99% of the stuff -- it is relatively cheap, standardized, and ready to grow when you are, and it fits right into the J2EE/EJB middle tier. Don't mess with the fragile custom framework, YOU are not in the business of coding database engines, are you?
Greg
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 18, 2002 8:36 PM
To: JDJList
Subject: [jdjlist] Platform Selection - Should I use J2EE+EJB?
Greetings,
Everyone knows Entity Beans are used to represent business objects or
persistent data. They often exist as single records in database. If I am not
using RDBMS, but a database which formed by thousands of xml files with quite
complex tree structure. Moreover, the some applications are going to perform
high volume calculations base on the values stored in the xml files. (e.g. a
calculation may have to access a single field in all xml files for a summarized
result)
Should I go ahead with J2EE+EJB?
-Victor
-----------------------------
Disclaimer: This email (including every file transmitted with it) may contain confidential and privileged information and is solely for the use of the intended recipient(s). Any unauthorised dissemination, distribution or copying of this email is strictly prohibited. Please notify the sender and delete this email immediately if you have received this by mistake. We do not accept liability arising from email transmitted by mistake.
To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm
To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm