[jira] [Comment Edited] (DELTASPIKE-1115) Entity meta data discovery works not the same as in JPA
[ https://issues.apache.org/jira/browse/DELTASPIKE-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297016#comment-15297016 ] Alexandr Smirnov edited comment on DELTASPIKE-1115 at 5/23/16 8:24 PM: --- That is. There was an idea to switch from our legacy code to the new, jpa based, without changing the qualified entity names. In this way that would be possible to make a migration step by step. Jpa works without any problem, because class path loading is limited to one jar with xml descriptor. But deltaspike jpa tried to load any Entity class. There is a solution in our case, we have to rename every entity class, But does it has any sense in general case? There should be persistence descriptor in any case. Why try to have wider search scope for deltaspike. was (Author: temaleva): That is. There was an idea to switch from our legacy code the new, jpa based, without changing the qualified entity names. In this way that would be possible to make a migration step by step. Jpa works without any problem, because class path loading is limited to one jar with xml descriptor. But deltaspike jpa tried to load any Entity class. There is a solution in our case, we have to rename every entity class, But does it has any sense in general case? There should be persistence descriptor in any case. Why try to have wider search scope for deltaspike. > Entity meta data discovery works not the same as in JPA > --- > > Key: DELTASPIKE-1115 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1115 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module, JPA-Module >Affects Versions: 1.6.0 >Reporter: Alexandr Smirnov >Priority: Minor > > In JPA, Entity metadata discovery mechanism search and loads Entity only from > one jar, where persistence.xml is found. > On the other side, deltaspike jpa/data module search the whole classpath. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-1115) Entity meta data discovery works not the same as in JPA
[ https://issues.apache.org/jira/browse/DELTASPIKE-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297016#comment-15297016 ] Alexandr Smirnov commented on DELTASPIKE-1115: -- That is. There was an idea to switch from our legacy code the new, jpa based, without changing the qualified entity names. In this way that would be possible to make a migration step by step. Jpa works without any problem, because class path loading is limited to one jar with xml descriptor. But deltaspike jpa tried to load any Entity class. There is a solution in our case, we have to rename every entity class, But does it has any sense in general case? There should be persistence descriptor in any case. Why try to have wider search scope for deltaspike. > Entity meta data discovery works not the same as in JPA > --- > > Key: DELTASPIKE-1115 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1115 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module, JPA-Module >Affects Versions: 1.6.0 >Reporter: Alexandr Smirnov >Priority: Minor > > In JPA, Entity metadata discovery mechanism search and loads Entity only from > one jar, where persistence.xml is found. > On the other side, deltaspike jpa/data module search the whole classpath. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DELTASPIKE-1115) Entity meta data discovery works not the same as in JPA
Alexandr Smirnov created DELTASPIKE-1115: Summary: Entity meta data discovery works not the same as in JPA Key: DELTASPIKE-1115 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1115 Project: DeltaSpike Issue Type: Improvement Components: Data-Module, JPA-Module Affects Versions: 1.6.0 Reporter: Alexandr Smirnov Priority: Minor In JPA, Entity metadata discovery mechanism search and loads Entity only from one jar, where persistence.xml is found. On the other side, deltaspike jpa/data module search the whole classpath. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DELTASPIKE-691) Weld 2.x support
Alexandr Smirnov created DELTASPIKE-691: --- Summary: Weld 2.x support Key: DELTASPIKE-691 URL: https://issues.apache.org/jira/browse/DELTASPIKE-691 Project: DeltaSpike Issue Type: Wish Reporter: Alexandr Smirnov java.lang.IncompatibleClassChangeError: Class org.apache.deltaspike.core.util.bean.ImmutablePassivationCapableBean does not implement the requested interface javax.enterprise.inject.spi.BeanAttributes at org.jboss.weld.bean.attributes.ExternalBeanAttributesFactory.validateStereotypes(ExternalBeanAttributesFactory.java:75) When trying to start with Weld 2.2.1 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (DELTASPIKE-691) Weld 2.x support
[ https://issues.apache.org/jira/browse/DELTASPIKE-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Smirnov updated DELTASPIKE-691: Component/s: Data-Module Environment: arquillian-weld-se-embedded-1.1 unit test Affects Version/s: 1.0.1 Weld 2.x support Key: DELTASPIKE-691 URL: https://issues.apache.org/jira/browse/DELTASPIKE-691 Project: DeltaSpike Issue Type: Wish Components: Data-Module Affects Versions: 1.0.1 Environment: arquillian-weld-se-embedded-1.1 unit test Reporter: Alexandr Smirnov java.lang.IncompatibleClassChangeError: Class org.apache.deltaspike.core.util.bean.ImmutablePassivationCapableBean does not implement the requested interface javax.enterprise.inject.spi.BeanAttributes at org.jboss.weld.bean.attributes.ExternalBeanAttributesFactory.validateStereotypes(ExternalBeanAttributesFactory.java:75) When trying to start with Weld 2.2.1 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (DELTASPIKE-691) Weld 2.x support
[ https://issues.apache.org/jira/browse/DELTASPIKE-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14101157#comment-14101157 ] Alexandr Smirnov commented on DELTASPIKE-691: - But this exception mean, that libraries are not binary compatible. And the reason is that deltaspike depends on geronimo-jcdi_1.0_spec which is not binary compatible with cdi-api 1.1/1.2 from Jboss. Weld 2.x support Key: DELTASPIKE-691 URL: https://issues.apache.org/jira/browse/DELTASPIKE-691 Project: DeltaSpike Issue Type: Wish Components: Data-Module Affects Versions: 1.0.1 Environment: arquillian-weld-se-embedded-1.1 unit test Reporter: Alexandr Smirnov java.lang.IncompatibleClassChangeError: Class org.apache.deltaspike.core.util.bean.ImmutablePassivationCapableBean does not implement the requested interface javax.enterprise.inject.spi.BeanAttributes at org.jboss.weld.bean.attributes.ExternalBeanAttributesFactory.validateStereotypes(ExternalBeanAttributesFactory.java:75) When trying to start with Weld 2.2.1 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (DELTASPIKE-691) Weld 2.x support
[ https://issues.apache.org/jira/browse/DELTASPIKE-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14101264#comment-14101264 ] Alexandr Smirnov commented on DELTASPIKE-691: - Exactly, I mean that. You compile (using OWB profile) against the api (geronimo cdi api 1.0) which is not binary compatible with the another api (jboss cdi api 1.2). That is why you have another profile in parent-code pom to run test in Weld. Unfortunately (for me) only the code compiled with default profile is deployed to maven central. So I have to build deltaspike myself with activated Weld profile and deploy it to our local repository. No problem, I can do it. But I would like to create issue on this point, so we have artifacts in maven central built with Weld profile activated. Weld 2.x support Key: DELTASPIKE-691 URL: https://issues.apache.org/jira/browse/DELTASPIKE-691 Project: DeltaSpike Issue Type: Wish Components: Data-Module Affects Versions: 1.0.1 Environment: arquillian-weld-se-embedded-1.1 unit test Reporter: Alexandr Smirnov java.lang.IncompatibleClassChangeError: Class org.apache.deltaspike.core.util.bean.ImmutablePassivationCapableBean does not implement the requested interface javax.enterprise.inject.spi.BeanAttributes at org.jboss.weld.bean.attributes.ExternalBeanAttributesFactory.validateStereotypes(ExternalBeanAttributesFactory.java:75) When trying to start with Weld 2.2.1 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (DELTASPIKE-691) Weld 2.x support
[ https://issues.apache.org/jira/browse/DELTASPIKE-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14101285#comment-14101285 ] Alexandr Smirnov commented on DELTASPIKE-691: - https://issues.apache.org/jira/browse/DELTASPIKE-693 Weld 2.x support Key: DELTASPIKE-691 URL: https://issues.apache.org/jira/browse/DELTASPIKE-691 Project: DeltaSpike Issue Type: Wish Components: Data-Module Affects Versions: 1.0.1 Environment: arquillian-weld-se-embedded-1.1 unit test Reporter: Alexandr Smirnov java.lang.IncompatibleClassChangeError: Class org.apache.deltaspike.core.util.bean.ImmutablePassivationCapableBean does not implement the requested interface javax.enterprise.inject.spi.BeanAttributes at org.jboss.weld.bean.attributes.ExternalBeanAttributesFactory.validateStereotypes(ExternalBeanAttributesFactory.java:75) When trying to start with Weld 2.2.1 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (DELTASPIKE-693) Deploy the deltaspike version built with Weld maven profile into maven central
[ https://issues.apache.org/jira/browse/DELTASPIKE-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Smirnov updated DELTASPIKE-693: Description: Only deltaspike built with a default profile OWB deployed to maven central. Weld users have to build deltaspike they self (with activated Weld profile ). was: Only deltaspike built with a default profile OWN deployed to maven central. Weld users have to build deltaspike they self (with activated Weld profile ). Deploy the deltaspike version built with Weld maven profile into maven central -- Key: DELTASPIKE-693 URL: https://issues.apache.org/jira/browse/DELTASPIKE-693 Project: DeltaSpike Issue Type: Wish Components: Build Affects Versions: 1.0.1, 1.0.2 Reporter: Alexandr Smirnov Only deltaspike built with a default profile OWB deployed to maven central. Weld users have to build deltaspike they self (with activated Weld profile ). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (DELTASPIKE-691) Weld 2.x support
[ https://issues.apache.org/jira/browse/DELTASPIKE-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14101873#comment-14101873 ] Alexandr Smirnov commented on DELTASPIKE-691: - You are right, sorry. And thank you for your help. I appreciate it so much. The wrong dependency in my case comes from myfaces-api 2.3, not from deltaspike. myfaces has geronimo-jcdi_1.0_spec in compiled scope. I have to manually extract it. I will write to myfaces project. Weld 2.x support Key: DELTASPIKE-691 URL: https://issues.apache.org/jira/browse/DELTASPIKE-691 Project: DeltaSpike Issue Type: Wish Components: Data-Module Affects Versions: 1.0.1 Environment: arquillian-weld-se-embedded-1.1 unit test Reporter: Alexandr Smirnov java.lang.IncompatibleClassChangeError: Class org.apache.deltaspike.core.util.bean.ImmutablePassivationCapableBean does not implement the requested interface javax.enterprise.inject.spi.BeanAttributes at org.jboss.weld.bean.attributes.ExternalBeanAttributesFactory.validateStereotypes(ExternalBeanAttributesFactory.java:75) When trying to start with Weld 2.2.1 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (DELTASPIKE-693) Deploy the deltaspike version built with Weld maven profile into maven central
[ https://issues.apache.org/jira/browse/DELTASPIKE-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Smirnov closed DELTASPIKE-693. --- Deploy the deltaspike version built with Weld maven profile into maven central -- Key: DELTASPIKE-693 URL: https://issues.apache.org/jira/browse/DELTASPIKE-693 Project: DeltaSpike Issue Type: Wish Components: Build Affects Versions: 1.0.1, 1.0.2 Reporter: Alexandr Smirnov Only deltaspike built with a default profile OWB deployed to maven central. Weld users have to build deltaspike they self (with activated Weld profile ). -- This message was sent by Atlassian JIRA (v6.2#6252)
