> When testing the 1.7 distro builds I request your extra attention for what > to do with the xalan and xerces jars. > > In the current nightly builds xalan and xerces are present, but 'switched > off' because not named .jar. > > In certain setups this ensures that everything works withouth doing > anything at all with this respect. > > In other setups it might be needed to rename those files or to isntall > them > in your app-server. > > 1.6.5 we released with xerces and xalan jars in WEB-INF/lib and for tomcat > you had to move these to common/endorsed. > > I think we need some configuration which is optimally easy for as many > people as possible and when decided upon, it needs to be documented what > you > have to do for your specific setup. > > So, if you installed/tested 1.7 builds, please report what you did with > these > jars, and what situation would you have liked best.
I am testing mmbase 1.7 for a while now with the editwizards and I copied the xalan and xerces to my tomcat endorsed dir. Today I switched my testing mmbase webapp to tomcat 5.0.16 and java 1.4.2_03 and used the jars from tomcat. At first, the editwizard produced a lot of warnings in the log, but I fixed that. So the editwizard can be used with a normal tomcat installation. When I removed all jars from the endorsed dir I got this error: java.lang.NullPointerException org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java: 725) org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform erImpl.java:2339) org.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(Transformer Impl.java:2160) org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.j ava:1213) org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java: 668) org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java: 1129) org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java: 1107) Guess, It has something to do with classloading and the wizard.xsl java extensions. The jvm xalan is loaded with a different classloader than the webapp classloader and it can't find the classes in the mmbase.jar. Nico Klasens Finalist IT Group Java Specialists
