June 2017 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-708) Serialization problems in section "1.3.1. JSF example".

by Martin Andersson (JIRA)

[ https://issues.jboss.org/browse/CDI-708?page=com.atlassian.jira.plugin.sy... ] Martin Andersson commented on CDI-708: -------------------------------------- Actually, CriteriaQuery is serializable. JPA 2.1, section "6.9 Query Execution": bq. CriteriaQuery, CriteriaUpdate, and CriteriaDelete objects must be serializable. > Serialization problems in section "1.3.1. JSF example". > ------------------------------------------------------- > > Key: CDI-708 > URL: https://issues.jboss.org/browse/CDI-708 > Project: CDI Specification Issues > Issue Type: Bug > Components: Concepts > Affects Versions: 2.0 .Final > Reporter: Martin Andersson > > Section "1.3.1. JSF example" provide an example of a class {{Login}}, that saves in its state an {{EntityManager}} reference and two {{Parameter}} references. > The JPA specification does not say that a {{Parameter}} instance is serializable. > This is also true for the {{EntityManager}} reference which is {{@Dependent}} (see section "1.3.3. Java EE component environment example"). JPA does not specify that the {{EntityManager}} is serializable and the EJB specification only specifies serialization semantics for passivation-enabled {{@Stateful}} EJB:s (which encourages the bean provider to not mark an {{EntityManager}} reference as transient, see EJB §4.2.1). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-708) Serialization problems in section "1.3.1. JSF example".

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-708?page=com.atlassian.jira.plugin.sy... ] Martin Kouba commented on CDI-708: ---------------------------------- Good catch! For the record, this also applies to {{CriteriaQuery<User> query}} field and the resource bean for {{EntityManager}} is defined in 1.3.3 as {{@Dependent}}: {code:java} @Produces @PersistenceContext(unitName="UserData") @Users EntityManager userDatabaseEntityManager; {code} (in fact, containers are not required to support resources with scope other than {{@Dependent}}) > Serialization problems in section "1.3.1. JSF example". > ------------------------------------------------------- > > Key: CDI-708 > URL: https://issues.jboss.org/browse/CDI-708 > Project: CDI Specification Issues > Issue Type: Bug > Components: Concepts > Affects Versions: 2.0 .Final > Reporter: Martin Andersson > > Section "1.3.1. JSF example" provide an example of a class {{Login}}, that saves in its state an {{EntityManager}} reference and two {{Parameter}} references. > The JPA specification does not say that a {{Parameter}} instance is serializable. > This is also true for the {{EntityManager}} reference which is {{@Dependent}} (see section "1.3.3. Java EE component environment example"). JPA does not specify that the {{EntityManager}} is serializable and the EJB specification only specifies serialization semantics for passivation-enabled {{@Stateful}} EJB:s (which encourages the bean provider to not mark an {{EntityManager}} reference as transient, see EJB §4.2.1). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-708) Serialization problems in section "1.3.1. JSF example".

by Martin Andersson (JIRA)

Martin Andersson created CDI-708: ------------------------------------ Summary: Serialization problems in section "1.3.1. JSF example". Key: CDI-708 URL: https://issues.jboss.org/browse/CDI-708 Project: CDI Specification Issues Issue Type: Bug Components: Concepts Affects Versions: 2.0 .Final Reporter: Martin Andersson Section "1.3.1. JSF example" provide an example of a class {{Login}}, that saves in its state an {{EntityManager}} reference and two {{Parameter}} references. The JPA specification does not say that a {{Parameter}} instance is serializable. This is also true for the {{EntityManager}} reference which is {{@Dependent}} (see section "1.3.3. Java EE component environment example"). JPA does not specify that the {{EntityManager}} is serializable and the EJB specification only specifies serialization semantics for passivation-enabled {{@Stateful}} EJB:s (which encourages the bean provider to not mark an {{EntityManager}} reference as transient, see EJB §4.2.1). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-707) InjectionPointConfigurator #addQualifier etc does not define the @Default qualifier handling

by Mark Struberg (JIRA)

