Hi I'm new to Tapestry, I've managed to implement two working applications so far. My question in not closely related to Tapestry itself but since this mailing list is so helpful and active I decided to ask.
I noticed that since I started using Hibernate, Springs IoC containter and other frameworks there is so many xml config files to manage. First thing you have to place them somwhere then you have to find them somehow in your application context. My question is what is the best way to prevent hardcoding paths to config files in your application code, to make it somehow configurable but on the other hand to not introduce another config files for config files ;) I use Tomcat servlet containter and I must say I am little confused. Take Hibernate for instance. There is this hibernate config file, then hibernate mapping file which I have to place in C:/windows/system32 dir to be seen by hibernate. I tried to use absolute paths etc. but that does not seem to work. It's as if hibernate behaves different in a web application and different in desktop application. Everything is a mess right now and I would really appreciate if any experienced userd could give me a clues how to cope with this problem. I just need general directions how to manage those configs. I thought about definig paths to config files in web.xml as an application context parameters and then get them in my web app but is this any good? -- Best Pozdrawiam Lukasz Kucharski [EMAIL PROTECTED] [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
