December 2013 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-386) Two examples in section 5.2.4 contradict the rules of the same section

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-386?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-386: ------------------------------------- Labels: 12-02-13-EGM cdi-1.1-mr (was: cdi-1.1-mr) > Two examples in section 5.2.4 contradict the rules of the same section > ---------------------------------------------------------------------- > > Key: CDI-386 > URL: https://issues.jboss.org/browse/CDI-386 > Project: CDI Specification Issues > Issue Type: Bug > Affects Versions: 1.1.PFD > Reporter: Marko Lukša > Assignee: Marko Lukša > Labels: 12-02-13-EGM, cdi-1.1-mr > > The examples in section 5.2.4 state that bean {{Dao<T extends Persistent>}} is eligible for injection into both {{Dao<Order>}} and {{Dao<User>}}, but according to the rules stated in the same section this isn't true. > Also note that the spec doesn't state explicitly that {{Order extends Persistent}} and {{User extends Persistent}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (CDI-381) Additional implementations of Request Context

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-381?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-381: ------------------------------------- Labels: 12-02-13-EGM cdi-1.1-mr (was: cdi-1.1-mr) > Additional implementations of Request Context > --------------------------------------------- > > Key: CDI-381 > URL: https://issues.jboss.org/browse/CDI-381 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Joseph Snyder > Priority: Minor > Labels: 12-02-13-EGM, cdi-1.1-mr > > Suppose another spec wanted to define when @RequestScoped applied to its > operations, how would it do that? The javadocs for @RequestScoped seem to > be an exhaustive list, not allowing the scope to be used in other contexts. > The javadocs need to indicate that the scope can be active at other > times beyond what the spec describes. It can be tricky to do that in a > way that doesn't allow people to implement the currently defined scopes > incorrectly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (CDI-77) Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-77?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand updated CDI-77: ------------------------------------ Labels: 12-02-13-EGM cdi-1.1-mr (was: cdi-1.1-mr) > Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans > ---------------------------------------------------------------------------------------------------- > > Key: CDI-77 > URL: https://issues.jboss.org/browse/CDI-77 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Resolution > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Labels: 12-02-13-EGM, cdi-1.1-mr > Fix For: TBD > > > for example > class Foo { > @Inject Bar bar; > } > class bar { > @Inject Foo foo; > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (CDI-379) Clarify life cycle of RequestScoped

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-379?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-379: ------------------------------------- Labels: 12-02-13-EGM cdi-1.1-mr (was: cdi-1.1-mr) > Clarify life cycle of RequestScoped > ----------------------------------- > > Key: CDI-379 > URL: https://issues.jboss.org/browse/CDI-379 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Joseph Snyder > Priority: Minor > Labels: 12-02-13-EGM, cdi-1.1-mr > > This is one of the areas where the CDI spec could be clearer. It defines > the points where "some" request scope is active, and where "some" request > scope is destroyed, but it doesn't clearly state what the span of a particular > request context is. You sort of have to work backwards and figure it out. > Update the spec to indicate when a particular request scope is > created, what operations it's active during, and when it's destroyed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (CDI-382) Clarify interceptors are not associated with the result of a producer method/field

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-382?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-382: ------------------------------------- Labels: 12-02-13-EGM cdi-1.1-mr (was: cdi-1.1-mr) > Clarify interceptors are not associated with the result of a producer method/field > ---------------------------------------------------------------------------------- > > Key: CDI-382 > URL: https://issues.jboss.org/browse/CDI-382 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Interceptors > Affects Versions: 1.1.PFD > Reporter: Martin Kouba > Labels: 12-02-13-EGM, cdi-1.1-mr > > The interceptors part from CDI-59 resolution [1] is missing in the final version of the spec, probably lost during the Interceptors section transfer to the Interceptors 1.2 spec. > [1] https://github.com/cdi-spec/cdi/pull/110 > "Interceptors are not associated with the return value of a producer method or the current value of a producer field." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (CDI-370) Expand @RequestScoped and @SessionScoped to account for WebSocket

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-370?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-370: ------------------------------------- Labels: cdi-1.1-mr investigate (was: cdi-1.1-mr) > Expand @RequestScoped and @SessionScoped to account for WebSocket > ----------------------------------------------------------------- > > Key: CDI-370 > URL: https://issues.jboss.org/browse/CDI-370 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Joseph Snyder > Labels: cdi-1.1-mr, investigate > > We've been testing injection into a WebSocket endpoint. > @ReqestScoped objects are usable within the @OnOpen callback. This is because this object is executed within a valid request scope. > However if you try to use the injected object from within the @OnMessage callback you get a Weld error: > SEVERE: org.jboss.weld.context.ContextNotActiveException: > WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped > Can the definition of when @RequestScoped is active be expanded to include a WebSocket @OnMessage callback? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (CDI-377) automatic JSR-330 annotation processing problematic

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-377?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-377: ------------------------------------- Labels: cdi-1.1-mr investigate (was: cdi-1.1-mr) > automatic JSR-330 annotation processing problematic > --------------------------------------------------- > > Key: CDI-377 > URL: https://issues.jboss.org/browse/CDI-377 > Project: CDI Specification Issues > Issue Type: Bug > Components: Java EE integration > Affects Versions: 1.1.PFD > Environment: glassfish-4 > Reporter: Reuben Pasquini > Labels: cdi-1.1-mr, investigate > Fix For: TBD > > > The jsr-330 dependency injection annotations (javax.inject.*) find use in javase environments using IOC packages like guice. > Adding a dependency on a jar that uses guice or whatever in a javase environment > to a war deployed to a jee7 container > results in CDI processing annotated classes intended for > app-managed injection. See this ticket filed with guava for a concrete example: > https://code.google.com/p/guava-libraries/issues/detail?id=1433 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (CDI-395) Public fields in extensions should not be allowed

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-395?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-395: ------------------------------------- Labels: cdi-1.1-mr investigate (was: cdi-1.1-mr) > Public fields in extensions should not be allowed > ------------------------------------------------- > > Key: CDI-395 > URL: https://issues.jboss.org/browse/CDI-395 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Portable Extensions > Affects Versions: 1.1.PFD > Reporter: Marko Lukša > Labels: cdi-1.1-mr, investigate > > Since the container must provide an @ApplicationScoped bean for every extension and since a proxy must be injected into injection points requesting this bean, it should be clear that extensions should not be allowed to have public fields. The spec doesn't specify this explicitly, but it should - like it does for non-dependent managed beans. > The container should treat this as a definition error, otherwise people may end up accessing these public fields of extensions and getting weird errors. > See also WELD-1474 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (CDI-389) Revert CDI-85

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-389?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-389: ------------------------------------- Labels: (was: cdi-1.1-mr) > Revert CDI-85 > ------------- > > Key: CDI-389 > URL: https://issues.jboss.org/browse/CDI-389 > Project: CDI Specification Issues > Issue Type: Bug > Affects Versions: 1.1.PFD > Reporter: Marko Lukša > Fix For: 1.1.1 (Proposed) > > > Bullet 4 of section 5.2.4 should be reverted back from: > {quote} > the required type parameter is an actual type, the bean type parameter is a type variable and the actual type is assignable *from* > the upper bound, if any, of the type variable, or > {quote} > to > {quote} > the required type parameter is an actual type, the bean type parameter is a type variable and the actual type is assignable *to* > the upper bound, if any, of the type variable, or > {quote} > See discussion at http://lists.jboss.org/pipermail/cdi-dev/2013-July/004290.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (CDI-397) Clarify Section 6.6.3 regarding singletons

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-397?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-397: ------------------------------------- Fix Version/s: 1.1.1 (Proposed) (was: TBD) > Clarify Section 6.6.3 regarding singletons > ------------------------------------------ > > Key: CDI-397 > URL: https://issues.jboss.org/browse/CDI-397 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 1.1.FD > Reporter: Jozef Hartinger > Priority: Minor > Labels: cdi-1.1-mr > Fix For: 1.1.1 (Proposed) > > > The section 6.6.3 Passivation capable dependencies states: > {quote} > all singleton beans are passivation capable dependencies > {quote} > Clearly the specification intents to address *singleton session beans* but the current wording does not make that explicit and users confuse this line and consider javax.inject.Singleton-scoped beans also to be passivation capable dependencies. > The spec should instead say that: > {quote} > all singleton *session* beans are passivation capable dependencies > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev December 2013