Mark Struberg created CDI-707: --------------------------------- Summary: InjectionPointConfigurator #addQualifier etc does not define the @Default qualifier handling Key: CDI-707 URL: https://issues.jboss.org/browse/CDI-707 Project: CDI Specification Issues Issue Type: Bug Reporter: Mark Struberg 3.8 defines the handling of @Default if no other qualifier is applied. So what happens if someone removes all Qualifiers? Or if someone adds some other Qualifier but still keep @Default around? We should clarify what happens in those cases. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-706) ProducerConfigurator has no method to configure the InjectionPoints

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/CDI-706?page=com.atlassian.jira.plugin.sy... ] Matej Novotny commented on CDI-706: ----------------------------------- Also one more thing... bq. So it is effectively not possible to properly *create* a Producer with this Configurator. Yes, it not. Configurators were meant as a way to alter existing entities (producers in this case; only during {{ProcessProducer}}). If you wish to create a new one, I think {{BeanConfigurator}} is a better fit as there you define a way to produce such beans from scratch. > ProducerConfigurator has no method to configure the InjectionPoints > ------------------------------------------------------------------- > > Key: CDI-706 > URL: https://issues.jboss.org/browse/CDI-706 > Project: CDI Specification Issues > Issue Type: Bug > Reporter: Mark Struberg > > Producer has not only produce() and dispose() but also > {noformat} > Set<InjectionPoint> getInjectionPoints() > {noformat} > But this information cannot be set with the ProducerConfigurator. > So it is effectively not possible to properly create a Producer with this Configurator. > Or did I miss some trick? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-706) ProducerConfigurator has no method to configure the InjectionPoints

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/CDI-706?page=com.atlassian.jira.plugin.sy... ] Matej Novotny commented on CDI-706: ----------------------------------- Hey Mark, not sure you missed a trick, but I think you missed CDI-673. We purposely removed those methods for reasons described in the issue above. > ProducerConfigurator has no method to configure the InjectionPoints > ------------------------------------------------------------------- > > Key: CDI-706 > URL: https://issues.jboss.org/browse/CDI-706 > Project: CDI Specification Issues > Issue Type: Bug > Reporter: Mark Struberg > > Producer has not only produce() and dispose() but also > {noformat} > Set<InjectionPoint> getInjectionPoints() > {noformat} > But this information cannot be set with the ProducerConfigurator. > So it is effectively not possible to properly create a Producer with this Configurator. > Or did I miss some trick? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-706) ProducerConfigurator has no method to configure the InjectionPoints

by Mark Struberg (JIRA)

Mark Struberg created CDI-706: --------------------------------- Summary: ProducerConfigurator has no method to configure the InjectionPoints Key: CDI-706 URL: https://issues.jboss.org/browse/CDI-706 Project: CDI Specification Issues Issue Type: Bug Reporter: Mark Struberg Producer has not only produce() and dispose() but also {noformat} Set<InjectionPoint> getInjectionPoints() {noformat} But this information cannot be set with the ProducerConfigurator. So it is effectively not possible to properly create a Producer with this Configurator. Or did I miss some trick? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

Proposal regarding CDI-705

by Antoine Sabot-Durand

Hi all, It seems that we introduced a mistake in CDI 2.0 regarding its alignment with JTA. See https://issues.jboss.org/browse/CDI-705 Transactional observer bound to BEFORE_COMPLETION shouldn’t be triggered if the transaction is rolled back or marked for roll back. I suggest that we skip the matching test in the TCK [1] and allow impl to skip this rule and align on JTA. JTA should be corrected in a coming MR. Thanks for your feedback Antoine [1] https://github.com/cdi-spec/cdi-tck/blob/master/impl/src/main/java/org...

7 years, 4 months

2
2
0 / 0

Proposal for CDI-705

by Antoine Sabot-Durand

Hi all, It seems that we introduced a mistake in CDI 2.0 regarding its alignment with JTA. See issues.jboss.org/browse/CDI-705 Transactional observer bound to BEFORE_COMPLETION shouldn’t be triggered if the transaction is rolled back or marked for roll back. I suggest that we skip the matching test in the TCK [1] and allow impl to skip this rule and align on JTA. JTA should be corrected in a coming MR. Thanks for your feedback [1] github.com/cdi-s...t.java Antoine

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-705) BEFORE_COMPLETION Transactional observer is notified for transaction which is marked for rollback

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-705?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-705: ------------------------------------- Fix Version/s: 2.0.1 > BEFORE_COMPLETION Transactional observer is notified for transaction which is marked for rollback > ------------------------------------------------------------------------------------------------- > > Key: CDI-705 > URL: https://issues.jboss.org/browse/CDI-705 > Project: CDI Specification Issues > Issue Type: Bug > Components: Events > Affects Versions: 2.0 .Final > Reporter: Tomas Remes > Fix For: 2.0.1 > > > In {{10.4.5. Transactional observer methods}} CDI spec states: > {quote} > If the transaction is in progress, but javax.transaction.Synchronization callback cannot be > registered due to the transaction being already marked for rollback or in state where > javax.transaction.Synchronization callbacks cannot be registered, the before completion, after completion and after failure observer methods are notified at the same time as other observers, but after_success observer methods get skipped. > {quote} > This doesn't conform to JTA spec, which says in {{3.3.2 Transaction Synchronization}}: > {quote} > The Synchronization.beforeCompletion method is called prior to the > start of the two-phase transaction commit process. This call is executed with > the transaction context of the transaction that is being committed. > {quote} > So the before_completion transactional observer shouldn't be notified for transaction marked for rollback. > The method {{Synchronization.beforeCompletion}} is actually not called at WildFly and GlassFish app servers for transaction which is marked for rollback. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev June 2017