Hi Jaco, Sorry for not having had the opportunity for an earlier response. Here is my answer to your questions.
It is not our aim is not rely on a particular way of configuration in our core components at all. Instead you work with classes and set the properties from your code in any way you like. The XML config-file is one way that is used by the examples. This is done by the class XMLConfiguration class which is supplied with the Empire-db core but there is no need to use it at all and it is never used internally either. The XMLConfiguration class uses simple reflection and it is small and lean. At the moment we're not using Spring and we have no examples or guidelines on how to use it. As all important classes can be instantiated and extended by the application I don’t see much need for dependency injection. The problem I see with Spring is, that it could break our paradigm of "String free coding" and "compile-time-safety". So if you want to use Spring with Empire-db you may need to write your own extensions that allow dependency injection where needed. Second, we're not doing dealing with transactions - other than those offered by the underlying DBMS - at all. Again this is because we want to keep it small and simple. An application which needs cross database transactions or similar must implement its own logic. But maybe you want to convince us that supporting a transaction manager would be a useful improvement by giving us a useful scenario. Best regards Rainer Jaco van Tonder wrote: > re: Spring Configuration > > Hello guys, > > I am busy investigating Empire-DB as a replacement for Hibernate in our > organization (so far so good). :) I have a couple of questions though. > > I put together a config class that does not make use of a config file > (looked at the examples, and just used the defaults), but instead is > wired using Spring (simple setter injection). I could not find any > examples that uses this method so I am not sure if this is the best way > to do it. I looked at the source code and could not find any other way > of configuring Empire-DB that is not XML based. > > Q: Is there a recommended way of configuring Empire-DB using Spring? > > I read that there is no built-in transaction support. Obviously this is > important for databases. ☺ > > Q: What transaction managers are known to work well with Empire-DB? > JOTM, etc etc etc? Are there any examples of this available somewhere? > > I am willing to document any of the answers (ie spring configuration, > transaction manager examples) on the project wiki. > > Thank you in advance. > > ---Jaco > > ________________________________________ > Attention: > The information contained in this message and or attachments is > intended only for the person or entity to which it is addressed and may > contain confidential and/or privileged material. Any review, > retransmission, dissemination or other use of, or taking of any action > in reliance upon, this information by persons or entities other than > the intended recipient is prohibited. If you received this in error, > please contact the sender and delete the material from any system and > destroy any copies. > Thank You. > ________________________________________ > ________________________________________ > This e-mail message has been scanned for Viruses and Content and > cleared by MailMarshal > ________________________________________
