[OWB-642] Method WebBeansUtil.configureProducerMethodSpecializations is unreliable

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.3
• Fix Version/s: 1.5.0
• Component/s: Inheritance, Specialization
• Environment: OWB trunk
• Assignee: Martin Kočí
• Reporter: Martin Kočí
• Created: 20/Jan/12 16:07
• Updated: 19/Apr/15 14:53
• Resolved: 12/Apr/15 19:12

Description

I have specialized producer method like this:

@Produces @Specializes @MyConfigValue @Named
public Boolean getProducerMethod()

{....}

Problem is that @Named is also at parent method -> exception "Specialized method getProducerMethod may not define @Named annotation"

but this happens randomly once per 10 container starts or so.

I tracked it down to:

if (superMethod != null && superMethod.equals(pb.getCreatorMethod()))

{ producerBeanListHelper.add(pb); pLeft = (pb.isSpecializedBean()) ? pb : null; }

else

{ pLeft = null; }

When I comment out the pLeft = null; line OWB detect problem with @Named every time

I guess that there are two or more problems together:

1) client problem in my code : @Named at specialized method
2) configureProducerMethodSpecializations is based on loop over BeanManagerImpl().getBeans(), which is set -> random order of ProducerMethodBean procesing
3) bug in pLeft/pRight algorithm that clears pLeft with first unsuccessful method match, but pLeft/pRight are used for class equality, not method equality