On 06 Sep 2007 18:11:09 +0200 (CEST), Robo <[EMAIL PROTECTED]> wrote: > After small troubles I had with it I know it. But from my point of view it is > not correct to initiatie not used libraries just by including it in App > Server classpath. From my point of view lib is lib, and when nto called by > developer it sould not be initiated by App server. I runned into troubles > with dependecies SELF initialized itself. I saw this behaviur several times > before but everytime I`m suprised. As I said from my point of view, lib is > lib. But this guides me to troubles :-) But to be concrete I need to develop > demo app using fove frameworks, not using Maven :-), so I put every lib in > wicket into lib dir to not to solve missing lib troubles when building demo > app. But it raised contrary, unnessesary \"self living\" lib problem.
You can't really depend on libs following such rules. All sorts of frameworks do this, from Guice to Seam to logging libraries, and it can get you in trouble with XML handling as well. As a general rule, only include what you need. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
