You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2011/08/12 20:51:27 UTC
[jira] [Created] (OWB-603) Incorporate enhanced BeanArchive
handling of the preliminary CDI-1.1 specification
Incorporate enhanced BeanArchive handling of the preliminary CDI-1.1 specification
----------------------------------------------------------------------------------
Key: OWB-603
URL: https://issues.apache.org/jira/browse/OWB-603
Project: OpenWebBeans
Issue Type: Improvement
Components: Interceptor and Decorators
Affects Versions: 1.1.0
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: 1.2.0
This affects Interceptors, Decorators and Alternatives:
The CDI-1.0 spec defines that Interceptors, Decorators and Alternatives must only count for beans of the very the Bean Archive (BDA = the jar file) they are defined in (via beans.xml). OWB currently ignores this (there is also no TCK for it) because this behaviour is utterly broken.
The CDI-1.1 (JSR-346) EG is working on improving this:
https://issues.jboss.org/browse/CDI-18
This is work in progress, but we should stay close to the new mechanism because it's better than what we currently have.
As a first step, we shall remove our DeploymentException when the same Interceptor gets enabled in more than 1 beans.xml files on the classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Yan: [jira] [Created] (OWB-603) Incorporate enhanced BeanArchive handling of the preliminary CDI-1.1 specification
Posted by Mark Struberg <st...@yahoo.de>.
yes, I think we should get 1.1.1 out of the door the next 2 weeks anyway ;)
For now I did just commit things which improve our current behaviour in non-BDA mode with Weld.
An example: in Seam3 some interceptors are defined over and over again in each jar. This used to lead to a WebBeansConfigurationException claiming that an <interceptor> is only allowed once.
But actually that is wrong: it must only exist once in the _same_ _beans.xml_!
I'll spare the ordering and enabled stuff from CDI-1.1 for OWB-1.2.
LieGrue,
strub
--- On Fri, 8/12/11, Gurkan Erdogdu <gu...@yahoo.com> wrote:
> From: Gurkan Erdogdu <gu...@yahoo.com>
> Subject: Yan: [jira] [Created] (OWB-603) Incorporate enhanced BeanArchive handling of the preliminary CDI-1.1 specification
> To: "dev@openwebbeans.apache.org" <de...@openwebbeans.apache.org>
> Date: Friday, August 12, 2011, 7:15 PM
> >>>Should we separate owb
> 1.1 (which is an cdi 1.0 implementation) from
> >>>>early cdi 1.1 work somehow? A new branch
> perhaps?
>
> +1.
>
>
> Gurkan
>
>
>
> ________________________________
> Kimden: Joseph Bergmark <be...@apache.org>
> Kime: dev@openwebbeans.apache.org
> Gönderildiği Tarih: 12 Ağustos 2011 22:13 Cuma
> Konu: Re: [jira] [Created] (OWB-603) Incorporate enhanced
> BeanArchive handling of the preliminary CDI-1.1
> specification
>
> Should we separate owb 1.1 (which is an cdi 1.0
> implementation) from
> early cdi 1.1 work somehow? A new branch perhaps?
>
> Joe
>
> On Fri, Aug 12, 2011 at 2:51 PM, Mark Struberg (JIRA)
> <ji...@apache.org>
> wrote:
> > Incorporate enhanced BeanArchive handling of the
> preliminary CDI-1.1 specification
> >
> ----------------------------------------------------------------------------------
> >
> > Key: OWB-603
> > URL: https://issues.apache.org/jira/browse/OWB-603
> > Project: OpenWebBeans
> > Issue Type: Improvement
> > Components: Interceptor and Decorators
> > Affects Versions: 1.1.0
> > Reporter: Mark Struberg
> > Assignee: Mark Struberg
> > Fix For: 1.2.0
> >
> >
> > This affects Interceptors, Decorators and
> Alternatives:
> >
> > The CDI-1.0 spec defines that Interceptors, Decorators
> and Alternatives must only count for beans of the very the
> Bean Archive (BDA = the jar file) they are defined in (via
> beans.xml). OWB currently ignores this (there is also no TCK
> for it) because this behaviour is utterly broken.
> > The CDI-1.1 (JSR-346) EG is working on improving
> this:
> > https://issues.jboss.org/browse/CDI-18
> >
> > This is work in progress, but we should stay close to
> the new mechanism because it's better than what we currently
> have.
> >
> > As a first step, we shall remove our
> DeploymentException when the same Interceptor gets enabled
> in more than 1 beans.xml files on the classpath.
> >
> > --
> > This message is automatically generated by JIRA.
> > For more information on JIRA, see: http://www.atlassian.com/software/jira
> >
> >
> >
Yan: [jira] [Created] (OWB-603) Incorporate enhanced BeanArchive handling of the preliminary CDI-1.1 specification
Posted by Gurkan Erdogdu <gu...@yahoo.com>.
>>>Should we separate owb 1.1 (which is an cdi 1.0 implementation) from
>>>>early cdi 1.1 work somehow? A new branch perhaps?
+1.
Gurkan
________________________________
Kimden: Joseph Bergmark <be...@apache.org>
Kime: dev@openwebbeans.apache.org
Gönderildiği Tarih: 12 Ağustos 2011 22:13 Cuma
Konu: Re: [jira] [Created] (OWB-603) Incorporate enhanced BeanArchive handling of the preliminary CDI-1.1 specification
Should we separate owb 1.1 (which is an cdi 1.0 implementation) from
early cdi 1.1 work somehow? A new branch perhaps?
Joe
On Fri, Aug 12, 2011 at 2:51 PM, Mark Struberg (JIRA) <ji...@apache.org> wrote:
> Incorporate enhanced BeanArchive handling of the preliminary CDI-1.1 specification
> ----------------------------------------------------------------------------------
>
> Key: OWB-603
> URL: https://issues.apache.org/jira/browse/OWB-603
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Interceptor and Decorators
> Affects Versions: 1.1.0
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 1.2.0
>
>
> This affects Interceptors, Decorators and Alternatives:
>
> The CDI-1.0 spec defines that Interceptors, Decorators and Alternatives must only count for beans of the very the Bean Archive (BDA = the jar file) they are defined in (via beans.xml). OWB currently ignores this (there is also no TCK for it) because this behaviour is utterly broken.
> The CDI-1.1 (JSR-346) EG is working on improving this:
> https://issues.jboss.org/browse/CDI-18
>
> This is work in progress, but we should stay close to the new mechanism because it's better than what we currently have.
>
> As a first step, we shall remove our DeploymentException when the same Interceptor gets enabled in more than 1 beans.xml files on the classpath.
>
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
Re: [jira] [Created] (OWB-603) Incorporate enhanced BeanArchive
handling of the preliminary CDI-1.1 specification
Posted by Joseph Bergmark <be...@apache.org>.
Should we separate owb 1.1 (which is an cdi 1.0 implementation) from
early cdi 1.1 work somehow? A new branch perhaps?
Joe
On Fri, Aug 12, 2011 at 2:51 PM, Mark Struberg (JIRA) <ji...@apache.org> wrote:
> Incorporate enhanced BeanArchive handling of the preliminary CDI-1.1 specification
> ----------------------------------------------------------------------------------
>
> Key: OWB-603
> URL: https://issues.apache.org/jira/browse/OWB-603
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Interceptor and Decorators
> Affects Versions: 1.1.0
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 1.2.0
>
>
> This affects Interceptors, Decorators and Alternatives:
>
> The CDI-1.0 spec defines that Interceptors, Decorators and Alternatives must only count for beans of the very the Bean Archive (BDA = the jar file) they are defined in (via beans.xml). OWB currently ignores this (there is also no TCK for it) because this behaviour is utterly broken.
> The CDI-1.1 (JSR-346) EG is working on improving this:
> https://issues.jboss.org/browse/CDI-18
>
> This is work in progress, but we should stay close to the new mechanism because it's better than what we currently have.
>
> As a first step, we shall remove our DeploymentException when the same Interceptor gets enabled in more than 1 beans.xml files on the classpath.
>
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
[jira] [Updated] (OWB-603) Incorporate enhanced BeanArchive
handling of the preliminary CDI-1.1 specification
Posted by "Mark Struberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OWB-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Struberg updated OWB-603:
------------------------------
Fix Version/s: (was: 1.1.1)
1.2.0
> Incorporate enhanced BeanArchive handling of the preliminary CDI-1.1 specification
> ----------------------------------------------------------------------------------
>
> Key: OWB-603
> URL: https://issues.apache.org/jira/browse/OWB-603
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Interceptor and Decorators
> Affects Versions: 1.1.0
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 1.2.0
>
>
> This affects Interceptors, Decorators and Alternatives:
> The CDI-1.0 spec defines that Interceptors, Decorators and Alternatives must only count for beans of the very the Bean Archive (BDA = the jar file) they are defined in (via beans.xml). OWB currently ignores this (there is also no TCK for it) because this behaviour is utterly broken.
> The CDI-1.1 (JSR-346) EG is working on improving this:
> https://issues.jboss.org/browse/CDI-18
> This is work in progress, but we should stay close to the new mechanism because it's better than what we currently have.
> As a first step, we shall remove our DeploymentException when the same Interceptor gets enabled in more than 1 beans.xml files on the classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira