[weld-issues] [JBoss JIRA] (CDITCK-598) org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between p

2018-03-22 Thread ankur kathuria (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ankur kathuria commented on  CDITCK-598  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between platform and ejb specs   
 

  
 
 
 
 

 
 The proposed change fixes the test in GlassFish(Weld 3).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849)  
 
 

 
   
 

  
 

  
 

   

___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues

[weld-issues] [JBoss JIRA] (CDITCK-598) org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between p

2018-03-22 Thread Matej Novotny (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matej Novotny updated  CDITCK-598  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 CDI TCK /  CDITCK-598  
 
 
  org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between platform and ejb specs   
 

  
 
 
 
 

 
Change By: 
 Matej Novotny  
 
 
Status: 
 Pull Request Sent Resolved  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849)  
 
 

 
   
 

  
 

  
 

   

___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues

[weld-issues] [JBoss JIRA] (CDITCK-598) org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between p

2018-03-21 Thread Joseph Snyder (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joseph Snyder commented on  CDITCK-598  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between platform and ejb specs   
 

  
 
 
 
 

 
 I have asked Ankur Kathuria (he is the current Glassfish/CDI engineer) to test the proposed change.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849)  
 
 

 
   
 

  
 

  
 

   

___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues

[weld-issues] [JBoss JIRA] (CDITCK-598) org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between p

2018-03-21 Thread Matej Novotny (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Issue was automatically transitioned when Matej Novotny created pull request #160 in GitHub  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 CDI TCK /  CDITCK-598  
 
 
  org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between platform and ejb specs   
 

  
 
 
 
 

 
Change By: 
 Matej Novotny  
 
 
Status: 
 Open Pull Request Sent  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849)  
 
 

 
   
 

  
 

  
 

   

___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues

[weld-issues] [JBoss JIRA] (CDITCK-598) org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between p

2018-03-21 Thread Matej Novotny (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matej Novotny updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 CDI TCK /  CDITCK-598  
 
 
  org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between platform and ejb specs   
 

  
 
 
 
 

 
Change By: 
 Matej Novotny  
 
 
Git Pull Request: 
 https://github.com/cdi-spec/cdi-tck/pull/159, https://github.com/cdi-spec/cdi-tck/pull/160  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849)  
 
 

 
   
 

  
 

  
 

   

___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues

[weld-issues] [JBoss JIRA] (CDITCK-598) org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between p

2018-03-21 Thread Matej Novotny (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matej Novotny updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 CDI TCK /  CDITCK-598  
 
 
  org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between platform and ejb specs   
 

  
 
 
 
 

 
Change By: 
 Matej Novotny  
 
 
Fix Version/s: 
 2.1.0.Final  
 
 
Fix Version/s: 
 2.0.4.Final  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849)  
 
 

 
   
 

  
 

  
 

   

___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues

[weld-issues] [JBoss JIRA] (CDITCK-598) org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between p

2018-03-21 Thread Matej Novotny (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matej Novotny commented on  CDITCK-598  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between platform and ejb specs   
 

  
 
 
 
 

 
 Joseph Snyder if the TCK test used module instead of comp would that fix it for you?  
 
 
 
 
  toner = (Toner) InitialContext.doLookup("java:module/Toner");  
 
 
 printer = (Printer) InitialContext.doLookup("java:module/Printer");
  
 
 
 
  I see no reason why we couldn't alter the test that way and avoid the cross-spec issue. The test is focused around transactional observers so it shouldn't change a thing. Or is there something I am missing?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849)  
 
 

 
   
 

  
 

  
 

   

___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.or

[weld-issues] [JBoss JIRA] (CDITCK-598) org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between p

2017-08-01 Thread Martin Kouba (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Kouba commented on  CDITCK-598  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between platform and ejb specs   
 

  
 
 
 
 

 
 Test added to the canonical exlude list:  https://github.com/cdi-spec/cdi-tck/commit/904106be616fe615ed7f8a9b70d68c143be7976a  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.3#72005-sha1:73be91d)  
 
 

 
   
 

  
 

  
 

   

___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues

[weld-issues] [JBoss JIRA] (CDITCK-598) org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between p

2017-08-01 Thread Joseph Snyder (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joseph Snyder created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 CDI TCK /  CDITCK-598  
 
 
  org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between platform and ejb specs   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 2.0.2.Final  
 
 
Assignee: 
 Matej Novotny  
 
 
Components: 
 Tests  
 
 
Created: 
 01/Aug/17 1:32 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Joseph Snyder  
 

  
 
 
 
 

 
 org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest is failing in GlassFish because of the lookup of the ejbs in java:comp in FooObserver. Here's the code in FooObserver#init around line 58:  toner = (Toner) InitialContext.doLookup("java:comp/Toner"); printer = (Printer) InitialContext.doLookup("java:comp/Printer"); I have debugged it and the reason is that GlassFish is not populating the java:comp namespace with the ejbs. GlassFish does populate the java:module namespace so this does work:  toner = (Toner) InitialContext.doLookup("java:module/Toner"); printer = (Printer) InitialContext.doLookup("java:module/Printer"); We (at Oracle) have been having a lengthy discussion about this and have found discrepancies between the EJB spec and the platform spec. In a very simplistic summary when the ejb is in a war the EJB spec (4.4.2.1) does not identify the java:comp as a namespace that must be populated (for the ejb) while the platform spec (5.2.2) says that java:comp refers to the same namespace as java:module implying that the ejb must be able to be looked up via both the java:module and java:comp namespace. The following spec issue has been filed to evaluate of Java EE spec 5.2.2 paragraph "For historical reason ..." in relation to EJB spec portable JNDI lookup to clarify the requirement in the ej