On Wed, 31 Oct 2001 20:15, Stephane Bailliez wrote: > Each solution has its limit there. Simply because we don't want to put the > hassle on the user and avoid him to put 3 jars in the classpath we package > everything in a single one. > > More than often in real time case it appears you have to deal with old > versions because you did a development tighted to it (Say parser.jar and > the binding) and can't switch to a new version easily (you simply cannot > allocate time for it), and you want to benefit from some recent version of > Xalan 2.x for some other features (extended support of xsl) and xt for its > speed in some area. All this must work together. Add to this that you are > using castor that needs xerces for serialization and that it must run in > some version old version of tomcat or weblogic that mess everything and you > are in a real mess. > > I even encountered the case using OpenXML about an incorrect signature for > a method in a DOM interface... > > The fact that everyone want to bundle everything in a jar makes it a pain > because your only solution would be to hack the jars and remove all these > and explicitely separate this in dom1.jar, dom2.jar, sax1.jar, sax2.jar > because you end up with dependencies that you cannot control in a web > application and even sometimes you end up with circular dependencies.
yup - but it is a more widespread issue. The JVM design is soo poor in this area it is astounding. A decent shared library system that learnt from mistakes of .so/.dll hells based on mechanisms like JDK1.3 extensions would be sooo much better. Unfortunately this thing makes it harder for a monopoly to be established so I can't see it being changed in the future ;( -- Cheers, Pete -------------------------------------------- Beer is proof that God loves us and wants us to be happy. -- Benjamin Franklin -------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
