|
Project
|
IntelliJ IDEA
|
|
Priority
|
Normal |
|
Type
|
Bug |
|
Fix versions
|
No Fix versions |
|
State
|
Fixed |
|
Assignee
|
Peter Gromov |
|
Subsystem
|
J2EE.Spring |
|
Affected versions
|
No Affected versions |
|
Fixed in build
|
108.65 |
I'll try to next nightly build today.
confirmed no other spring/custom plugins were installed
I'm using JDK5 in my project that is provided from WAS 6.1.0.19 because I'm working and deploying into that specific server for my project.
Grant
I will. Do you know when they will be available on the ftp?
Thanks
BTW – this is parsing the DWR namespace with DWR 2.0.5 JAR.
I can zip up the JDK I'm using for my project if that helps.
Grant
Thanks
So, we still see incompatible class version? Even 47 (0x2F) doesn't suit it? Due to the spec, it should fit into Java 1.3.
So, we get to know which class versions does your JDK need.
Yes, maybe zipping JDK up isn't such a bad thing. A more minor thing is to try to run com.intellij.spring.model.xml.custom.CustomBeanParser class from customNs.jar in Spring plugin. It has main method, and reads from console. If it actually runs, you could type 'input\n' and some other text, and then see it fails because it can't find Spring in classpath. That would be pretty normal.
By the way, stupid question, do your Spring and DWR (as they appear in classpath of your IDEA module) class versions satisfy your JDK? Should be at most 49 (0x31) in any class file at offset 6, after CAFEBABE00.
I haven't had a chance to test your suggestions but in the mean time, I uploaded the WAS JDK I'm using as IDEADEV-32098.zip to the .uploads folder on your FTP. Maybe using that will help you reproduce.
Thanks!
I should also note, I'm using the Spring 2.5.6 build from the public maven repo as well.