Description Anton Lem 2013-01-18 18:18:09 EST

I'm trying to migrate some web-spring-aop application to Virgo. To enable LTW I added <context:load-time-weaver aspectj-weaving="on" /> element into a spring context. During starting of my web bundle Virgo wrote:

o.s.beans.factory.support.DefaultListableBeanFactory              Overriding bean definition for bean 'loadTimeWeaver': replacing [Generic bean: class [org.springframework.context.weaving.DefaultContextLoadTimeWeaver]; scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null] with [Generic bean: class [org.springframework.context.weaving.DefaultContextLoadTimeWeaver]; scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null]

As I know, in this case Virgo has to use KernelLoadTimeWeaver instead DefaultContextLoadTimeWeaver. But it doesn't (as it wrote). Then I tried to explicitly set the weaver class <context:load-time-weaver aspectj-weaving="on" weaver-class="org.eclipse.virgo.kernel.dmfragment.internal.KernelLoadTimeWeaver"/>.
Virgo wrote:

o.s.beans.factory.support.DefaultListableBeanFactory              Overriding bean definition for bean 'loadTimeWeaver': replacing [Generic bean: class [org.eclipse.virgo.kernel.dmfragment.internal.KernelLoadTimeWeaver]; scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null] with [Generic bean: class [org.eclipse.virgo.kernel.dmfragment.internal.KernelLoadTimeWeaver]; scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null] 

As you can see the replaced and the new weaver is equal again. It seems to me we have some mistake (copy-paste???) in a message formating command. Or is this more serious problem?