This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
When I running my tests, all is OK. But when results are transforming from XMLs to HTMLs, exception from xalan is shown in console and no HTML results are generated. See attachment for last lines of xtest output.
Created attachment 9001 [details] Output
This is cause by the fact, that there is a conflict between different versions of xalan (one is supplied by JDK and the other one is supplied by XTest). For more details look at xalan mailing list archive at <http://marc.theaimsgroup.com/?l=xalan-j-users&m=103642272130703&w=2> A solution for this might be to disable using XTest's supplied Xalan when running tests in JDK 1.4.*.
I found workaround to get it worked. Add following code into XMLFactoryUtil.NestedTransformerImpl.transform(...) : String val=trans.getOutputProperty("{http://xml.apache.org/xalan}content-handler"); if (val!=null) trans.setOutputProperty("{http://xml.apache.org/xslt}content-handler", val); val=trans.getOutputProperty("{http://xml.apache.org/xalan}entities"); if (val!=null) trans.setOutputProperty("{http://xml.apache.org/xslt}entities", val); val=trans.getOutputProperty("{http://xml.apache.org/xalan}indent-amount"); if (val!=null) trans.setOutputProperty("{http://xml.apache.org/xslt}indent-amount", val); Martin, do you agree with that ?
I think if it really works for all usecases (i.e. run build script from shell, run build script in ide) this could be used as a workaround for current problems. On the other hand, I would like to see more robust solution of this problem in the future, because Xalan can change again and in XTest there is currently no reason to use our supplied Xalan in JDK 1.4 or higher. Also when JDK 1.3 will not be supported, we can get rid of Xalan in XTest at all. It will also shrink the size of the whole package, which is always a good thing.
OK, workarounded :-)