RE: [Springframework-developer] Anybody know historical purpose of dependency-check 'default' value?

[Christophe R. <cr...@ac...>]

It may have a relation with the beans root node default-dependency-check
attribute.

<!ATTLIST beans default-dependency-check (none | objects | simple | all)
"none">

When dependency-check is set to default on some beans, it should use the
value specified on the beans node.

Just my thought...

Christophe

> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...] On Behalf
> Of Alef Arendsen
> Sent: Wednesday, June 30, 2004 7:35 PM
> To: spr...@li...
> Subject: RE: [Springframework-developer] Anybody know historical purpose
> of dependency-check 'default' value?
> 
> I don't know,
> 
> I've searched a bit through my email archives and have attached a couple
> of mail related to the introduction of the dependency checking features.
> 
> I think we (or however implemented this) chose to have a default
> attributes to allow for future modification of the default if needed??
> 
> Alef
> 
> > -----Original Message-----
> > From: spr...@li...
> > [mailto:spr...@li...] On
> Behalf
> > Of Colin Sampaleanu
> > Sent: Thursday, July 01, 2004 1:01 AM
> > To: spr...@li...
> > Subject: [Springframework-developer] Anybody know historical purpose
> of
> > dependency-check 'default' value?
> >
> > I'm trying to figure out why the DTD allows both 'none' and 'default'
> > for the dependency-check attribute.
> >
> > <!--
> >     Optional attribute controlling whether to check whether all this
> >     beans dependencies, expressed in its properties, are satisfied.
> >     Default is no dependency checking.
> >
> >     "simple" type dependency checking includes primitives and String
> >     "object" includes collaborators (other beans in the factory)
> >     "all" includes both types of dependency checking
> > -->
> > <!ATTLIST bean dependency-check (none | objects | simple | all |
> > default) "default">
> >
> > If you look at the code, none is the default (when nothing is
> > specified). 'default gets treated exactly like none, but it seems
> almost
> > like an accident.
> >
> >     protected int getDependencyCheck(String att) {
> >         int dependencyCheckCode =
> > RootBeanDefinition.DEPENDENCY_CHECK_NONE;
> >         if (DEPENDENCY_CHECK_ALL_ATTRIBUTE_VALUE.equals(att)) {
> >             dependencyCheckCode =
> RootBeanDefinition.DEPENDENCY_CHECK_ALL;
> >         }
> >         else if (DEPENDENCY_CHECK_SIMPLE_ATTRIBUTE_VALUE.equals(att))
> {
> >             dependencyCheckCode =
> > RootBeanDefinition.DEPENDENCY_CHECK_SIMPLE;
> >         }
> >         else if (DEPENDENCY_CHECK_OBJECTS_ATTRIBUTE_VALUE.equals(att))
> {
> >             dependencyCheckCode =
> > RootBeanDefinition.DEPENDENCY_CHECK_OBJECTS;
> >         }
> >         // else leave default value
> >         return dependencyCheckCode;
> >     }
> >
> > Is 'default' still needed?
> >
> > Colin
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email sponsored by Black Hat Briefings & Training.
> > Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> > digital self defense, top technical experts, no vendor pitches,
> > unmatched networking opportunities. Visit www.blackhat.com
> > _______________________________________________
> > Springframework-developer mailing list
> > Spr...@li...
> > https://lists.sourceforge.net/lists/listinfo/springframework-developer
> >
> >
>