This is deliberate. We have deprecated the usage of plain "class" and
"parent" in favor of "(class)" and "(parent)", respectively, to bring those
settings in line with the other special properties: "(abstract)",
"(singleton)", etc. Plain names indicate bean properties there, which was
confusing with the special keys "class" and "parent". After all, a bean
class has every right to have an actual "parent" bean property, that is, a
"setParent" method... which of course is completely different from setting
the parent of a bean definition.
As a consequence, I would suggest to perform a renaming on all your
properties files there: simply replace ".class=" with ".(class)=" and
".parent=" with ".(parent)=". It's likely that we are gonna remove the
entire support for the former special keys in Spring 1.3, to actually allow
for a true "parent" bean property.
Juergen
_____
From: spr...@li...
[mailto:spr...@li...] On Behalf Of
Magnus Heino
Sent: Friday, November 18, 2005 10:18 AM
To: spr...@li...
Subject: [Springframework-developer] deprecated
PropertiesBeanDefinitionReader's "class" and "parent" keywords in favor of
"(class)" and "(parent)"
Hi.
I am using ResourceBundleViewResolver.
The deprecation to "class" in favor of "(class)" in Spring 1.2.6 means that
entries in views.properties that used to be
Index.class=org.springframework.web.servlet.view.JstlView
Index.url=/WEB-INF/views/Index.jsp
now has to be
Index.(class)=org.springframework.web.servlet.view.JstlView
Index.url=/WEB-INF/views/Index.jsp
Otherwise you get a deprecation warning:
WARN Use of 'class' property in
org.springframework.beans.factory.support.PropertiesBeanDefinitionReader is
deprecated in favor of '(class)'. at
org.springframework.beans.factory.support.PropertiesBeanDefinitionReader.isC
lassKey(PropertiesBeanDefinitionReader.java:506)
Bug or feature?
--
/Magnus Heino
|
