Why is the application class holding database properties? What you're wanting to do is called tight-coupling is not a good idea as it makes one class rely too much on the other.


>Any other way around this problem? E.g. in the application class I want to keep a reference to Database class, but from Database class I want to set properties of the application class?
>
>If, say, I add similar (or same) properties to the database class, can I somehow signal to the application class when database is setting its properties, so I can update application class properties?