I'm seeing some behavior that *appears* to be default CAS behavior, but it's
just not working like I expected and it has me stumped.
If I create a brand new project directory, and only stick a pom.xml in it
(hence using 100% CAS defaults, no overrides or customizations whatsoever) and
run "mvn clean package", I get a cas.war that deploys to Tomcat just fine
(using CAS 4.0.0 and Tomcat 7).
But then I go ahead and add a
src/main/webapp/WEB-INF/spring-configuration/propertyFileConfigurer.xml file,
that has the following contents:
<bean id="propertyPlaceholderConfigurer"
class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
<property name="ignoreResourceNotFound"
value="true" />
<property name="locations">
<list>
<value>file:/home/myuser/cas.properties</value>
</list>
</property>
</bean>
And, just to see what happens, I intentionally *do not* put a cas.properties
file under /home/myuser. Now when I run "mvn clean package" and deploy the
cas.war to Tomcat, I get all sorts of exceptions in the Tomcat log, complaining
about there not being a host.name property specified (which is true since I
don't have a /home/myuser/cas.properties file).
I *expected* CAS to look for /home/myuser/cas.properties and, if it can't be
found, to use the same defaults that were applied before I added a
propertyFileConfigurer.xml file. Instead, it looks like CAS looks for
/home/myuser/cas.properties, and if it can't be found, just gives up and
doesn't try to apply any defaults at all.
Is this normal CAS behavior? If so, what are all the other properties (besides
host.name) that I need to provide CAS with, and where is this documented?
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
