[weld-issues] [JBoss JIRA] (WELD-1950) CDI Producer Injection Point Divergence glassfish3.1.2/weblogic 12 and tomee 1.7.1

2015-05-16 Thread Nuno Godinho de Matos (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nuno Godinho de Matos created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Weld /  WELD-1950 
 
 
 
  CDI Producer Injection Point Divergence glassfish3.1.2/weblogic 12 and tomee 1.7.1  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 1.1.14.Final 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Class Beans (Managed and Session) 
 
 
 

Created:
 

 16/May/15 1:35 PM 
 
 
 

Environment:
 

 Windows 7 , JDK 64 - Glassfish 3.1.2.2 and Tomcat EE 1.7.1 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Nuno Godinho de Matos 
 
 
 
 
 
 
 
 
 
 
HI There, 
I've filed a bug under: https://issues.apache.org/jira/browse/TOMEE-1586 
But most likely belongs to weld, where weld passed and Injection Point with the attributes of the incorrect injeciton point. 
The divergence Producer (Injectionpoint) behavior is described in more detail on the TomEE original bug report.  
You have a sample application to reproduce this issue under: 

[weld-issues] [JBoss JIRA] (CDITCK-482) SessionContextListenerShutdownTest relies on non-specified behaviour

2015-05-16 Thread Mark Struberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Struberg created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 CDI TCK /  CDITCK-482 
 
 
 
  SessionContextListenerShutdownTest relies on non-specified behaviour  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Feature Request 
 
 
 

Affects Versions:
 

 1.2.4.Final 
 
 
 

Assignee:
 
 Tomas Remes 
 
 
 

Created:
 

 16/May/15 1:58 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Mark Struberg 
 
 
 
 
 
 
 
 
 
 
SessionContextListenerShutdownTest relies on sessionDestroyed getting invoked on undeploy. But this is actually not defined by the servlet spec. Many containers really don't call this. Instead they serialize away the Session to disc or to another cluster node and then de-serialize them back again. In which case the Session continues as nothing has happened. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment