I'm playing around with XML config file and noticed this behavior.
When I have a config property name in my file that doesn't exist in my package I get this error. "Cannot resolve a package path to an object in the package". For example, if I have a connection object named "DB_Conn1" in my package, and in the config file, I have a property for something called "DB_Conn2", then the package errors saying that there is no connection object named "DB_Conn2" in my package.
BUT, it does't always behave this way. If I go into my connection manager in my package and put in connection information that is valid, then the package seems to ignore the fact that I have a non-existing property in the config file and just uses the connection info that is saved in the package.
This seems like inconsistent behavior to me. Does anyone know what I'm talking about?