cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <va...@reverycodes.com>
Subject Re: Spring bean names
Date Fri, 07 Dec 2007 16:30:45 GMT
On Dec 7, 2007, at 9:25 AM, Reinhard Poetz wrote:

> Vadim Gritsenko wrote:
>> On Dec 7, 2007, at 2:59 AM, Carsten Ziegeler wrote:
>>> Vadim Gritsenko wrote:
>>>>
>>>> Thanks for quick fix! btw why bean is named
>>>> "org.apache.cocoon.portal.om.CopletAdapter.cocoon" and not
>>>> "org.apache.cocoon.portal.om.CopletAdapter/cocoon"?
>>>>
>>> Good question - to be honest, I don't know :)
>>> I think there were some problems with using a "/" in Spring bean  
>>> names
>> Hmm... That's bad.
>
> It's not really a problem. You can't use "/" in id attributes. That  
> was the reason why <bean name=""/> was introduced because Spring  
> webflow needed a way to put URIs into bean ids.

But we are talking about name attribute? Is there a problem with it too?


>>> it doesn't matter as these components are
>>> accessed through our spring configurator bean map and this bean map
>>> checks for boths versions.
>> Did not know this; I thought only '/' is allowed.
>
> The "/" is used if an Avalon selector is mimicked. If you access  
> Spring beans using the Spring Configurator's bean map, the name  
> doesn't matter because the selection is done based on the interface  
> name.

So Carsten was wrong above? It does not rely on syntax but interface  
name?

Vadim

Mime
View raw message