"ragavgomatam" wrote:
In my spring-inject.jar under META-INF I have a spring-inject-spring.xml21:15:50,688 INFO [NamedXmlBeanDefinitionReader] Loading XML bean definitions from URL [vfsfile:/C:/jboss-5.0.0.Beta3/server/default/deploy/Ejb3.ear/spring-inject.jar/META-INF/jboss-spring.xml]
I've just added (commited in the trunk) a legacy default name support to SpringParserDeployer.
The current default is still from meta file: -spring.xml.
But if you set this flag to true, the name from jar containing -spring.xml file will be used.
From SpringParserDeployer:
/** * Should we use deployment unit's name as default. * e.g. using string before .jar|spring|... as the name * * Previous versions used string before .spring as the name, * setting this to true results in this legacy behaviour. * * Current default is string before -spring.xml. * * @param useLegacyDefaultName the flag */ public void setUseLegacyDefaultName(boolean useLegacyDefaultName) { this.useLegacyDefaultName = useLegacyDefaultName; }
Ales,
Yeah that was a small bug in my ant build....Fixed it...Works fine....Thanks...I think this should be documented in Jboss-spring documentation....
Spring Injection works fine with Ejb 3. with Spring Deployer in Jboss 5 Beta 3.
As an aside, how does Pitchfork fit in ? Can we try injecting POJO's into ejb3 with PitchFork M2 release ? They have a JeeEjbBeanFactoryPostProcessor in pitchfork which recognizes @EJB anotation. Can we use this too in Jboss 5 ? Your thoughts.
"ragavgomatam" wrote:
Yeah that was a small bug in my ant build....Fixed it...Works fine....Thanks...I think this should be documented in Jboss-spring documentation....
Spring Injection works fine with Ejb 3. with Spring Deployer in Jboss 5 Beta 3.
"ragavgomatam" wrote:
As an aside, how does Pitchfork fit in ? Can we try injecting POJO's into ejb3 with PitchFork M2 release ? They have a JeeEjbBeanFactoryPostProcessor in pitchfork which recognizes @EJB anotation. Can we use this too in Jboss 5 ? Your thoughts.