XSLT Debugger not showing XML output
Answered
Having an odd problem with the XSLT Debugger. Whenever I try to debug an XSL file the output is missing all XML markup. It only shows me the textual attributes. If I use the debugger without debug the output appears correctly for the same run configuration?
e.g. run output
debug output
The structure tab on the debug output is similarly empty except for one root text node. Shouldn't the output match? obviously I'm trying to debug a bunch of XSL stylesheets.
This is IDEA 2017.3.5, jdk 7 and I'm using saxon-he 9.7.0 on centos 6.
There are errors in the idea.log:
2018-06-26 15:20:04,995 [ 892720] ERROR - rationStore.ComponentStoreImpl - Cannot init XSLT-Support.FileAssociations.UIState component state
java.lang.RuntimeException: java.lang.NoSuchMethodException: com.intellij.ide.util.treeView.TreeState.<init>()
at com.intellij.util.ExceptionUtil.rethrow(ExceptionUtil.java:171)
at com.intellij.util.ReflectionUtil.newInstance(ReflectionUtil.java:427)
at com.intellij.configurationStore.DefaultStateSerializerKt.deserializeState(DefaultStateSerializer.kt:36)
at com.intellij.configurationStore.StateStorageBase.deserializeState(StateStorageBase.kt:42)
at com.intellij.configurationStore.StateStorageBase.getState(StateStorageBase.kt:38)
at com.intellij.configurationStore.StateStorageBase.getState(StateStorageBase.kt:34)
at com.intellij.configurationStore.ComponentStoreImpl.a(ComponentStoreImpl.kt:315)
at com.intellij.configurationStore.ComponentStoreImpl.a(ComponentStoreImpl.kt:290)
at com.intellij.configurationStore.ComponentStoreImpl.initComponent(ComponentStoreImpl.kt:90)
at com.intellij.openapi.components.impl.PlatformComponentManagerImpl.initializeComponent(PlatformComponentManagerImpl.java:54)
at com.intellij.openapi.components.impl.ServiceManagerImpl$MyComponentAdapter.getComponentInstance(ServiceManagerImpl.java:225)
at com.intellij.util.pico.DefaultPicoContainer.getLocalInstance(DefaultPicoContainer.java:239)
at com.intellij.util.pico.DefaultPicoContainer.getComponentInstance(DefaultPicoContainer.java:206)
at com.intellij.openapi.components.ServiceManager.doGetService(ServiceManager.java:49)
at com.intellij.openapi.components.ServiceManager.getService(ServiceManager.java:43)
at org.intellij.lang.xpath.xslt.associations.impl.FileAssociationsConfigurable.<init>(FileAssociationsConfigurable.java:40)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at org.picocontainer.defaults.InstantiatingComponentAdapter.newInstance(InstantiatingComponentAdapter.java:193)
at com.intellij.util.pico.CachingConstructorInjectionComponentAdapter.doGetComponentInstance(CachingConstructorInjectionComponentAdapter.java:103)
at com.intellij.util.pico.CachingConstructorInjectionComponentAdapter.instantiateGuarded(CachingConstructorInjectionComponentAdapter.java:80)
at com.intellij.util.pico.CachingConstructorInjectionComponentAdapter.getComponentInstance(CachingConstructorInjectionComponentAdapter.java:63)
at com.intellij.openapi.extensions.AbstractExtensionPointBean.instantiate(AbstractExtensionPointBean.java:75)
at com.intellij.openapi.options.ConfigurableEP$ClassProducer.createElement(ConfigurableEP.java:341)
at com.intellij.openapi.options.ConfigurableEP.createConfigurable(ConfigurableEP.java:267)
at com.intellij.openapi.options.ex.ConfigurableWrapper.a(ConfigurableWrapper.java:58)
at com.intellij.openapi.options.ex.ConfigurableWrapper.getConfigurable(ConfigurableWrapper.java:117)
at com.intellij.openapi.options.ex.ConfigurableWrapper.cast(ConfigurableWrapper.java:98)
at com.intellij.openapi.options.ex.ConfigurableCardPanel.prepare(ConfigurableCardPanel.java:42)
at com.intellij.openapi.options.ex.ConfigurableCardPanel.prepare(ConfigurableCardPanel.java:35)
at com.intellij.ui.CardLayoutPanel.a(CardLayoutPanel.java:128)
at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:315)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NoSuchMethodException: com.intellij.ide.util.treeView.TreeState.<init>()
at java.lang.Class.getConstructor0(Class.java:3082)
at java.lang.Class.getDeclaredConstructor(Class.java:2178)
at com.intellij.util.ReflectionUtil.newInstance(ReflectionUtil.java:412)
Please sign in to leave a comment.
Looking at the exception could be that XSLT Debugger plugin is not compatible. Could you please try 2018.1.5 from https://www.jetbrains.com/idea/download?
If problem remains please file a bug at https://youtrack.jetbrains.com/issues/IDEA.
Can't use IDEA2018 on this legacy project because of the subversion support changes IDEA-184261
Has the xslt debugger definitely been updated in this version?
Found another stylesheet thats behaving oddly. Again can run it successfully, but when I try to debug this time it throws an error:
Which is really odd debug appears to use a different version of saxon to run configurations? Not the project/module version? Matches should be available in XSLT 2.0 the stylesheet is defined as such, its not dependant on backwards compatibility support.
Run and Debug modes use different transformers: https://youtrack.jetbrains.com/issue/IDEA-110474#focus=streamItem-27-551120-0-0
Does it help if you specify transformer type as -Dxslt.transformer.type=saxon9 in Advanced tab VM Arguments field?
No I was already using that and it didn't help, also tried with xalan and I found IDEA-105198 which suggests adding the plugin saxon jars to your project. This didn't work at all. The saxon bundled with the plugin is very much older than saxon-he. Not the same packages internally.
Please file a YouTrack issue with an example project or the information that can be used to try to reproduce the problem. Thank you!