|
From: Alef A. <al...@jt...> - 2004-05-14 13:32:18
|
Remco, You shouldn't be writing your own AbstractApplicationContext. There are BeanFactories and BeanDefinitionReaders. The BeanDefinitionReader is what you should have a look at. There's XmlBeanDefinitionReader that reads XML files and there is also a properties based reader. Time is being spent on getting a Jython Beandefinitionreader in place, but this won't be ready soon. Also, I've spent a bit of time on the GroovyBeanDefinitionReader, but since Groovy is still a moving target, I've postponed it a bit (also because of time limitations). Have a look at the thread of about almost ago a week ago about alternative methods to read bean definitions (http://article.gmane.org/gmane.comp.java.springframework.user/1987 and then click on the subject to see the thread). Groet, Alef _____ From: spr...@li... [mailto:spr...@li...] On Behalf Of Remco Bos Sent: Friday, May 14, 2004 3:04 PM To: spr...@li... Subject: [Springframework-developer] ApplicationContext without the use of XML Is anyone using the springframework ApplicationContext without the use of XML (applicationContext.xml)? I know it's possible to write your own AbstractApplicationContext implementation, but has anyone tried it? I don't like XML configuration files. I really don't. First I had to learn the beautiful java language, and now I feel like a scriptkiddy again, coding bean mappings and workflow stuff (mvc) and other things in XML files. (I do see the beauty of dependency injection, but XML.) |