Well,
I had same problem, however it was SIMPLY solved by putting the (or
jboss-spring-jdk5.jar) in the default/lib.
Never ever put jboss-spring-jdk5.jar in your spring or deployer, this is the
problem.
Regards,
Zaid
View the original post :
What about if you have a single spring.jar in the
jboss/server/[configuration]/lib ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4008338#4008338
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4008338
Hum... The same spring.jar for all applications ? I prefer to keep control of
the version in each war.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4008346#4008346
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4008346
Hmmm ... i don't see how else would you be able to use the same BeanFactory
class instance in deployer and .war.
Maybe use previous advice, for the apps that use BF from deployer and scoped
deployment for others.
btw: Spring jars are mostly back compatible, with really small diffs.
View the
That's what i thought. I'll see if it's possible to use the sema spring for all
webapps.
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4008366#4008366
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4008366
