Spring 2.0 support slightly broken (does not recognize the new dtd)

I noticed that property name completion did not work anymore while editing my springContext.xml.

Turns out that this happens because Spring 2.0 has a spring-beans-2.0.dtd instead of a spring-beans.dtd. (They added a version number)

Is this something that can I can fix/configure manually in IDEA or does this require some magic code change from you guys? If so then I will file a bug report for it.

S.

7 comments
Comment actions Permalink

I think you should add the new DTD to IDEA's resources Plugins.

"Stefan Arentz" <no_reply@jetbrains.com> дÈëÏûÏ¢ÐÂÎÅ:8831274.1164927571581.JavaMail.itn@is.intellij.net...
>I noticed that property name completion did not work anymore while editing
>my springContext.xml.
>

Turns out that this happens because Spring 2.0 has a spring-beans-2.0.dtd
instead of a spring-beans.dtd. (They added a version number)

>

Is this something that can I can fix/configure manually in IDEA or does
this require some magic code change from you guys? If so then I will file
a bug report for it.

>

S.



0
Comment actions Permalink

The xml of Spring 2.0 is like as:

]]>

Idea 6.0 can recognise!

0
Comment actions Permalink

I think you should add the new DTD to IDEA's
resources Plugins.


That does not help. I think IDEA has hardcoded the Spring DTD name somewhere.

S.

0
Comment actions Permalink

Ah yes, the new style XSD seems to work.

For simple projects I usually just use the DTD style though. I'll still file IDEA not recognizing the 2.0 version as a bug then.

S.

0
Comment actions Permalink

http://www.jetbrains.net/jira/browse/IDEADEV-12070

Stefan Arentz wrote:

Ah yes, the new style XSD seems to work.

For simple projects I usually just use the DTD style though. I'll still file IDEA not recognizing the 2.0 version as a bug then.

S.


--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0
Comment actions Permalink

Thank you Maxim.

S.

0
Comment actions Permalink

Shouldn't this be fixed for the 6.0.x version also??

BTJ

0

Please sign in to leave a comment.