[weld-issues] [JBoss JIRA] (WELD-2534) Log a warning when starting multiple SE containers and resetting SingletonProvider

2018-10-03 Thread Matej Novotny (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matej Novotny created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Weld /  WELD-2534  
 
 
  Log a warning when starting multiple SE containers and resetting SingletonProvider   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Affects Versions: 
 3.0.5.Final  
 
 
Assignee: 
 Matej Novotny  
 
 
Components: 
 Java SE Support  
 
 
Created: 
 03/Oct/18 6:47 AM  
 
 
Fix Versions: 
 3.1.0.Final  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Matej Novotny  
 

  
 
 
 
 

 
 Follows up on WELD-2247. We want to log warning when multiple SE instances were created and SingletonProvider was reset. This can happen if user supplies their own singleton provider implementation.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
   

[weld-issues] [JBoss JIRA] (WELD-2534) Log a warning when starting multiple SE containers and resetting SingletonProvider

2018-10-03 Thread Matej Novotny (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matej Novotny updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Weld /  WELD-2534  
 
 
  Log a warning when starting multiple SE containers and resetting SingletonProvider   
 

  
 
 
 
 

 
Change By: 
 Matej Novotny  
 
 
Priority: 
 Major Minor  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505)  
 
 

 
   
 

  
 

  
 

   

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

[weld-issues] [JBoss JIRA] (WELD-2534) Log a warning when starting multiple SE containers and resetting SingletonProvider

2018-11-25 Thread Matej Novotny (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matej Novotny commented on  WELD-2534  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Log a warning when starting multiple SE containers and resetting SingletonProvider   
 

  
 
 
 
 

 
 Martin Kouba do you happen to remember what we meant by this issue? Looking at linked issue, we rejected that one and logging seems to make no sense ATM because RegistrySingletonProvider is enforced anyway in SE (static block is invoked when the class is loaded by CL). I would suggest to close this one as well, WDYT?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505)  
 
 

 
   
 

  
 

  
 

   

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

[weld-issues] [JBoss JIRA] (WELD-2534) Log a warning when starting multiple SE containers and resetting SingletonProvider

2018-11-27 Thread Martin Kouba (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Kouba commented on  WELD-2534  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Log a warning when starting multiple SE containers and resetting SingletonProvider   
 

  
 
 
 
 

 
 I'm fine with closing this issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505)  
 
 

 
   
 

  
 

  
 

   

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

[weld-issues] [JBoss JIRA] (WELD-2534) Log a warning when starting multiple SE containers and resetting SingletonProvider

2018-11-27 Thread Matej Novotny (Jira)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matej Novotny closed an issue as Rejected  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Closing as rejected. This logging doesn't make sense to me with current setup where, in SE, we always override singleton provider with our implementation.  
 

  
 
 
 
 

 
 Weld /  WELD-2534  
 
 
  Log a warning when starting multiple SE containers and resetting SingletonProvider   
 

  
 
 
 
 

 
Change By: 
 Matej Novotny  
 
 
Status: 
 Open Closed  
 
 
Fix Version/s: 
 3.1.0.Beta1  
 
 
Fix Version/s: 
 3.1.0.Final  
 
 
Resolution: 
 Rejected  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505)