Re: [Springframework-developer] Props and prop tags

[Martin K. <Mar...@St...>]

>   I just wanted to know why these two are named prop and props,
> I think property and properties would be more obvious. Are there
> any plans to change the tag style within the Springframework 2.x 
> releases?

Well, I reread this post and I noticed that it isn't that obvious, 
what I mean. I think about the destinction between a property
of a bean and the property of a properties. I don't know
the exactly reason why a property of properties, an element 
of a map and a property of a bean are diffrently handled.

I understand the diffrence between list set map but I do 
not know what property (bean), property (props)
and element(map) makes so distinct.

To substitute prop it would be possible to 
use property I guess.

Looking at the property declaration:

<!ELEMENT property (
 description?,
 (bean | ref | idref | list | set | map | props | value | null)
)>

Wouldn't it be possible to go for:

<!ELEMENT property (
 description?,
 (bean | ref | idref | list | set | map | props | value | null|#PCDATA)
)>

It would also be a nice to have since to set a string property
I would only go for:
<property name="name">my name is</property>

Objects and all can be mapped to string using a special method on
the properties type/implementation. 

Since props and map are semantically equal (except the destinction
for string), I don't if it shouldn't be a matter of the semantic when
the parameter gets injected.

Meaning if you declare:

setMyProperty(Map map); //you will get a map
setMyProperty(StringProperties properties); //you will get properties
                       
I mean there is not a distinction in the general concept between
property and prop and props and map. 

I guess that this destinction is not usefull in terms of the 
declartive language which is used to set up the beans context.
It seams not necessary but it is not urgent or need after all.
I just wondered why this decision was made.


By the way I am still refactoring the DefaultXmlBeanDefinitionParser 
and it drove me using a semantic active parse tree. You know
just like an ordinary parse tree but with a lot of semantic knowledge
I would't refer it a parse tree anymore. Currently I am addin

> 
> 
> Cheers,
> 
> Martin (Kersten)
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer