Spicefactory

sikeh · Joined: 15 Jan 2010 Posts: 5

Hi all,

I'm new to Cinnamon, my spring conf looks like the following:

Jens Halm · Posted: Sat Jan 16, 2010 12:38 am Post subject:

Hm, usually Spring people are quite good in keeping backwards compatibility so I'm a bit surprised. Does the container throw any Exceptions as an indication of what it does not like? I haven't worked with Spring 3 myself so far.
_________________
Jens Halm
Spicefactory

sikeh · Joined: 15 Jan 2010 Posts: 5

Hi Jens,

for instance, I have

Jens Halm · Posted: Sat Jan 16, 2010 2:24 pm Post subject:

Now this looks weird. The message implies that the BookingService is not available at all. I'm inclined to think that this is probably not Cinnamon-related. Could it be that they changed something in the way how and when a bean qualifies for auto-wiring?

It would be interesting to see what happens if you switch back to directly referencing the bean instead of autowiring:

sikeh · Joined: 15 Jan 2010 Posts: 5

Hi Jens,

I think it's the problem of <cinnamon:export-service /> tag, if I comment this out, beans are created and injected properly under Spring 3.

Regards,
Sike

Jens Halm · Posted: Mon Jan 18, 2010 1:36 pm Post subject:

Then it must be swallowing exceptions. Or they changed something in the way custom namespace handlers are registered. Silent failure is very rare with Spring, so it really looks weird. I'll be looking into it, but it may take some time.
_________________
Jens Halm
Spicefactory

sikeh · Joined: 15 Jan 2010 Posts: 5

any updates on this?

Regards,
Sike

wensg · Joined: 10 Mar 2010 Posts: 2

I ran into the same problem when using spring 3. Apparently the AbstractBeanDefinitionParser from spring changed so that it now also registers a bean alias based on the name attribute of the element it is parsing. The 'cinnamon:export-service' tag in the following definition

<bean id="pmt-metamodelLoader" class="org.spicefactory.pimento.metamodel.impl.DefaultMetamodelLoader" lazy-init="true">
<cinnamon:export-service service-interface="org.spicefactory.pimento.metamodel.impl.MetamodelLoader"/>
</bean>

creates a bean of type "org.spicefactory.cinnamon.config.spring.SpringServiceConfig" with alias "pmt-metamodelLoader".

I was able to work around this by explicitly declaring the serviceconfig bean:

<bean id="pmt-metamodelLoader" class="org.spicefactory.pimento.metamodel.impl.DefaultMetamodelLoader" lazy-init="true"/>

<bean class="org.spicefactory.cinnamon.config.spring.SpringServiceConfig">
<constructor-arg type="java.lang.String" value="pmt-metamodelLoader"/>
<constructor-arg type="java.lang.String"><null/></constructor-arg>
<constructor-arg type="java.lang.Class" value="org.spicefactory.pimento.metamodel.impl.MetamodelLoader"/>
<constructor-arg type="java.lang.Class" value="org.spicefactory.pimento.metamodel.impl.DefaultMetamodelLoader"/>
<constructor-arg type="java.util.List"><null/></constructor-arg>
<constructor-arg type="boolean" value="true"/>
<constructor-arg type="java.lang.String"><null/></constructor-arg>
</bean>

Jens Halm · Posted: Thu Mar 11, 2010 11:23 am Post subject:

sikeh · Joined: 15 Jan 2010 Posts: 5

thanks for your help, wensg : )

however I still have a question, seems like you are using pimento, but I'm not, how should I configurate serviceconfig bean in this case?

Regards,
Sike