Dears, my question is simple: Am I right?
I'm brain new to the Avalon stuff and the like. I didn't yet downloaded the whole bunch of docs, but I read the "Developing With Apache Avalon" pages ( http://avalon.apache.org/developing/index.html ) as well as some FAQs. From these "Developing" pages it seems that 'data' is something has few to do with Avalon. It seems that Components supply the enterprise/business methods, which may eventually accept/result in data. As a result, every effort in maintain data instances unique would be from the user application. It seems to me that Avalon has no support for primary-key/data bindings, in example. Also, I found few words about transactional support in Avalon. It seems to me that it is not possible to enforce a Commit-All-Or-Rollback-All design to Avalon Components, at least with the current design of connections and components relationships. I'm asking this because I have to face the design of an application which strongly relies on a db as a data repository. I was first tempted to use a J2EE container system (OpenEJB) to develop it, next I 'discovered' the Avalon Project and I was wondering about the limits of both frameworks. Thank you, -- Giampaolo Tomassoni --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
