* Properties resource file does not exist
* A required property could not be resolved

I think by always “falling back” to some default setting raises the possibility of mis-configuration. One could be thinking we have a successful deployment on staging when it could be pointing to some other environment like QA …

Any ideas on how to have strict failure feedback along with above flexibility?

I have the below bean definition in my application context xml file

${app.mode}

“env” is a boolean in Mode class, and here is how I defined the PropertyPlaceholderConfigurer

file:${conf.dir}/server.properties

and in my class I am using

System.setProperty(“JBOSS.conf.dir”, C:/jboss/server/default/conf);
applicationContext = new ClassPathXmlApplicationContext(“applicationContext.xml”);

Now this {value} is not getting resolved while running the applicaiton. I am getting the below error

org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘mode’ defined in class path resource [applicationContext.xml]: Error setting property values; nested exception is org.springframework.beans.PropertyAccessExceptionsException: PropertyAccessExceptionsException (1 errors); nested propertyAccessExceptions are: [org.springframework.beans.TypeMismatchException: Failed to convert property value of type [java.lang.String] to required type [boolean] for property ‘env’; nested exception is java.lang.IllegalArgumentException: Invalid boolean value [${app.mode}]]
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1031)
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:823)
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:345)
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:226)
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:147)
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:275)
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:318)
org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:81)
org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:66)
org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:57)

Please suggest how to proceed

necesito saber donde configurar el classpath.

Try -Dconfig=file:c://user.properties instead.

Christian

classpath:application.properties
classpath:local.properties
${config}

and in my tomcat run configuration I have specified a VM argument as -Dconfig=”C:\user.properties”
which looks fine to me but when I run tomcat it complains about file not found \C:\user.properties, Can anyone tell me if am missing anything in here.

It’s been years since we’ve had a real use for JNDI. All of our resources are application managed as opposed to configured in a application server. We avoid depending on the app server whenever possible, as those dependencies make testing difficult or lead to duplicate configuration. That’s not to say it isn’t a valid solution, it’s just one that doesn’t work for us because of the way we do things.

<property name=”properties”>
  <props><prop key=”config”></prop></props>
</property>

to the ServletContextPropertyPlaceholderConfigurer definition.