Hi all, Versions Tapestry: 5.2.4 Spring: 3.1.0.M1
We're using java based container configuration with spring - so no xml files are used for configuring beanfactories. With tapestry-spring this is currently unsupported as TapestryApplicationContext extends from XmlWebApplicationContext. As a workaround I've tried setting the tapestry.use-external-spring-context (Compatibility mode). I then get runtime exceptions due to service naming conflicts. "Service id 'environment' has already been defined..." Believe this is an internal spring bean introduced in 3.1.0.M1. Anyways - I don't really need the compatibility mode where spring beans are exposed as services. I know it's possible to have an applicationcontext.xml that defines a single bean entry - which is annotated with @Configuration. But the mission was to get rid of all xml configurations to begin with. Any plans for tapestry-spring to support AnnotationConfigWebApplicationContext? Or perhaps - use the Compatibility mode with the (new) option of turning off exposure of spring beans as tapestry services. Any suggestions? thanks Magnus
