Databases
StackOverflow2013
Postsdbo
POSpring ContextLoader fails to find applicationContext.xml
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSpring ContextLoader fails to find applicationContext.xml
    primarykey
    data
    text
    <p>I've been working alone on a project for a long time and now another developer joined so I wanted to set up the project on his machine from SVN. We are both using very similar set-ups:</p> <ul> <li>OS X Snow Leopard</li> <li>Latest Eclipse WTP</li> <li>m2eclipse Maven Plugin</li> <li>Subversive SVN Plugin</li> <li>Tomcat 6.0.24</li> </ul> <p>The Spring version used is 2.5.6. </p> <p>I set up the project on his machine using Eclipse's "Project from SVN" tool, essentially creating a 1:1 copy of the project. Maven took care of all dependencies without problems as far as I can tell, the project compiled without problems. The project structure is following the Maven standard for webapps with resources (like the applicationContext.xml) in src/main/resources, the project's code in src/main/java and all web-app related files in src/main/webapp and src/main/webapp/WEB-INF respectively.</p> <p>The web.xml is configured to load the context like so:</p> <pre><code>&lt;context-param&gt; &lt;param-name&gt;contextConfigLocation&lt;/param-name&gt; &lt;param-value&gt;classpath:applicationContext.xml&lt;/param-value&gt; &lt;/context-param&gt; &lt;listener&gt; &lt;listener-class&gt;org.springframework.web.context.ContextLoaderListener&lt;/listener-class&gt; &lt;/listener&gt; </code></pre> <p>Using the "Servers" tool of Eclipse I tried launching the application right from Eclipse, but it failed immediately with a FileNotFoundException when trying to load the applicationContext.xml.</p> <p>Since the code checked out from SVN has been left untouched I guess the problem has to do with some parameter for the Maven plugin. Or that I forgot some important step to finalize the set-up. Has anybody encountered a similar issue or has an idea where I should start looking?</p> <p>Thank you very much for you help!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USLunikon
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSpring ContextLoader fails to find applicationContext.xml
      1. USant
      1. VTFavorite
    2. VO
      singulars
      1. POSpring ContextLoader fails to find applicationContext.xml
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSpring ContextLoader fails to find applicationContext.xml
      1. USSteinway Wu
      1. VTFavorite
    1. COcheck if the file has been copied to the appropriate location - i.e. WEB-INF/classes/applicationContext.xml
      singulars
      1. POSpring ContextLoader fails to find applicationContext.xml
      1. USBozho
    2. COIt is not copied to WEB-INF/classes, but that's not the case in my own (functioning) project. Instead, the file is copied to target/classes as per Maven-standard. This again seems to work on both machines. Possibly some configuration is missing for this folder to be included as part of the classpath on start-up?
      singulars
      1. POSpring ContextLoader fails to find applicationContext.xml
      1. USLunikon
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload