Danger, Danger, Danger Will Robinson! > 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)
At a minimum, I hope your business logic is separated from accessing these thousands of XML files: Order.java calcuateTax(); get attribute a from file 101 get attribute x from file 109 updateCustomer(); get state element from file 502 I hope the logic is not like the above. At a minimum, I would decouple access to those XML files as much as possible from the rest of your code. I hope there is a data access layer rather than direct data access details sprinkled throughout. J2EE ( with or without EJB ) with a relational backend persistence is going to work better for you. High volume? Are these read only? Are they cached? Also, if you choose to adopt J2EE, take a look at the J2EE Core Patterns book for guidance on structure. Book Link: http://makeashorterlink.com/?U5F5212E1 Regards, Dave --- [EMAIL PROTECTED] wrote: > 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 __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm
