That's done already -- this is not a privilege of the spring framework, but part of the DTD specification. All attributes marked as #IDREF in the DTD are verified to match existing #ID elements.
That's done already -- this is not a privilege of the spring framework, but part of the DTD specification. All attributes marked as #IDREF in the DTD are verified to match existing #ID elements.
Not what I mean. Say you have a persistence.xml file with a persistenceService bean. But in business.xml, your object uses this bean but misspells the name, the DTD won't catch this. -- -
don't forget refactoring. Change the variable name, it should not only change the getters/setters, but tags in the spring file. That alone would prob be enough for a first pass...
--pete
ps. the request for spring has already been created...
don't forget refactoring. Change the variable name, it should not only change the getters/setters, but tags in the spring file. That alone would prob be enough for a first pass...
--pete
ps. the request for spring has already been created...
That's done already -- this is not a privilege of the spring framework, but part of the DTD specification. All attributes marked as #IDREF in the DTD are verified to match existing #ID elements.
In article <8492706.1115294520590.JavaMail.itn@is.intellij.net>,
mbrito@gmail.com says...
Not what I mean. Say you have a persistence.xml file with a
persistenceService bean. But in business.xml, your object uses this bean
but misspells the name, the DTD won't catch this.
--
-
David H. McCoy
-
don't forget refactoring. Change the variable name, it should not only change the getters/setters, but tags in the spring file. That alone would prob be enough for a first pass...
--pete
ps. the request for spring has already been created...
http://www.jetbrains.net/jira/browse/IDEABKL-2804
In article <27117137.1115336870400.JavaMail.itn@is.intellij.net>,
no_mail@jetbrains.com says...
Some do change, actually. Classpaths but not much else. Support is most
welcome!
--
-
David H. McCoy
-