If you're using AppFuse 2, it's best to create and modify an applicationContext.xml file (like in the tutorials). This way, your configuration lives in your application and AppFuse's lives in other files. If you ever want to disable AppFuse functionality, you can remove it's files that contains those beans (this may cause downstream issues, but if you're Spring-savvy, it shouldn't be too hard to solve).
Matt On 3/6/07, VJ22 <[EMAIL PROTECTED]> wrote:
Hello, Just a simple architectural question....Should we stick to modifying the existing application context files ( e.g. *dao.xml,*service.xml) or is it advisable to keep our dao/service classes seperately ? If I stick to re-using does this mean that I will have to check out the source code into my project and start building it with my new classes in-built ? Any pointers.... Tks...VJ -- View this message in context: http://www.nabble.com/Architectural-Question-tf3353510s2369.html#a9326095 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- http://raibledesigns.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
