Results 1 to 2 of 2

Thread: Managing applicationContext.xml

  1. #1

    Default Managing applicationContext.xml

    Hello,

    This question is about manageability of the applicationContext.xml file.

    As new business objects and DAOs are added into the architecture this file is going to grow large. Hence, is there a way by which this file can be somehow "modularized" (like struts-config.xml)?

    Also, when there is a team working on the project. This file is going to be updated by all. This modularization will help solve the issue of everyone trying to modify the same file.

    Thanks

  2. #2
    Join Date
    Aug 2004
    Location
    Southampton, UK
    Posts
    826

    Default

    There are a collection ways in which you can modularize your Spring configuration files.

    1. Use the <import> tag.
    2. Most ApplicationContext implementations support input from multiple files, so you can create a single ApplicationContext from n configuration files.

    In a web application settings the ContextLoaderListener/Servlet accepts a comma-separated list of file names from which to load the ApplicationContext .

    Rob
    Rob Harrop
    Lead Engineer, dm Server
    SpringSource
    http://www.springsource.com

    Co-Author - Pro Spring

Similar Threads

  1. Managing components / projects / dev cycle: Maven or ant?
    By rebornspirit in forum Architecture
    Replies: 9
    Last Post: Oct 6th, 2006, 09:34 AM
  2. Managing large Spring XML config files
    By roshang in forum Architecture
    Replies: 7
    Last Post: Oct 12th, 2005, 10:16 AM
  3. Managing configuration & dependencies?
    By jbar in forum Architecture
    Replies: 5
    Last Post: Sep 1st, 2005, 09:52 AM
  4. Managing beans on JDK 1.4
    By josep in forum Container
    Replies: 2
    Last Post: Jun 17th, 2005, 05:06 AM
  5. Replies: 2
    Last Post: Apr 15th, 2005, 02:11 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •