[weld-issues] [JBoss JIRA] (WELD-2632) Allow unwrapping of a proxied object

2020-07-24 Thread Klemen Ferjancic (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Klemen Ferjancic updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Weld /  WELD-2632  
 
 
  Allow unwrapping of a proxied object   
 

  
 
 
 
 

 
Change By: 
 Klemen Ferjancic  
 

  
 
 
 
 

 
 This is a revival of https://issues.redhat.com/browse/WELD-2245 and [https://hibernate.atlassian.net/browse/HHH-11020] for reconsideration.I am not asking for change in default behaviour but to give developer the power to override it.The setup with injected EntityManager and unwrapping the instance is quite common so I don't think it is fair to require custom workarounds for this. I understand the logic why Weld is safeguarding this to prevent escape from proxy but there are use cases like this one in JPA where you do actually want the underlying instance. I think there should be a way to tell Weld to let us do this while keeping the defaults.Something like (making this up on the fly):{color:#9e880d}@JustLetMeUnwrap{color}{color:#00}Session session {color}= em.unwrap(Session.class); ..or any developer convenient way to override the default behaviour when needed. This would also appear to be a blind spot in JPA/CDI interop at the spec level so clarification there would also be welcome.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.8#713008-sha1:1606a5c)  
 
 

 
   
 
  

[weld-issues] [JBoss JIRA] (WELD-2632) Allow unwrapping of a proxied object

2020-07-24 Thread Klemen Ferjancic (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Klemen Ferjancic created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Weld /  WELD-2632  
 
 
  Allow unwrapping of a proxied object   
 

  
 
 
 
 

 
Issue Type: 
  Feature Request  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 24/Jul/20 9:28 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Klemen Ferjancic  
 

  
 
 
 
 

 
 This is a revival of https://issues.redhat.com/browse/WELD-2245 and https://hibernate.atlassian.net/browse/HHH-11020 for reconsideration. I am not asking for change in default behaviour but to give developer the power to override it. The setup with injected EntityManager and unwrapping the instance is quite common so I don't think it is fair to require custom workarounds for this. I understand the logic why Weld is safeguarding this to prevent escape from proxy but there are use cases like this one in JPA where you do actually want the underlying instance. I think there should be a way to tell Weld to let us do this while keeping the defaults. Something like (making this up on the fly): @JustLetMeUnwrapSession session = em.unwrap(Session.class);   ..or any developer convenient way to override the default behaviour when needed.   This would also appear to be a blind spot in JPA/CDI interop at the spec level so clarification there would also be welcome.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment