Jenkins build is still unstable: OpenWebBeans-trunk » JSR-346 TCK runner #1012

[Apache Jenkins Server]

See 

Jenkins build is still unstable: OpenWebBeans-trunk #1012

[Apache Jenkins Server]

See 

OWB-983 Patch

[Daniel Cunha]

Hi guys,

I worked in a simple patch to sample. Can someone review it?

OWB-983

Thanks.

--
Daniel Cunha (soro)
Sent from my cell phone.

[jira] [Resolved] (OWB-987) improve getReference type handling

[Mark Struberg (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OWB-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Struberg resolved OWB-987.
---

   Resolution: Fixed
Fix Version/s: 1.2.7

> improve getReference type handling
> --
>
> Key: OWB-987
> URL: https://issues.apache.org/jira/browse/OWB-987
> Project: OpenWebBeans
>  Issue Type: Improvement
>Affects Versions: 1.2.6
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Minor
> Fix For: 1.2.7, 2.0.0
>
>
> If no specific bean type is given for getReference we currently use 
> bean.getBeanClass(). But this is actually wrong for producer methods and 
> producer fields as those will return the containing class.
> This is only a minor enhancement as it only hits us if we enter the 
> getEjbOrJmsProxyReference path. This gets used if we @Inject a pure EJB in 
> which case the EJB container might not even take this information into 
> account.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (OWB-987) improve getReference type handling

[Mark Struberg (JIRA)]

Mark Struberg created OWB-987:
-

 Summary: improve getReference type handling
 Key: OWB-987
 URL: https://issues.apache.org/jira/browse/OWB-987
 Project: OpenWebBeans
  Issue Type: Improvement
Affects Versions: 1.2.6
Reporter: Mark Struberg
Assignee: Mark Struberg
Priority: Minor
 Fix For: 2.0.0


If no specific bean type is given for getReference we currently use 
bean.getBeanClass(). But this is actually wrong for producer methods and 
producer fields as those will return the containing class.

This is only a minor enhancement as it only hits us if we enter the 
getEjbOrJmsProxyReference path. This gets used if we @Inject a pure EJB in 
which case the EJB container might not even take this information into account.



--
This message was sent by Atlassian JIRA
(v6.2#6252)