Announcement Announcement Module
No announcement yet.
Custom BeanFactory-implementation? Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Custom BeanFactory-implementation?

    [I already posted about this to the architectural discussion, see
    however, this forum seems to be the correct place.. ]

    I would like to create a custom BeanFactory implementation. What things should I consider? Here are a few questions:

    - is it enough to just implement the BeanFactory interface?
    - or should I implement the ApplicationContext interface instead? (since that is what people actually seem to be using)
    - is the concept of a custom BeanFactory plausible? How difficult it is for applications to take a custom implementation into use?


    I am developing an XML-based configuration tool called JICE that is functionally very close to the XmlBeanFactory of Spring Framework.

    In my opinion JICE has some advantages over XmlBeanFactory. However, Spring framework as a whole is unbeatable because it covers so many different aspects. So I was hoping that JICE and Spring could be made to dance together. JICE could become an alternative for the XmlBeanFactory.

    I'm sorry if this idea sounds too offending. My intention is not to mock Spring.

    Information about JICE can be found at:


    Timo Laitinen
    Last edited by robyn; May 14th, 2006, 11:10 AM.

  • #2
    I'm sorry if this idea sounds too offending. My intention is not to mock Spring.
    No, that's absolutely fine. More config alternatives are a good thing. However, I would rather we continued the discussion over at the other location, although I agree that this would have been a good place for it at the outset.

    So, let's continue at
    Last edited by robyn; May 14th, 2006, 11:12 AM.