]
Pete Muir updated CDITCK-168:
-----------------------------
Fix Version/s: 1.0.2.Final
1.1.0.CR1
extensions.processBean.ProcessBean event count issue
----------------------------------------------------
Key: CDITCK-168
URL:
https://jira.jboss.org/browse/CDITCK-168
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Tests
Affects Versions: 1.0.2.CR1
Environment: any
Reporter: Scott Ferguson
Fix For: 1.0.2.Final, 1.1.0.CR1
The issue is in an assertion in extensions.processBean.ProcessBeanTest, counting the
number of times the Cowshed bean raises a discovery event. There are three tests affected
by this issue:
extensions.processBean.ProcessBeanTest
testProcessProducerFieldEvent()
testProcessProducerMethodEvent()
extensions.processBean.ProcessSessionBeanTest
testProcessSessionBeanEvent()
specifically
testProcessProducerMethodEvent()
79: assert ProcessBeanObserver.getCowShedProcessBeanCount() == 2;
testProcessProducerFieldEvent()
102: assert ProcessBeanObserver.getChickenHutchProcessBeanCount() == 2;
testProcessSessionBeanEvent()
63: assert ProcessBeanObserver.getElephantProcessBeanCount() == 2;
But I can't see how this number is 2 instead of 1. The Cowshed looks like:
public class Cowshed {
@Produces public Cow getDaisy() { ... }
}
So there should be 3 relevant extension events fired:
ProcessBean<Cowshed>
ProcessProducerMethod<Cowshed, Cow>
ProcessBean<Cow>
I double checked the ProcessProducerMethod interface:
ProcessProducerMethod<T,X> extends ProcessBean<X>
which is where the ProcessBean<Cow> comes from, but I don't see where
the 2nd ProcessBean<Cowshed> comes from.
The ProcessSessionBean issue is essentially the same
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: