Contexts & Dependency Injection for Java

CDI EG meeting 12/16/2013 notes on CDI 1.2

Posted by Antoine Sabot-Durand on Dec 16, 2013 | Comments

The following people assisted this meeting :

  • Mark Struberg (ms)

  • Joseph Bergmark(jb)

  • Jozef Hartinger (jh)

  • Martin Kouba (mk)

  • JJ Snyder (jj)

  • Phil Zampino (pz)

  • Antoine Sabot-Durand (asd)

Proposed Agenda

The following agenda was proposed

  1. Discussion on the last ticket pending : CDI-395 Public fields in extensions should not be allowed

  2. Last second ticket

  3. Next step for the MR.

Discussion on CDI-395

We were waiting on implementation feedback on this point. jh told us that there was too much risk to create retro-compatibility issues. So it was decided to remove CDI-395 from MR.

Last minute issues

Jira Description Decision Note

CDI-408

bean-discovery-mode="annotated" and Producers/Observers in @Dependent beans

in MR

CDI-410

@RequestScoped Javadoc outdated

in MR

CDI-388

Session bean specialization example is not valid

in MR

CDI-376

BeanManager#getProducerFactory return type differs between API and spec

in MR

CDI-411

CDI conversation activation conflicts with the Servlet spec

Pending

needs some test before decicing if we can include it in MR. Test leaded by jh

Next Step

The list is now closed (except for 411) It’s accessible here and in Jira. The Maintenance Release will be officially launch on the 6th january week. By then, work and discussion can start on the ticket chosen for this MR.

Conclusion of EG preparation on CDI 1.2

Posted by Antoine Sabot-Durand on Dec 16, 2013 | Comments

Updated on 01/07/2014

We finished to deal with the list of 28 Jira we planned to introduce or not in MR. So 24 of them will be in MR and 4 won’t. The list is also accessible on Jira.

Jira Description Decision Note

CDI-413

Update outdated license

in MR

CDI-408

bean-discovery-mode="annotated" and Producers/Observers in @Dependent beans

in MR

CDI-410

@RequestScoped Javadoc outdated

in MR

CDI-388

Session bean specialization example is not valid

in MR

CDI-376

BeanManager#getProducerFactory return type differs between API and spec

in MR

CDI-377

automatic JSR-330 annotation processing problematic

in MR

Mention needed and perhaps a new feature

CDI-380

Clarify SessionScoped

in MR

We should be less descriptive and like for CDI-381 add a general statement telling that other spec/extensions can change the behavior of built-in scope

CDI-372

clarify behavior of implicit bean archive

in MR

The notion of Bean Archive is introduce in Chapter 12, we should do an introduction before

CDI-320

Clarify whether ProcessAnnotatedType should be fired for annotations

in MR

According to pm it shouldn’t and we should clarify this

CDI-318

@WithAnnotations types can appear on any supertype

in MR

Mainly Javadoc correction on @WithAnnotation

CDI-280

behavior of CDI bean @Specializes session bean is undefined

in MR

could benefit some clarification

CDI-220

Clarify interceptors are not associated with the result of a producer method/field

in MR

CDI-405

Reword the description of @RequestScoped and @ApplicationScoped in section 2.4.1

in MR

CDI-401

Clarify the meaning of "bean class local view"

in MR

CDI-398

Clarify that an array with a variable component type or parameterized component type containing wildcards is not a valid bean type

in MR

CDI-392

Clarify when the operations of BeanManager can be called

in MR

CDI-386

Two examples in section 5.2.4 contradict the rules of the same section

in MR

CDI-382

Clarify interceptors are not associated with the result of a producer method/field

in MR

CDI-381

Additional implementations of Request Context

in MR

we should add general statement telling that extension can change the behavior of built-in scope

CDI-406

Make stereotypes bean defining annotations

in MR

CDI-404

adding bean-defining annotations for Interceptor while setting bean-discovery-mode="annotated"

in MR

CDI-389

Revert CDI-85

in MR

we revert to CDI 1.0 behavior but we will have to propose something better in CDI 2.0

CDI-397

Clarify Section 6.6.3 regarding singletons

in MR

we should go a little beyond and check all occurrences of "singleton" in the spec to clarify if it’s an singleton session bean or a singleton scope

CDI-411

CDI conversation activation conflicts with the Servlet spec

in MR

Solution exist at different level. We should at least put a mention in the spec and o something at impl level

CDI-379

Clarify life cycle of RequestScoped

out MR

each spec should detail how they stick to built-in scope

CDI-370

Expand @RequestScoped and @SessionScoped to account for WebSocket

out MR

It’s the responsibility of Websocket spec. We should ensure they take the point before closing the ticket

CDI-77

Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans

out MR

Container doesn’t have to support this : the ticket should be closed

CDI-395

Public fields in extensions should not be allowed

out MR

it can bring backwards compatibility problem to correct this issue. We should see if impls allows it today. If it’s not the case it could be safely added to the MR

CDI EG meeting 12/09/2013 notes on CDI 1.2 MR

Posted by Antoine Sabot-Durand on Dec 09, 2013 | Comments

The following people assisted this meeting :

  • Pete Muir (pm)

  • Jozef Hartinger (jh)

  • Martin Kouba (mk)

  • JJ Snyder (jj)

  • Antoine Sabot-Durand (asd)

Proposed Agenda

The following agenda was proposed

  1. Issues discussion : 6 issues where proposed

  2. Back on CDI-377 (automatic JSR-330 annotation processing problematic)

Issues discussion

The discussion around the proposed ticket was quite straight forward. The result is in the table below

Jira Description Decision Note

CDI-380

Clarify SessionScoped

in MR

We should be less descriptive and like for CDI-381 add a general statement telling that other spec/extensions can change the behavior of built-in scope

CDI-372

clarify behavior of implicit bean archive

in MR

The notion of Bean Archive is introduce in Chapter 12, we should do an introduction before

CDI-320

Clarify whether ProcessAnnotatedType should be fired for annotations

in MR

According to pm it shouldn’t and we should clarify this

CDI-318

@WithAnnotations types can appear on any supertype

in MR

Mainly Javadoc correction on @WithAnnotation

CDI-280

behavior of CDI bean @Specializes session bean is undefined

in MR

could benefit some clarification

CDI-220

Clarify interceptors are not associated with the result of a producer method/field

in MR

Back on CDI-377 (automatic JSR-330 annotation processing problematic)

This issue will be fixed in implementation and the sepc will mention something about recommendation to provide default exclusion list for most framework. We still have to discuss if we introduce a jar exclusion mechanism in the spec or this will be based on existing package exclusion.

Conclusion

We finished to deal with the list of Jira tickets we planned to introduce or not in MR. As we have a little more time it was decided to re-open the list for some more on next meeting

CDI EG meeting 12/02/2013 notes on CDI 1.2 MR

Posted by Antoine Sabot-Durand on Dec 02, 2013 | Comments

The following people assisted this meeting :

  • Pete Muir (pm)

  • Mark Struberg (ms)

  • Jozef Hartinger (jh)

  • Joseph Bergmark (jb)

  • Phil Zampino (pz) (Java EE EG member)

  • JJ Snyder (jj)

  • Antoine Sabot-Durand (asd)

Proposed Agenda

The following agenda was proposed

  1. Feed back on Java EE EG conf call we had on tuesday

  2. Issues discussion : 9 issues where proposed

Feedback on Java EE EG meeting

To sum up :

  • Java EE EG is ok with our MR roadmap :

    • 16th Dec - list of issues complete

    • 6th Jan - Maintenance review starts

    • 7th March - Maintenance review ends

    • 21st March - Maintenance ballot ends

  • According to JCP rules on update, we are going for CDI 1.2 (not 1.1.1)

  • Regarding ticket CDI-370 (Expand @RequestScoped and @SessionScoped to account for WebSocket) we agree that job should be done in Websocket Spec. So asd will work with Stuart Douglas to bring this point to the Websocket EG. The direct consequence for our MR is that CDI-370 is not in and should be closed after we check that Websocket EG got the point on their side.

  • We also talk about classloader issue that were raised during CDI-377 (automatic JSR-330 annotation processing problematic). EG members agreed that it’s a good point but very difficult to resolve. It could only be solve in a major EE release.

Issues discussion

The discussion around the proposed ticket was quite straight forward. The result is in the table below

Jira Description Decision Note

CDI-405

Reword the description of @RequestScoped and @ApplicationScoped in section 2.4.1

in MR

CDI-401

Clarify the meaning of "bean class local view"

in MR

CDI-398

Clarify that an array with a variable component type or parameterized component type containing wildcards is not a valid bean type

in MR

CDI-392

Clarify when the operations of BeanManager can be called

in MR

CDI-386

Two examples in section 5.2.4 contradict the rules of the same section

in MR

CDI-382

Clarify interceptors are not associated with the result of a producer method/field

in MR

CDI-381

Additional implementations of Request Context

in MR

we should add general statement telling that extension can change the behavior of built-in scope

CDI-379

Clarify life cycle of RequestScoped

out MR

each spec should detail how they stick to built-in scope

CDI-77

Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans

out MR

Container doesn’t have to support this : the ticket should be closed

Conclusion

EG has still 8 issues to discuss (inluding CDI-377). We should close the list as planned on mid-december.

Tag Cloud