Project
IntelliJ IDEA
Priority
Normal
Type
Bug
Fix versions
No Fix versions
State
Fixed
Assignee
Dmitry Avdeev
Subsystem
J2EE.Spring
Affected versions
No Affected versions
Fixed in build
108.65  
  • Created by   Taras Tielkes
    4 years ago (08 Oct 2007 21:04)
  • Updated by   root
    2 years ago (17 Jan 2010 20:54)
  • Jira: IDEADEV-22587
    (history, comments)
 
IDEA-41391 no completion/validation for some attributes of the 'lang' namespace
0
Issue is visible to: All Users
  The issue is visible to the selected user group only
  1. no resolving for 'scope' attribute (all)
  2. no resolving for 'script-interfaces' attribute (jruby,bsh)
  3. no resolving for 'script-source' attribute (all)
  4. attribute 'refresh-check-delay' is declared as 'xsd:long' but modeled as 'Integer'
  5. no resolving for 'customizer-ref' attribute (groovy)

Attached patch solved the first 3.
It also removes from methods from com.intellij.spring.model.xml.lang.DynamicScript which were duplicate to methods on com.intellij.spring.model.xml.lang.SimpleScript.

I assume the fix for (4) should be made in DOM internals: at the moment it doesn't support Long type.

(5) can be easily fixed using the annotation-driven Converter from the patch attached to IDEA-38971: the specified type should be 'org.springframework.scripting.groovy.GroovyObjectCustomizer'

Issue was resolved
Comments (4)
 
History
 
Linked Issues (?)
 
Taras Tielkes
  Taras Tielkes
08 Oct 2007 21:23
4 years ago
In addition, for <lang:jruby> and <lang:bsh>, the value of the 'script-interfaces' attribute could be used to implement getBeanClass(). While only the first specified interface can be returned through this method, it would allow bean reference completion from other beans (IDEA-39721) to work in most cases.
t800t8
  t800t8
15 Oct 2007 06:31
4 years ago
No resolving for "name" attribute of <lang:property>
Taras Tielkes
  Taras Tielkes
15 Oct 2007 12:41
4 years ago
To support "name", IDEA (or a plugin) would have to parse the groovy/jruby/bsh language.

The other attributes mentioned in the issue description and first comment do not require such extensive support. In other words they could be supported in a bugfix release without much risk.
Dmitry Avdeev
  Dmitry Avdeev
17 Oct 2007 15:31
4 years ago
Thanks Taras. Your patch is applied.