[
https://issues.apache.org/jira/browse/OWB-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974991#action_12974991
]
David Jencks commented on OWB-493:
----------------------------------
I think there is a problem in OWB with the current test. The test has:
Cow...
public class Cowshed
{
@Produces
public Cow getDaisy()
{
return new Cow("Daisy");
}
...
public void observeCowProcessProducerMethod(@Observes
ProcessProducerMethod<Cow, Cowshed> event)
{
ProcessBeanObserver.cowProcessProducerMethod = event;
}
which the tck expects to be called with the ProcessProducerMethod<Cow,
Cowshed> event. However, although a ProcessProducerMethod is being
constructed, it appears to be a ProcessProducerMethod<Cowshed, Cow> so isn't
firing this observer method.
I haven't been able to figure out if the test is correct and/or how to switch
the types in the event.
> ProcessProducerMethod and ProcessProducerField type parameters are reversed
> in filtering (?) CDITCK-168
> --------------------------------------------------------------------------------------------------------
>
> Key: OWB-493
> URL: https://issues.apache.org/jira/browse/OWB-493
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Events
> Affects Versions: 1.1.0
> Reporter: David Jencks
> Assignee: Gurkan Erdogdu
> Fix For: 1.1.0
>
>
> See https://jira.jboss.org/browse/CDITCK-168
> The tck extensions.processBean.ProcessBeanTest test had a couple errors where
> ProcessProducerMethod<Cowshed, Cow> was treated as a ProcessMethod<Cowshed>
> whereas it is a ProcessMethod<Cow>, and similarly for ProcessProducerField.
> OWB seems to be subject to the same error.
> public void observeCowProcessProducerMethod(@Observes
> ProcessProducerMethod<Cowshed, Cow> event)
> is getting called correctly for the ProcessProducerMethod, but
> public void observeCowShedProccesBean(@Observes ProcessBean<Cowshed> event)
> is getting called with the same event.
> I haven't been able to figure out where the problem is.
> The corrected test is in 1.0.2.CR3
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
