0

Under normal startup of my application checking the server log shows that when it is time for a particular bean to be deployed, it shows something along the lines of:

installing bean: ...

with dependencies: 
and demands:
  ...
and supplies:  
  jndi:My_EAR/My_Class/remote   
  Class:my.package.my.class  
  jndi:My_EAR/My_Class/local-my.package.my.class

However, if I deploy the same bean with all of the classes being instrumented by cobertura, it no longer 'supplies' the "Class:" entry, which seemingly stops me being able to inject the class without referencing it explicitly by JNDI name.

Is this intentional behaviour? Is there a way to force it to still supply the Class entry? It's a large codebase with a heavily used class so I'd rather not have to update all injection references if I can get away with it.

Thanks.

Andrew Stubbs
  • 4,322
  • 3
  • 29
  • 48
  • I don't know the answer, but could you share why you want to deploy the instrumented code? I've never done something like this, but I can see that it might have a use case or two (detect dead code?) – Augusto Aug 03 '12 at 14:55
  • Pretty much, I have JUnit tests set up that are testing how things are acting within the container at the component level, I'd like to be able to see the coverage of said components if possible. – Andrew Stubbs Aug 06 '12 at 08:04

0 Answers0