title: Tomcat context.xml Parameter declaration accessed in Spring's application context
body: <p>One of our apps declare some parameters in Tomcat's context.xml as such:</p>
  
  <pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
  &lt;Context&gt;
      &lt;WatchedResource&gt;WEB-INF/web.xml&lt;/WatchedResource&gt;
      &lt;Parameter name="defaultSchema" override="true" value="demo"/&gt;
      &lt;Resource 
           auth="Container" 
           description="DB Connection for Local Jazzee" 
           driverClassName="oracle.jdbc.OracleDriver" 
           . . .
      /&gt;
  &lt;/Context&gt;
  </code></pre>
  
  <p>And then in Spring's applicationContext.xml we are able to use that parameter when we instantiate some beans:</p>
  
  <pre><code>&lt;bean id="sessionFactory" class="org.springframework.orm.hibernate3.annotation.AnnotationSessionFactoryBean"&gt;
      &lt;property name="dataSource" ref="dataSource" /&gt;
      &lt;property name="hibernateProperties"&gt;
          &lt;props&gt;
              &lt;prop key="hibernate.default_schema"&gt;${defaultSchema}&lt;/prop&gt;
              . . . 
  &lt;/bean&gt;
  </code></pre>
  
  <p>And that works fine.</p>
  
  <p>Problem I'm having is that I'm trying to duplicate this in another application, and it's not working.  When I try to start the app, I get the error:</p>
  
  <pre><code>Invalid bean definition with name 'sessionFactory' defined in class path resource [db/applicationContext.xml]: Could not resolve placeholder 'defaultSchema'
  </code></pre>
  
  <p>It's the same developer Tomcat instance in both cases, so the Tomcat version is the same.  The Spring library versions appear to be the same as well.  Also, if I hardcode the schema name in the application context, it works fine.  So the dataSource is fine.</p>
  
  <p>Any thoughts on what might be breaking this functionality?</p>