[OWB-308] minor clean up on specialization code path

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: M3
• Fix Version/s: M4
• Component/s: Injection and Lookup
• Assignee: Gurkan Erdogdu
• Reporter: Ying Wang
• Created: 25/Feb/10 22:43
• Updated: 26/Feb/10 00:17
• Resolved: 26/Feb/10 00:17

Description

Ran some tests on recent driver and found a few Exceptions fired due to multiple invocation of bean.setBeanName( ) when configure specialization. Changes in this patch include:

1. For class-based specialization, if bean specialization is already configured, skip setting bean name and populating qualifiers
2. For producer-based specialization, comment out 2 blocks of setBeanName/populating qualifiers in old code path, since that is delayed to configSpecializedProducerMethodBeans() in checkSpecializations step.
3. Original test case SpecializesProducer1Test will not work, since there is no container and checkSpecializations( ) is not invoked.
4. migrate new SpecializesProducer1Test to use a container in newtest package.