[jira] Commented: (OWB-472) archive centric beans.xml enabling
[ https://issues.apache.org/jira/browse/OWB-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12994151#comment-12994151 ] Gerhard Petracek commented on OWB-472: -- i agree with mark! archive centric beans.xml enabling --- Key: OWB-472 URL: https://issues.apache.org/jira/browse/OWB-472 Project: OpenWebBeans Issue Type: Improvement Components: Injection and Lookup Reporter: Jacquelle Leggett Assignee: Mark Struberg Attachments: patch.txt Original Estimate: 336h Remaining Estimate: 336h This issue was discussed in great detail in June (http://mail-archives.apache.org/mod_mbox/openwebbeans-dev/201006.mbox/browser) on the developers forum. The title of the thread is problems with lack of archive-centric BeanManager. The main problem is described below (snippet from discussion): ...Our current design does not permit either of the following scenarions, AFAICT: b.jar and c.jar both enable the interceptor defined in a.jar (treated as a duplicate) Exactly one of b.jar and c.jar enables the interceptor defined in a.jar (ends up enabled for beans from either archive if enabled in one -- this is in the more troubling neighborhood)... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Fwd: [jira] Commented: (OWB-472) archive centric beans.xml enabling
https://issues.jboss.org/browse/CDI-18 My personal fear is that this will quickly lead to lots of follow up failures like one can currently see in glassfish and JBossAS. For getting this done if e.g. an EE server needs to implement the CDI-1.0 spec then this can still be provided via a custom ScannerService Impl, isn't? LieGrue, strub --- On Sun, 2/13/11, Eric Covener cove...@gmail.com wrote: From: Eric Covener cove...@gmail.com Subject: Fwd: [jira] Commented: (OWB-472) archive centric beans.xml enabling To: dev@openwebbeans.apache.org Date: Sunday, February 13, 2011, 8:52 PM Isn't the current code pretty non-intrusive and no behavior change by default? Is there something like a draft to cite that shows what overhaul in this area is due in 1.1? -- Forwarded message -- From: Mark Struberg (JIRA) j...@apache.org Date: Sun, Feb 13, 2011 at 3:40 PM Subject: [jira] Commented: (OWB-472) archive centric beans.xml enabling To: dev@openwebbeans.apache.org [ https://issues.apache.org/jira/browse/OWB-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12994150#comment-12994150 ] Mark Struberg commented on OWB-472: --- I fear we need to rollback the commits. The problem with this is that the whole BDA definition is UTTERLY broken in the spec. This resulted in a spec change which is due to 1.1. See CDI-18 for more information. By implementing the same sh**t than Weld currently has (they are forced to, but hey, we are not the RI ;) we just corrupt any normal modus operandi. Comments are welcome. archive centric beans.xml enabling --- Key: OWB-472 URL: https://issues.apache.org/jira/browse/OWB-472 Project: OpenWebBeans Issue Type: Improvement Components: Injection and Lookup Reporter: Jacquelle Leggett Assignee: Mark Struberg Attachments: patch.txt Original Estimate: 336h Remaining Estimate: 336h This issue was discussed in great detail in June (http://mail-archives.apache.org/mod_mbox/openwebbeans-dev/201006.mbox/browser) on the developers forum. The title of the thread is problems with lack of archive-centric BeanManager. The main problem is described below (snippet from discussion): ...Our current design does not permit either of the following scenarions, AFAICT: b.jar and c.jar both enable the interceptor defined in a.jar (treated as a duplicate) Exactly one of b.jar and c.jar enables the interceptor defined in a.jar (ends up enabled for beans from either archive if enabled in one -- this is in the more troubling neighborhood)... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Eric Covener cove...@gmail.com
Re: Fwd: [jira] Commented: (OWB-472) archive centric beans.xml enabling
+1 regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/2/13 Mark Struberg strub...@yahoo.de https://issues.jboss.org/browse/CDI-18 My personal fear is that this will quickly lead to lots of follow up failures like one can currently see in glassfish and JBossAS. For getting this done if e.g. an EE server needs to implement the CDI-1.0 spec then this can still be provided via a custom ScannerService Impl, isn't? LieGrue, strub --- On Sun, 2/13/11, Eric Covener cove...@gmail.com wrote: From: Eric Covener cove...@gmail.com Subject: Fwd: [jira] Commented: (OWB-472) archive centric beans.xml enabling To: dev@openwebbeans.apache.org Date: Sunday, February 13, 2011, 8:52 PM Isn't the current code pretty non-intrusive and no behavior change by default? Is there something like a draft to cite that shows what overhaul in this area is due in 1.1? -- Forwarded message -- From: Mark Struberg (JIRA) j...@apache.org Date: Sun, Feb 13, 2011 at 3:40 PM Subject: [jira] Commented: (OWB-472) archive centric beans.xml enabling To: dev@openwebbeans.apache.org [ https://issues.apache.org/jira/browse/OWB-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12994150#comment-12994150 ] Mark Struberg commented on OWB-472: --- I fear we need to rollback the commits. The problem with this is that the whole BDA definition is UTTERLY broken in the spec. This resulted in a spec change which is due to 1.1. See CDI-18 for more information. By implementing the same sh**t than Weld currently has (they are forced to, but hey, we are not the RI ;) we just corrupt any normal modus operandi. Comments are welcome. archive centric beans.xml enabling --- Key: OWB-472 URL: https://issues.apache.org/jira/browse/OWB-472 Project: OpenWebBeans Issue Type: Improvement Components: Injection and Lookup Reporter: Jacquelle Leggett Assignee: Mark Struberg Attachments: patch.txt Original Estimate: 336h Remaining Estimate: 336h This issue was discussed in great detail in June ( http://mail-archives.apache.org/mod_mbox/openwebbeans-dev/201006.mbox/browser ) on the developers forum. The title of the thread is problems with lack of archive-centric BeanManager. The main problem is described below (snippet from discussion): ...Our current design does not permit either of the following scenarions, AFAICT: b.jar and c.jar both enable the interceptor defined in a.jar (treated as a duplicate) Exactly one of b.jar and c.jar enables the interceptor defined in a.jar (ends up enabled for beans from either archive if enabled in one -- this is in the more troubling neighborhood)... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Eric Covener cove...@gmail.com
Re: [jira] Commented: (OWB-472) archive centric beans.xml enabling
On Sun, Feb 13, 2011 at 4:12 PM, Gerhard gerhard.petra...@gmail.com wrote: yes - it's non-intrusive because i fixed it. Non-intrusive in terms of technical rationale to call for a revert, not non-intrusive in terms of you had to refactor to use trunk in an appserver. however, we have a spi (ScannerService) for such additional features. We have many SPIs and Plugins, and in trunk we have a set that can satisfy the requirements of CDI 1.0.
[jira] Commented: (OWB-472) archive centric beans.xml enabling
[ https://issues.apache.org/jira/browse/OWB-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12994169#comment-12994169 ] Gurkan Erdogdu commented on OWB-472: AFAIK, BDA has been enabled as plugin or SPI. Therefore, current implementation may not affect any other parts, because it has not been enabled. archive centric beans.xml enabling --- Key: OWB-472 URL: https://issues.apache.org/jira/browse/OWB-472 Project: OpenWebBeans Issue Type: Improvement Components: Injection and Lookup Reporter: Jacquelle Leggett Assignee: Mark Struberg Attachments: patch.txt Original Estimate: 336h Remaining Estimate: 336h This issue was discussed in great detail in June (http://mail-archives.apache.org/mod_mbox/openwebbeans-dev/201006.mbox/browser) on the developers forum. The title of the thread is problems with lack of archive-centric BeanManager. The main problem is described below (snippet from discussion): ...Our current design does not permit either of the following scenarions, AFAICT: b.jar and c.jar both enable the interceptor defined in a.jar (treated as a duplicate) Exactly one of b.jar and c.jar enables the interceptor defined in a.jar (ends up enabled for beans from either archive if enabled in one -- this is in the more troubling neighborhood)... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OWB-472) archive centric beans.xml enabling
[ https://issues.apache.org/jira/browse/OWB-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12994179#comment-12994179 ] Jacquelle Leggett commented on OWB-472: --- I understand Mark's viewpoint, but I do not understand why there is a need to rollback changes. As I mentioned in a previous post, it is useful to have the ability to limit the scope of modifiers (interceptors, decorators, alternatives). This function is disabled by default. There were not many core changes. From memory, InjectionResolver was the only core class with significant changes. ScannerService was also modified to allow information about class location to be passed to the core. The rest of the changes were refactoring or config related. Overall, I was impressed at how straightforward the changes were to add this function...it's a credit to the design of OWB. archive centric beans.xml enabling --- Key: OWB-472 URL: https://issues.apache.org/jira/browse/OWB-472 Project: OpenWebBeans Issue Type: Improvement Components: Injection and Lookup Reporter: Jacquelle Leggett Assignee: Mark Struberg Attachments: patch.txt Original Estimate: 336h Remaining Estimate: 336h This issue was discussed in great detail in June (http://mail-archives.apache.org/mod_mbox/openwebbeans-dev/201006.mbox/browser) on the developers forum. The title of the thread is problems with lack of archive-centric BeanManager. The main problem is described below (snippet from discussion): ...Our current design does not permit either of the following scenarions, AFAICT: b.jar and c.jar both enable the interceptor defined in a.jar (treated as a duplicate) Exactly one of b.jar and c.jar enables the interceptor defined in a.jar (ends up enabled for beans from either archive if enabled in one -- this is in the more troubling neighborhood)... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OWB-472) archive centric beans.xml enabling
[ https://issues.apache.org/jira/browse/OWB-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12994211#comment-12994211 ] Gurkan Erdogdu commented on OWB-472: I do not see a reason to rollback the changes. Everyhing in OWB has been written as plugin. Therefore if you do not wish to use any plugin functioanality disabling is enough. archive centric beans.xml enabling --- Key: OWB-472 URL: https://issues.apache.org/jira/browse/OWB-472 Project: OpenWebBeans Issue Type: Improvement Components: Injection and Lookup Reporter: Jacquelle Leggett Assignee: Mark Struberg Attachments: patch.txt Original Estimate: 336h Remaining Estimate: 336h This issue was discussed in great detail in June (http://mail-archives.apache.org/mod_mbox/openwebbeans-dev/201006.mbox/browser) on the developers forum. The title of the thread is problems with lack of archive-centric BeanManager. The main problem is described below (snippet from discussion): ...Our current design does not permit either of the following scenarions, AFAICT: b.jar and c.jar both enable the interceptor defined in a.jar (treated as a duplicate) Exactly one of b.jar and c.jar enables the interceptor defined in a.jar (ends up enabled for beans from either archive if enabled in one -- this is in the more troubling neighborhood)... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira