[jira] [Resolved] (DELTASPIKE-839) Data module test deployments pack individual classes instead of JARs
[
https://issues.apache.org/jira/browse/DELTASPIKE-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Cunha (soro) resolved DELTASPIKE-839.
Resolution: Fixed
> Data module test deployments pack individual classes instead of JARs
>
>
> Key: DELTASPIKE-839
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-839
> Project: DeltaSpike
> Issue Type: Bug
> Components: Data-Module, Tests
>Affects Versions: 1.2.1
>Reporter: Ron Smeral
>Assignee: Daniel Cunha (soro)
>Priority: Minor
>
> Tests of all other modules pack dependencies using ShrinkWrap's
> {{addLibrary}}, but data module tests add api and impl classes individually
> using {{addClass}}. This reduces the fidelity of the tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-942) DeltaSpike fails to start with corrupted persistence.xml file.
[
https://issues.apache.org/jira/browse/DELTASPIKE-942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Cunha (soro) resolved DELTASPIKE-942.
Resolution: Fixed
DeltaSpike fails to start with corrupted persistence.xml file.
--
Key: DELTASPIKE-942
URL: https://issues.apache.org/jira/browse/DELTASPIKE-942
Project: DeltaSpike
Issue Type: Improvement
Components: Data-Module
Affects Versions: 1.4.1
Environment: * Java version: 1.8.0_40, vendor: Oracle Corporation
* Windows 7 Enterprise
* Apache Maven 3.2.3
Reporter: Grzegorz Demecki
Assignee: Daniel Cunha (soro)
Labels: easyfix
Attachments: DELTASPIKE-942-bug-showcase.zip
h4. Details
Please see attached sample web application and run it via:
{code} mvn clean compile jetty:run {code}
At startup we can see huge stack trace that tells literally nothing.
{code:java}
2015-07-01 16:38:50.076:WARN:oeja.ServletContainerInitializersStarter:main:
org.jboss.weld.exceptions.DefinitionException: Exception List with 1
exceptions:|Exception 0 :|java.lang.RuntimeException: Failed initializing
mapping files
at
org.apache.deltaspike.data.impl.meta.unit.PersistenceUnitReader.extractMappings(PersistenceUnitReader.java:82)
at
org.apache.deltaspike.data.impl.meta.unit.PersistenceUnitReader.lookupUnits(PersistenceUnitReader.java:54)
...
{code}
Whereas the exception should look like:
{code:java}
javax.servlet.ServletException: Caused by:
javax.persistence.PersistenceException: [PersistenceUnit: netadminPU] Unable
to resolve named mapping-file [META-INF/jpql/named-queries.xml]
{code}
_Because corruption is about pointing out to a not-existing mapping file
named {{named-queries.xml}}_
h4. Known workarounds
# Of course we can fix the corrupted {{persistence.xml}} file, by removing
line:
{{mapping-fileMETA-INF/jpql/named-queries.xml/mapping-file}}
# We can also remove dependency to deltaspike-data from {{pom.xml}} as it
solves the issue
Because then we got perfectly clear and correct message that tells us what
is wrong with {{persistene.xml}}.
For further details, please see file *README.md* inside attached application.
BTW: Why does the DeltaSpike parse persistence.xml at application startup?
Shouldn't this file be parsed with a lazy manner, at first usage of the
EntityManagerFactory?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-853) Use @Stereotype for interface/enum discovery
[ https://issues.apache.org/jira/browse/DELTASPIKE-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) resolved DELTASPIKE-853. Resolution: Fixed Use @Stereotype for interface/enum discovery Key: DELTASPIKE-853 URL: https://issues.apache.org/jira/browse/DELTASPIKE-853 Project: DeltaSpike Issue Type: Task Reporter: Jozef Hartinger Assignee: Daniel Cunha (soro) In several places DeltaSpike uses ProcessAnnotatedType to discover interfaces/enum provided by the application. These interfaces/enums are usually annotated with a marker annotation, e.g.: * @MessageBundle * @View/@Folder * @Repository * most likely others This works fine in explicit bean archives, where PAT is fired for each and every interface/enum within the archive. In CDI 1.1+ implicit bean archives, this won't work however as PAT is only fired for classes with a bean defining annotation. One option to make these extensions work in CDI 1.2 environment is to add @Stereotype to the marker annotations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (DELTASPIKE-965) EntityRepository.save() is broken for entities with String ID
[
https://issues.apache.org/jira/browse/DELTASPIKE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Cunha (soro) reassigned DELTASPIKE-965:
--
Assignee: Daniel Cunha (soro)
EntityRepository.save() is broken for entities with String ID
-
Key: DELTASPIKE-965
URL: https://issues.apache.org/jira/browse/DELTASPIKE-965
Project: DeltaSpike
Issue Type: Bug
Components: Data-Module
Affects Versions: 1.4.2
Reporter: Harald Wellmann
Assignee: Daniel Cunha (soro)
Priority: Blocker
Fix For: 1.4.3
EntityRepository.save() generates illegal SQL when the entity identity is of
String type.
This is a regression introduced in 1.4.2 with
{{org.apache.deltaspike.data.impl.handler.CdiQueryInvocationContext.countCheck(Object)}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-965) EntityRepository.save() is broken for entities with String ID
[
https://issues.apache.org/jira/browse/DELTASPIKE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643025#comment-14643025
]
Daniel Cunha (soro) commented on DELTASPIKE-965:
It's weird, this method was created because before we had a problem with String
ID.
If you can to see the deltaspike-dev list, Akm had this problem and we resolve
in 1.4.2.
I saw your comments in GitHub and we can improve the method, really.
But, I tested it and work fine.
I put this new test:
https://github.com/danielsoro/deltaspike/commit/24d6f86cd3a19a656281e162979560e1a917f6ff
Please, add a test that fail in your repository, will be more easy to fix it.
Thank you [~hwellmann]
EntityRepository.save() is broken for entities with String ID
-
Key: DELTASPIKE-965
URL: https://issues.apache.org/jira/browse/DELTASPIKE-965
Project: DeltaSpike
Issue Type: Bug
Components: Data-Module
Affects Versions: 1.4.2
Reporter: Harald Wellmann
Priority: Blocker
Fix For: 1.4.3
EntityRepository.save() generates illegal SQL when the entity identity is of
String type.
This is a regression introduced in 1.4.2 with
{{org.apache.deltaspike.data.impl.handler.CdiQueryInvocationContext.countCheck(Object)}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-965) EntityRepository.save() is broken for entities with String ID
[
https://issues.apache.org/jira/browse/DELTASPIKE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643255#comment-14643255
]
Daniel Cunha (soro) commented on DELTASPIKE-965:
If all test pass.. I think that we need to provide better tests to coverage
your problem.
Try create a sample e share it.. will be more easy to fix it.
Thank you [~hwellmann]
EntityRepository.save() is broken for entities with String ID
-
Key: DELTASPIKE-965
URL: https://issues.apache.org/jira/browse/DELTASPIKE-965
Project: DeltaSpike
Issue Type: Bug
Components: Data-Module
Affects Versions: 1.4.2
Reporter: Harald Wellmann
Assignee: Harald Wellmann
Priority: Blocker
Fix For: 1.4.3
EntityRepository.save() generates illegal SQL when the entity identity is of
String type.
This is a regression introduced in 1.4.2 with
{{org.apache.deltaspike.data.impl.handler.CdiQueryInvocationContext.countCheck(Object)}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-965) EntityRepository.save() is broken for entities with String ID
[
https://issues.apache.org/jira/browse/DELTASPIKE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643178#comment-14643178
]
Daniel Cunha (soro) commented on DELTASPIKE-965:
Yes, really necessary.
Before we used PersistecenUnitUtil#getIdentify
We had this problem:
http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/file/n4661005/CascadeRefreshGradleTestProject.zip
You have 2 entity where ID isn't auto generated
the problem is: he set ID of the parent and ID of the children. you call the
save of the entityRepository, entityRepository.save call merge, because for it,
it isn't a new Entity.
We used PersistenceUnitUtil for check it, but see the javadoc for it:
http://docs.oracle.com/javaee/6/api/javax/persistence/PersistenceUnitUtil.html#getIdentifier%28java.lang.Object%29
In discussion with Gerhard we found a solution for it:
i guess the only portable check is EntityManager#contains and if it returns
false a #load with the id if the id is available, the part with #contains
just to be faster with entities which are really loaded by the em, well -
instead of #load a count query would be better to avoid that it really loads
the entity.
then we changed it.
For me works fine, I didn't have any problem with it. ATM.
But, your change is cool, more expressive, please.. push direct in repository
or I can do it, if you prefer. :)
EntityRepository.save() is broken for entities with String ID
-
Key: DELTASPIKE-965
URL: https://issues.apache.org/jira/browse/DELTASPIKE-965
Project: DeltaSpike
Issue Type: Bug
Components: Data-Module
Affects Versions: 1.4.2
Reporter: Harald Wellmann
Assignee: Daniel Cunha (soro)
Priority: Blocker
Fix For: 1.4.3
EntityRepository.save() generates illegal SQL when the entity identity is of
String type.
This is a regression introduced in 1.4.2 with
{{org.apache.deltaspike.data.impl.handler.CdiQueryInvocationContext.countCheck(Object)}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-943) Provide add() methods instead of save() methods in EntityRepository
[ https://issues.apache.org/jira/browse/DELTASPIKE-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) resolved DELTASPIKE-943. Resolution: Won't Fix You can to extend EntityRepository and create your method add. For us, save make more sense to have in API. Thank you. Provide add() methods instead of save() methods in EntityRepository --- Key: DELTASPIKE-943 URL: https://issues.apache.org/jira/browse/DELTASPIKE-943 Project: DeltaSpike Issue Type: Improvement Components: JPA-Module Affects Versions: 1.4.1 Environment: JPA Reporter: Robin Roos Assignee: Daniel Cunha (soro) Priority: Minor The semantics of Repository is to model a Collection of persistent objects. There is no need to add() an object to a Collection if it is already in that Collection. By providing save() methods you lead developers to invoke save() on objects which they got from the Repository. This is (usually) inappropriate. Please provide add() methods to parallel the save() method signatures. Ideally the save() methods would be deprecated. Even if the save() methods remain, IDE inspections can then be configured to forbid their invocation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-943) Provide add() methods instead of save() methods in EntityRepository
[ https://issues.apache.org/jira/browse/DELTASPIKE-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) updated DELTASPIKE-943: --- Issue Type: Improvement (was: Bug) Provide add() methods instead of save() methods in EntityRepository --- Key: DELTASPIKE-943 URL: https://issues.apache.org/jira/browse/DELTASPIKE-943 Project: DeltaSpike Issue Type: Improvement Components: JPA-Module Affects Versions: 1.4.1 Environment: JPA Reporter: Robin Roos Assignee: Daniel Cunha (soro) Priority: Minor The semantics of Repository is to model a Collection of persistent objects. There is no need to add() an object to a Collection if it is already in that Collection. By providing save() methods you lead developers to invoke save() on objects which they got from the Repository. This is (usually) inappropriate. Please provide add() methods to parallel the save() method signatures. Ideally the save() methods would be deprecated. Even if the save() methods remain, IDE inspections can then be configured to forbid their invocation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-942) DeltaSpike fails to start with corrupted persistence.xml file.
[
https://issues.apache.org/jira/browse/DELTASPIKE-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14629614#comment-14629614
]
Daniel Cunha (soro) commented on DELTASPIKE-942:
Ok! I'll check soon.
DeltaSpike fails to start with corrupted persistence.xml file.
--
Key: DELTASPIKE-942
URL: https://issues.apache.org/jira/browse/DELTASPIKE-942
Project: DeltaSpike
Issue Type: Bug
Components: Data-Module
Affects Versions: 1.4.1
Environment: * Java version: 1.8.0_40, vendor: Oracle Corporation
* Windows 7 Enterprise
* Apache Maven 3.2.3
Reporter: Grzegorz Demecki
Assignee: Daniel Cunha (soro)
Labels: easyfix
Attachments: DELTASPIKE-942-bug-showcase.zip
h4. Details
Please see attached sample web application and run it via:
{code} mvn clean compile jetty:run {code}
At startup we can see huge stack trace that tells literally nothing.
{code:java}
2015-07-01 16:38:50.076:WARN:oeja.ServletContainerInitializersStarter:main:
org.jboss.weld.exceptions.DefinitionException: Exception List with 1
exceptions:|Exception 0 :|java.lang.RuntimeException: Failed initializing
mapping files
at
org.apache.deltaspike.data.impl.meta.unit.PersistenceUnitReader.extractMappings(PersistenceUnitReader.java:82)
at
org.apache.deltaspike.data.impl.meta.unit.PersistenceUnitReader.lookupUnits(PersistenceUnitReader.java:54)
...
{code}
Whereas the exception should look like:
{code:java}
javax.servlet.ServletException: Caused by:
javax.persistence.PersistenceException: [PersistenceUnit: netadminPU] Unable
to resolve named mapping-file [META-INF/jpql/named-queries.xml]
{code}
_Because corruption is about pointing out to a not-existing mapping file
named {{named-queries.xml}}_
h4. Known workarounds
# Of course we can fix the corrupted {{persistence.xml}} file, by removing
line:
{{mapping-fileMETA-INF/jpql/named-queries.xml/mapping-file}}
# We can also remove dependency to deltaspike-data from {{pom.xml}} as it
solves the issue
Because then we got perfectly clear and correct message that tells us what
is wrong with {{persistene.xml}}.
For further details, please see file *README.md* inside attached application.
BTW: Why does the DeltaSpike parse persistence.xml at application startup?
Shouldn't this file be parsed with a lazy manner, at first usage of the
EntityManagerFactory?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (DELTASPIKE-948) CdiQueryInvocationContext#isNew isn't portable across jpa providers
Daniel Cunha (soro) created DELTASPIKE-948: -- Summary: CdiQueryInvocationContext#isNew isn't portable across jpa providers Key: DELTASPIKE-948 URL: https://issues.apache.org/jira/browse/DELTASPIKE-948 Project: DeltaSpike Issue Type: Improvement Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) Ww use PersisteceUnitUnitl for it, however - see the javadoc for it: http://docs.oracle.com/javaee/6/api/javax/persistence/PersistenceUnitUtil.html#getIdentifier%28java.lang.Object%29 Solution: I guess the only portable check is EntityManager#contains and if it returns false a #load with the id if the id is available, the part with #contains just to be faster with entities which are really loaded by the em, well - instead of #load a count query would be better to avoid that it really loads the entity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-948) CdiQueryInvocationContext#isNew isn't portable across jpa providers
[ https://issues.apache.org/jira/browse/DELTASPIKE-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) updated DELTASPIKE-948: --- Description: We use PersisteceUnitUnitl for it, however - see the javadoc for it: http://docs.oracle.com/javaee/6/api/javax/persistence/PersistenceUnitUtil.html#getIdentifier%28java.lang.Object%29 Solution: I guess the only portable check is EntityManager#contains and if it returns false a #load with the id if the id is available, the part with #contains just to be faster with entities which are really loaded by the em, well - instead of #load a count query would be better to avoid that it really loads the entity. was: Ww use PersisteceUnitUnitl for it, however - see the javadoc for it: http://docs.oracle.com/javaee/6/api/javax/persistence/PersistenceUnitUtil.html#getIdentifier%28java.lang.Object%29 Solution: I guess the only portable check is EntityManager#contains and if it returns false a #load with the id if the id is available, the part with #contains just to be faster with entities which are really loaded by the em, well - instead of #load a count query would be better to avoid that it really loads the entity. CdiQueryInvocationContext#isNew isn't portable across jpa providers --- Key: DELTASPIKE-948 URL: https://issues.apache.org/jira/browse/DELTASPIKE-948 Project: DeltaSpike Issue Type: Improvement Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) We use PersisteceUnitUnitl for it, however - see the javadoc for it: http://docs.oracle.com/javaee/6/api/javax/persistence/PersistenceUnitUtil.html#getIdentifier%28java.lang.Object%29 Solution: I guess the only portable check is EntityManager#contains and if it returns false a #load with the id if the id is available, the part with #contains just to be faster with entities which are really loaded by the em, well - instead of #load a count query would be better to avoid that it really loads the entity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-948) CdiQueryInvocationContext#isNew isn't portable across jpa providers
[ https://issues.apache.org/jira/browse/DELTASPIKE-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) updated DELTASPIKE-948: --- Fix Version/s: 1.4.2 CdiQueryInvocationContext#isNew isn't portable across jpa providers --- Key: DELTASPIKE-948 URL: https://issues.apache.org/jira/browse/DELTASPIKE-948 Project: DeltaSpike Issue Type: Improvement Components: Data-Module Affects Versions: 1.4.1 Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) Fix For: 1.4.2 We use PersisteceUnitUnitl for it, however - see the javadoc for it: http://docs.oracle.com/javaee/6/api/javax/persistence/PersistenceUnitUtil.html#getIdentifier%28java.lang.Object%29 Solution: I guess the only portable check is EntityManager#contains and if it returns false a #load with the id if the id is available, the part with #contains just to be faster with entities which are really loaded by the em, well - instead of #load a count query would be better to avoid that it really loads the entity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-948) CdiQueryInvocationContext#isNew isn't portable across jpa providers
[ https://issues.apache.org/jira/browse/DELTASPIKE-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) updated DELTASPIKE-948: --- Component/s: Data-Module CdiQueryInvocationContext#isNew isn't portable across jpa providers --- Key: DELTASPIKE-948 URL: https://issues.apache.org/jira/browse/DELTASPIKE-948 Project: DeltaSpike Issue Type: Improvement Components: Data-Module Affects Versions: 1.4.1 Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) Fix For: 1.4.2 We use PersisteceUnitUnitl for it, however - see the javadoc for it: http://docs.oracle.com/javaee/6/api/javax/persistence/PersistenceUnitUtil.html#getIdentifier%28java.lang.Object%29 Solution: I guess the only portable check is EntityManager#contains and if it returns false a #load with the id if the id is available, the part with #contains just to be faster with entities which are really loaded by the em, well - instead of #load a count query would be better to avoid that it really loads the entity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-948) CdiQueryInvocationContext#isNew isn't portable across jpa providers
[ https://issues.apache.org/jira/browse/DELTASPIKE-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) updated DELTASPIKE-948: --- Affects Version/s: 1.4.1 CdiQueryInvocationContext#isNew isn't portable across jpa providers --- Key: DELTASPIKE-948 URL: https://issues.apache.org/jira/browse/DELTASPIKE-948 Project: DeltaSpike Issue Type: Improvement Components: Data-Module Affects Versions: 1.4.1 Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) Fix For: 1.4.2 We use PersisteceUnitUnitl for it, however - see the javadoc for it: http://docs.oracle.com/javaee/6/api/javax/persistence/PersistenceUnitUtil.html#getIdentifier%28java.lang.Object%29 Solution: I guess the only portable check is EntityManager#contains and if it returns false a #load with the id if the id is available, the part with #contains just to be faster with entities which are really loaded by the em, well - instead of #load a count query would be better to avoid that it really loads the entity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-948) CdiQueryInvocationContext#isNew isn't portable across jpa providers
[ https://issues.apache.org/jira/browse/DELTASPIKE-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) resolved DELTASPIKE-948. Resolution: Fixed CdiQueryInvocationContext#isNew isn't portable across jpa providers --- Key: DELTASPIKE-948 URL: https://issues.apache.org/jira/browse/DELTASPIKE-948 Project: DeltaSpike Issue Type: Improvement Components: Data-Module Affects Versions: 1.4.1 Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) Fix For: 1.4.2 We use PersisteceUnitUnitl for it, however - see the javadoc for it: http://docs.oracle.com/javaee/6/api/javax/persistence/PersistenceUnitUtil.html#getIdentifier%28java.lang.Object%29 Solution: I guess the only portable check is EntityManager#contains and if it returns false a #load with the id if the id is available, the part with #contains just to be faster with entities which are really loaded by the em, well - instead of #load a count query would be better to avoid that it really loads the entity. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-871) save() and findByxxx() in same transaction gives constraint violation exception
[ https://issues.apache.org/jira/browse/DELTASPIKE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14610192#comment-14610192 ] Daniel Cunha (soro) commented on DELTASPIKE-871: Hi [~mdkamaruzzaman], I'll close it If you cannot reproduce and doesn't have some sample to show, but reopen if you have this problem again or have some sample to us. We'll to be here to hear you when necessary. Thank you for reporting. save() and findByxxx() in same transaction gives constraint violation exception --- Key: DELTASPIKE-871 URL: https://issues.apache.org/jira/browse/DELTASPIKE-871 Project: DeltaSpike Issue Type: Bug Components: Data-Module Affects Versions: 1.2.0 Environment: Windows-7, Java-8, Netbeans-8.0.2 Reporter: Md Kamaruzzaman Assignee: Daniel Cunha (soro) It seems like when in the same EJB transaction, save() and findByxxx() is called, then delta-spike inserts the entity twice [once in save() and other time in findByxxx()] and gives a constraint violation exception. After some debuggin, it seems like save() gives a INSERT query in DB and findByxxx() method calls a flush which again gives the same INSERT query in DB [INSERT query from save() is not removed from EntityManager] and gives constraint violation exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-871) save() and findByxxx() in same transaction gives constraint violation exception
[ https://issues.apache.org/jira/browse/DELTASPIKE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) resolved DELTASPIKE-871. Resolution: Cannot Reproduce save() and findByxxx() in same transaction gives constraint violation exception --- Key: DELTASPIKE-871 URL: https://issues.apache.org/jira/browse/DELTASPIKE-871 Project: DeltaSpike Issue Type: Bug Components: Data-Module Affects Versions: 1.2.0 Environment: Windows-7, Java-8, Netbeans-8.0.2 Reporter: Md Kamaruzzaman Assignee: Daniel Cunha (soro) It seems like when in the same EJB transaction, save() and findByxxx() is called, then delta-spike inserts the entity twice [once in save() and other time in findByxxx()] and gives a constraint violation exception. After some debuggin, it seems like save() gives a INSERT query in DB and findByxxx() method calls a flush which again gives the same INSERT query in DB [INSERT query from save() is not removed from EntityManager] and gives constraint violation exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-673) CdiQueryInvocationContext#isNew does not work well with OpenJpa and detached entities
[
https://issues.apache.org/jira/browse/DELTASPIKE-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Cunha (soro) updated DELTASPIKE-673:
---
Fix Version/s: 1.4.2
CdiQueryInvocationContext#isNew does not work well with OpenJpa and detached
entities
-
Key: DELTASPIKE-673
URL: https://issues.apache.org/jira/browse/DELTASPIKE-673
Project: DeltaSpike
Issue Type: Improvement
Components: Data-Module
Affects Versions: 1.0.0
Reporter: Philip Herbst
Assignee: Daniel Cunha (soro)
Fix For: 1.4.2
I'm trying to use org.apache.deltaspike.data.api.EntityRepository on TomEE
1.5.2 with detached entities. Whenever I try to call the save method of
EntityRepository I get
{code}
org.apache.openjpa.persistence.EntityExistsException: Attempt to persist
detached object
{code}
CdiQueryInvocationContex#isNew returns true for my detached entity and and
because of that EntityManager#persist is called.
see org.apache.deltaspike.data.impl.handler.EntityRepositoryHandler#save
From OpenJpaPersistenceUtil#getIdentifier(OpenJPAEntityManagerFactory emf,
Object entity)
{code}
/**
* Get the object identifier for a persistent entity managed by one
* of the entity managers of the specified entity manager factory.
* @return The identifier of the entity or null if the entity does
* not have an identifier assigned or is not managed by any of the
* entity managers of the entity manager factory.
*/
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-941) JPA link broken in Data Module documentation
[ https://issues.apache.org/jira/browse/DELTASPIKE-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) updated DELTASPIKE-941: --- Fix Version/s: 1.4.2 JPA link broken in Data Module documentation Key: DELTASPIKE-941 URL: https://issues.apache.org/jira/browse/DELTASPIKE-941 Project: DeltaSpike Issue Type: Bug Components: Documentation Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) Priority: Minor Fix For: 1.4.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-448) Review exception handling in Data module
[ https://issues.apache.org/jira/browse/DELTASPIKE-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608984#comment-14608984 ] Daniel Cunha (soro) commented on DELTASPIKE-448: [~thomashug], I saw that you did some changes: https://github.com/apache/deltaspike/commit/4e8d58316ee707cda093fe24eb1c6b6286b90d04 Can we close it? Review exception handling in Data module Key: DELTASPIKE-448 URL: https://issues.apache.org/jira/browse/DELTASPIKE-448 Project: DeltaSpike Issue Type: Improvement Components: Data-Module Reporter: Thomas Hug Assignee: Daniel Cunha (soro) For the exception handling: - javax.persistence.PersistenceException should be re-thrown to the caller - Other exceptions should be wrapped in a QueryInvocationException. The exception should be available in the API module. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-941) JPA link broken in Data Module documentation
[ https://issues.apache.org/jira/browse/DELTASPIKE-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) resolved DELTASPIKE-941. Resolution: Fixed JPA link broken in Data Module documentation Key: DELTASPIKE-941 URL: https://issues.apache.org/jira/browse/DELTASPIKE-941 Project: DeltaSpike Issue Type: Bug Components: Documentation Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DELTASPIKE-941) JPA link broken in Data Module documentation
Daniel Cunha (soro) created DELTASPIKE-941: -- Summary: JPA link broken in Data Module documentation Key: DELTASPIKE-941 URL: https://issues.apache.org/jira/browse/DELTASPIKE-941 Project: DeltaSpike Issue Type: Bug Components: Documentation Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-871) save() and findByxxx() in same transaction gives constraint violation exception
[ https://issues.apache.org/jira/browse/DELTASPIKE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14604885#comment-14604885 ] Daniel Cunha (soro) commented on DELTASPIKE-871: [~mdkamaruzzaman], If you do think the problem is in DeltaSpike and not in your application, then please provide a self-contained test case. Do you have some sample? Thanks. :) save() and findByxxx() in same transaction gives constraint violation exception --- Key: DELTASPIKE-871 URL: https://issues.apache.org/jira/browse/DELTASPIKE-871 Project: DeltaSpike Issue Type: Bug Components: Data-Module Affects Versions: 1.2.0 Environment: Windows-7, Java-8, Netbeans-8.0.2 Reporter: Md Kamaruzzaman Assignee: Daniel Cunha (soro) It seems like when in the same EJB transaction, save() and findByxxx() is called, then delta-spike inserts the entity twice [once in save() and other time in findByxxx()] and gives a constraint violation exception. After some debuggin, it seems like save() gives a INSERT query in DB and findByxxx() method calls a flush which again gives the same INSERT query in DB [INSERT query from save() is not removed from EntityManager] and gives constraint violation exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-673) CdiQueryInvocationContext#isNew does not work well with OpenJpa and detached entities
[
https://issues.apache.org/jira/browse/DELTASPIKE-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Cunha (soro) resolved DELTASPIKE-673.
Resolution: Fixed
CdiQueryInvocationContext#isNew does not work well with OpenJpa and detached
entities
-
Key: DELTASPIKE-673
URL: https://issues.apache.org/jira/browse/DELTASPIKE-673
Project: DeltaSpike
Issue Type: Improvement
Components: Data-Module
Affects Versions: 1.0.0
Reporter: Philip Herbst
Assignee: Daniel Cunha (soro)
I'm trying to use org.apache.deltaspike.data.api.EntityRepository on TomEE
1.5.2 with detached entities. Whenever I try to call the save method of
EntityRepository I get
{code}
org.apache.openjpa.persistence.EntityExistsException: Attempt to persist
detached object
{code}
CdiQueryInvocationContex#isNew returns true for my detached entity and and
because of that EntityManager#persist is called.
see org.apache.deltaspike.data.impl.handler.EntityRepositoryHandler#save
From OpenJpaPersistenceUtil#getIdentifier(OpenJPAEntityManagerFactory emf,
Object entity)
{code}
/**
* Get the object identifier for a persistent entity managed by one
* of the entity managers of the specified entity manager factory.
* @return The identifier of the entity or null if the entity does
* not have an identifier assigned or is not managed by any of the
* entity managers of the entity manager factory.
*/
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-910) Add EntityRepository.getPrimaryKey(E entity)
[
https://issues.apache.org/jira/browse/DELTASPIKE-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Cunha (soro) resolved DELTASPIKE-910.
Resolution: Fixed
Add EntityRepository.getPrimaryKey(E entity)
Key: DELTASPIKE-910
URL: https://issues.apache.org/jira/browse/DELTASPIKE-910
Project: DeltaSpike
Issue Type: New Feature
Components: JPA-Module
Reporter: Xavier Dury
Assignee: Daniel Cunha (soro)
Priority: Trivial
It would be nice to add a method to retrieve the primary key of an entity on
its {{EntityRepository}} (by using
{{entityManagerFactory.getPersistenceUnitUtil().getIdentifier(entity)}}).
This would help implementing generic JSF {{DataModel}} based on
{{EntityRepository}}, especially for methods like {{getRowKey()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (DELTASPIKE-934) @Query metadata should be considered for any method expression
Daniel Cunha (soro) created DELTASPIKE-934: -- Summary: @Query metadata should be considered for any method expression Key: DELTASPIKE-934 URL: https://issues.apache.org/jira/browse/DELTASPIKE-934 Project: DeltaSpike Issue Type: Improvement Components: Data-Module Affects Versions: 1.4.0 Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) Fix For: 1.4.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-923) Add #entityName() to AbstractEntityRepository
[ https://issues.apache.org/jira/browse/DELTASPIKE-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) updated DELTASPIKE-923: --- Component/s: Data-Module Add #entityName() to AbstractEntityRepository - Key: DELTASPIKE-923 URL: https://issues.apache.org/jira/browse/DELTASPIKE-923 Project: DeltaSpike Issue Type: New Feature Components: Data-Module Affects Versions: 1.4.0 Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-700) Add #tableName() to AbstractEntityRepository
[ https://issues.apache.org/jira/browse/DELTASPIKE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) updated DELTASPIKE-700: --- Fix Version/s: 1.4.1 Add #tableName() to AbstractEntityRepository Key: DELTASPIKE-700 URL: https://issues.apache.org/jira/browse/DELTASPIKE-700 Project: DeltaSpike Issue Type: New Feature Components: Data-Module Reporter: Thomas Andraschko Assignee: Daniel Cunha (soro) Priority: Minor Fix For: 1.4.1 As table names can easiely be changed via @Table, it would be an typesafe usage to get the native table name for native queries e.g. @Table(name = tbl_MyEntity) public class MyEntity... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-700) Add #tableName() to AbstractEntityRepository
[ https://issues.apache.org/jira/browse/DELTASPIKE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) resolved DELTASPIKE-700. Resolution: Fixed Add #tableName() to AbstractEntityRepository Key: DELTASPIKE-700 URL: https://issues.apache.org/jira/browse/DELTASPIKE-700 Project: DeltaSpike Issue Type: New Feature Components: Data-Module Reporter: Thomas Andraschko Assignee: Daniel Cunha (soro) Priority: Minor As table names can easiely be changed via @Table, it would be an typesafe usage to get the native table name for native queries e.g. @Table(name = tbl_MyEntity) public class MyEntity... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DELTASPIKE-923) Add #entityName() to AbstractEntityRepository
Daniel Cunha (soro) created DELTASPIKE-923: -- Summary: Add #entityName() to AbstractEntityRepository Key: DELTASPIKE-923 URL: https://issues.apache.org/jira/browse/DELTASPIKE-923 Project: DeltaSpike Issue Type: New Feature Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-923) Add #entityName() to AbstractEntityRepository
[ https://issues.apache.org/jira/browse/DELTASPIKE-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) updated DELTASPIKE-923: --- Affects Version/s: 1.4.0 Add #entityName() to AbstractEntityRepository - Key: DELTASPIKE-923 URL: https://issues.apache.org/jira/browse/DELTASPIKE-923 Project: DeltaSpike Issue Type: New Feature Components: Data-Module Affects Versions: 1.4.0 Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-923) Add #entityName() to AbstractEntityRepository
[ https://issues.apache.org/jira/browse/DELTASPIKE-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) resolved DELTASPIKE-923. Resolution: Fixed Fix Version/s: 1.4.1 Add #entityName() to AbstractEntityRepository - Key: DELTASPIKE-923 URL: https://issues.apache.org/jira/browse/DELTASPIKE-923 Project: DeltaSpike Issue Type: New Feature Components: Data-Module Affects Versions: 1.4.0 Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) Priority: Minor Fix For: 1.4.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DELTASPIKE-924) Adjust The AbstractEntityRepository Class secion.
Daniel Cunha (soro) created DELTASPIKE-924: -- Summary: Adjust The AbstractEntityRepository Class secion. Key: DELTASPIKE-924 URL: https://issues.apache.org/jira/browse/DELTASPIKE-924 Project: DeltaSpike Issue Type: Improvement Components: Documentation Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) Priority: Minor Fix For: 1.4.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-924) Adjust The AbstractEntityRepository Class secion.
[ https://issues.apache.org/jira/browse/DELTASPIKE-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) resolved DELTASPIKE-924. Resolution: Fixed Adjust The AbstractEntityRepository Class secion. - Key: DELTASPIKE-924 URL: https://issues.apache.org/jira/browse/DELTASPIKE-924 Project: DeltaSpike Issue Type: Improvement Components: Documentation Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) Priority: Minor Fix For: 1.4.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-700) Add #tableName() to AbstractEntityRepository
[ https://issues.apache.org/jira/browse/DELTASPIKE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14580576#comment-14580576 ] Daniel Cunha (soro) commented on DELTASPIKE-700: Hi guys, please review it: https://github.com/danielsoro/deltaspike/commit/a91b6c6f22a6926d6c0e696ae1d935c3878202c1 If ok, I'll push it. :) Add #tableName() to AbstractEntityRepository Key: DELTASPIKE-700 URL: https://issues.apache.org/jira/browse/DELTASPIKE-700 Project: DeltaSpike Issue Type: Improvement Components: Data-Module Reporter: Thomas Andraschko Assignee: Daniel Cunha (soro) Priority: Minor As table names can easiely be changed via @Table, it would be an typesafe usage to get the native table name for native queries e.g. @Table(name = tbl_MyEntity) public class MyEntity... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-700) Add #tableName() to AbstractEntityRepository
[ https://issues.apache.org/jira/browse/DELTASPIKE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14580826#comment-14580826 ] Daniel Cunha (soro) commented on DELTASPIKE-700: Sure. Add #tableName() to AbstractEntityRepository Key: DELTASPIKE-700 URL: https://issues.apache.org/jira/browse/DELTASPIKE-700 Project: DeltaSpike Issue Type: Improvement Components: Data-Module Reporter: Thomas Andraschko Assignee: Daniel Cunha (soro) Priority: Minor As table names can easiely be changed via @Table, it would be an typesafe usage to get the native table name for native queries e.g. @Table(name = tbl_MyEntity) public class MyEntity... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-700) Add #tableName() to AbstractEntityRepository
[ https://issues.apache.org/jira/browse/DELTASPIKE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) updated DELTASPIKE-700: --- Issue Type: New Feature (was: Improvement) Add #tableName() to AbstractEntityRepository Key: DELTASPIKE-700 URL: https://issues.apache.org/jira/browse/DELTASPIKE-700 Project: DeltaSpike Issue Type: New Feature Components: Data-Module Reporter: Thomas Andraschko Assignee: Daniel Cunha (soro) Priority: Minor As table names can easiely be changed via @Table, it would be an typesafe usage to get the native table name for native queries e.g. @Table(name = tbl_MyEntity) public class MyEntity... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-910) Add EntityRepository.getPrimaryKey(E entity)
[
https://issues.apache.org/jira/browse/DELTASPIKE-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14579713#comment-14579713
]
Daniel Cunha (soro) commented on DELTASPIKE-910:
This case, we need to have a special implementation for discovery Entity ID
when the is provide by OpenJPA, because OpenJPA return an OpenJPAId:
http://mail-archives.apache.org/mod_mbox/openjpa-dev/201506.mbox/%3ccahlhu44m6hkcrec2iirxnwmbfus0_lfqist6vowrpbmhr_j...@mail.gmail.com%3E
or we can use EntityUtils like this:
https://github.com/danielsoro/deltaspike/commit/4de2fd06f3641f864b7920b43e9d09d0125e5dee
But, I have my doubt if EntityUtil is enough.
Add EntityRepository.getPrimaryKey(E entity)
Key: DELTASPIKE-910
URL: https://issues.apache.org/jira/browse/DELTASPIKE-910
Project: DeltaSpike
Issue Type: New Feature
Components: JPA-Module
Reporter: Xavier Dury
Assignee: Daniel Cunha (soro)
Priority: Trivial
It would be nice to add a method to retrieve the primary key of an entity on
its {{EntityRepository}} (by using
{{entityManagerFactory.getPersistenceUnitUtil().getIdentifier(entity)}}).
This would help implementing generic JSF {{DataModel}} based on
{{EntityRepository}}, especially for methods like {{getRowKey()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-594) Memory leak in RepositoryComponents singleton
[
https://issues.apache.org/jira/browse/DELTASPIKE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Cunha (soro) resolved DELTASPIKE-594.
Resolution: Fixed
Memory leak in RepositoryComponents singleton
-
Key: DELTASPIKE-594
URL: https://issues.apache.org/jira/browse/DELTASPIKE-594
Project: DeltaSpike
Issue Type: Bug
Components: Data-Module
Affects Versions: 0.7
Reporter: Harald Wellmann
Assignee: Harald Wellmann
Fix For: 1.4.1
{{RepositoryComponentsFactory}} has a static singleton member of type
{{RepositoryComponents}}.
Repository classes are added to this singleton, but are never deleted.
This will cause a classloader leak when the DeltaSpike modules live longer
than application modules, e.g. in OSGi when each DeltaSpike module is a
separate bundle, or in WildFly when DeltaSpike is installed as a JBoss module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-594) Memory leak in RepositoryComponents singleton
[
https://issues.apache.org/jira/browse/DELTASPIKE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14579663#comment-14579663
]
Daniel Cunha (soro) commented on DELTASPIKE-594:
Hi [~hwellmann],
reviewed and applied.
https://github.com/apache/deltaspike/commit/75fba93ee4e5a473b82d3fbb6a9eba81c37ab409
Memory leak in RepositoryComponents singleton
-
Key: DELTASPIKE-594
URL: https://issues.apache.org/jira/browse/DELTASPIKE-594
Project: DeltaSpike
Issue Type: Bug
Components: Data-Module
Affects Versions: 0.7
Reporter: Harald Wellmann
Assignee: Harald Wellmann
{{RepositoryComponentsFactory}} has a static singleton member of type
{{RepositoryComponents}}.
Repository classes are added to this singleton, but are never deleted.
This will cause a classloader leak when the DeltaSpike modules live longer
than application modules, e.g. in OSGi when each DeltaSpike module is a
separate bundle, or in WildFly when DeltaSpike is installed as a JBoss module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (DELTASPIKE-894) Trim for CriteriaSupport API
[ https://issues.apache.org/jira/browse/DELTASPIKE-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) reassigned DELTASPIKE-894: -- Assignee: Daniel Cunha (soro) (was: Thomas Hug) Trim for CriteriaSupport API Key: DELTASPIKE-894 URL: https://issues.apache.org/jira/browse/DELTASPIKE-894 Project: DeltaSpike Issue Type: New Feature Components: Data-Module Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) Priority: Minor Attachments: DELTASPIKE-894.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-701) Add method in EntityRepository to merge a detached entity and remove it
[
https://issues.apache.org/jira/browse/DELTASPIKE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Cunha (soro) resolved DELTASPIKE-701.
Resolution: Fixed
Add method in EntityRepository to merge a detached entity and remove it
---
Key: DELTASPIKE-701
URL: https://issues.apache.org/jira/browse/DELTASPIKE-701
Project: DeltaSpike
Issue Type: Improvement
Components: Data-Module
Reporter: Juliano Marques
Assignee: Daniel Cunha (soro)
Attachments: DELTASPIKE-701.patch
It will be nice if EntityRepository has a method like:
public void attachAndRemove(Entity entity) {
if (entityManager.contains(entity)) {
entityManager.remove(entity);
} else {
entityManager.remove(entityManager.merge(entity));
}
}
This method will be useful to handle java.lang.IllegalArgumentException:
Removing a detached instance exceptions.
Workaround: Create a query delegate with this method.
http://mail-archives.apache.org/mod_mbox/deltaspike-users/201408.mbox/%3CCAAuOd%3DXhb%3D-ssdzU%3DTdxWg8d18XXC15U7EjNiGya9eEgaA%2BUpA%40mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-894) Trim for CriteriaSupport API
[ https://issues.apache.org/jira/browse/DELTASPIKE-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) resolved DELTASPIKE-894. Resolution: Fixed Trim for CriteriaSupport API Key: DELTASPIKE-894 URL: https://issues.apache.org/jira/browse/DELTASPIKE-894 Project: DeltaSpike Issue Type: New Feature Components: Data-Module Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) Priority: Minor Attachments: DELTASPIKE-894.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-701) Add method in EntityRepository to merge a detached entity and remove it
[
https://issues.apache.org/jira/browse/DELTASPIKE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14577325#comment-14577325
]
Daniel Cunha (soro) commented on DELTASPIKE-701:
Thanks [~thomashug] and [~rafabene].
I'll apply later.
Add method in EntityRepository to merge a detached entity and remove it
---
Key: DELTASPIKE-701
URL: https://issues.apache.org/jira/browse/DELTASPIKE-701
Project: DeltaSpike
Issue Type: Improvement
Components: Data-Module
Reporter: Juliano Marques
Assignee: Thomas Hug
Attachments: DELTASPIKE-701.patch
It will be nice if EntityRepository has a method like:
public void attachAndRemove(Entity entity) {
if (entityManager.contains(entity)) {
entityManager.remove(entity);
} else {
entityManager.remove(entityManager.merge(entity));
}
}
This method will be useful to handle java.lang.IllegalArgumentException:
Removing a detached instance exceptions.
Workaround: Create a query delegate with this method.
http://mail-archives.apache.org/mod_mbox/deltaspike-users/201408.mbox/%3CCAAuOd%3DXhb%3D-ssdzU%3DTdxWg8d18XXC15U7EjNiGya9eEgaA%2BUpA%40mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-894) Trim for CriteriaSupport API
[ https://issues.apache.org/jira/browse/DELTASPIKE-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14577328#comment-14577328 ] Daniel Cunha (soro) commented on DELTASPIKE-894: Thank you, [~thomashug] and [~rafabene]. I'll fix it and apply later. Trim for CriteriaSupport API Key: DELTASPIKE-894 URL: https://issues.apache.org/jira/browse/DELTASPIKE-894 Project: DeltaSpike Issue Type: New Feature Components: Data-Module Reporter: Daniel Cunha (soro) Assignee: Thomas Hug Priority: Minor Attachments: DELTASPIKE-894.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (DELTASPIKE-911) Criteria API - Add support for accept multiple columns in orderBy
[ https://issues.apache.org/jira/browse/DELTASPIKE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) reassigned DELTASPIKE-911: -- Assignee: Daniel Cunha (soro) Criteria API - Add support for accept multiple columns in orderBy - Key: DELTASPIKE-911 URL: https://issues.apache.org/jira/browse/DELTASPIKE-911 Project: DeltaSpike Issue Type: Improvement Components: Data-Module Affects Versions: 1.4.0 Reporter: Daniel Cunha (soro) Assignee: Daniel Cunha (soro) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-911) Criteria API - Add support for accept multiple columns in orderBy
[ https://issues.apache.org/jira/browse/DELTASPIKE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) updated DELTASPIKE-911: --- Issue Type: Improvement (was: Bug) Criteria API - Add support for accept multiple columns in orderBy - Key: DELTASPIKE-911 URL: https://issues.apache.org/jira/browse/DELTASPIKE-911 Project: DeltaSpike Issue Type: Improvement Components: Data-Module Affects Versions: 1.4.0 Reporter: Daniel Cunha (soro) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-603) removeBy* - similiar to findBy*
[ https://issues.apache.org/jira/browse/DELTASPIKE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) updated DELTASPIKE-603: --- Attachment: (was: DELTASPIKE-603.patch) removeBy* - similiar to findBy* --- Key: DELTASPIKE-603 URL: https://issues.apache.org/jira/browse/DELTASPIKE-603 Project: DeltaSpike Issue Type: Improvement Components: Data-Module Reporter: Thomas Andraschko Assignee: Thomas Hug It would be great to allow a removeBy* - simliar to findBy* e.g. void removeByBrandId(String brandId); -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-603) removeBy* - similiar to findBy*
[ https://issues.apache.org/jira/browse/DELTASPIKE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14556716#comment-14556716 ] Daniel Cunha (soro) commented on DELTASPIKE-603: Patch updated in PR: https://github.com/apache/deltaspike/pull/33 removeBy* - similiar to findBy* --- Key: DELTASPIKE-603 URL: https://issues.apache.org/jira/browse/DELTASPIKE-603 Project: DeltaSpike Issue Type: Improvement Components: Data-Module Reporter: Thomas Andraschko Assignee: Thomas Hug It would be great to allow a removeBy* - simliar to findBy* e.g. void removeByBrandId(String brandId); -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-908) org.apache.deltaspike.test.scheduler.custom.CustomSchedulerWarFileTest fails with Weld
[
https://issues.apache.org/jira/browse/DELTASPIKE-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14556527#comment-14556527
]
Daniel Cunha (soro) commented on DELTASPIKE-908:
Sorry guys!
Test fixed: https://github.com/apache/deltaspike/pull/32
org.apache.deltaspike.test.scheduler.custom.CustomSchedulerWarFileTest fails
with Weld
--
Key: DELTASPIKE-908
URL: https://issues.apache.org/jira/browse/DELTASPIKE-908
Project: DeltaSpike
Issue Type: Bug
Components: Scheduler
Affects Versions: 1.3.0
Reporter: Tomas Remes
Assignee: Gerhard Petracek
Priority: Minor
Fix For: 1.4.1
{noformat}
junit.framework.AssertionFailedError: expected:lt;1gt; but was:lt;0gt;
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.failNotEquals(Assert.java:287)
at junit.framework.Assert.assertEquals(Assert.java:67)
at junit.framework.Assert.assertEquals(Assert.java:199)
at junit.framework.Assert.assertEquals(Assert.java:205)
at
org.apache.deltaspike.test.scheduler.custom.CustomSchedulerTest.checkAutoRegisteredSchedulerJob(CustomSchedulerTest.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:273)
at
org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60)
{noformat}
I am not sure what's the cause yet. I need to do further investigation. Weld
version doesn't matter here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-901) org.apache.deltaspike.data.impl.builder.postprocessor.CountQueryPostProcessor doesn't respect order by
[
https://issues.apache.org/jira/browse/DELTASPIKE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Cunha (soro) updated DELTASPIKE-901:
---
Attachment: DELTASPIKE-901.patch
org.apache.deltaspike.data.impl.builder.postprocessor.CountQueryPostProcessor
doesn't respect order by
--
Key: DELTASPIKE-901
URL: https://issues.apache.org/jira/browse/DELTASPIKE-901
Project: DeltaSpike
Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Romain Manni-Bucau
Attachments: DELTASPIKE-901.patch
using select p from MyEntity p order by p.someString
and
{code}
@Query(named = MyEntity.findAll)
QueryResultMyEntity all(@FirstResult int start, @MaxResults int
pageSize);
{code}
I get
{code}
org.apache.openjpa.lib.jdbc.ReportingSQLException: expression not in
aggregate or GROUP BY columns: T0.PROPERTY_KEY {SELECT
COUNT(t0.property_key), t0.property_key FROM properties t0} [code=-5574,
state=42574]
{code}
the count post processor doesn't handle the order by correctly.
Wonder if we should add order by parameters in the select clause or just
ignore it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-901) org.apache.deltaspike.data.impl.builder.postprocessor.CountQueryPostProcessor doesn't respect order by
[
https://issues.apache.org/jira/browse/DELTASPIKE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Cunha (soro) updated DELTASPIKE-901:
---
Attachment: (was: DELTASPIKE-901_2.patch)
org.apache.deltaspike.data.impl.builder.postprocessor.CountQueryPostProcessor
doesn't respect order by
--
Key: DELTASPIKE-901
URL: https://issues.apache.org/jira/browse/DELTASPIKE-901
Project: DeltaSpike
Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Romain Manni-Bucau
Attachments: DELTASPIKE-901.patch
using select p from MyEntity p order by p.someString
and
{code}
@Query(named = MyEntity.findAll)
QueryResultMyEntity all(@FirstResult int start, @MaxResults int
pageSize);
{code}
I get
{code}
org.apache.openjpa.lib.jdbc.ReportingSQLException: expression not in
aggregate or GROUP BY columns: T0.PROPERTY_KEY {SELECT
COUNT(t0.property_key), t0.property_key FROM properties t0} [code=-5574,
state=42574]
{code}
the count post processor doesn't handle the order by correctly.
Wonder if we should add order by parameters in the select clause or just
ignore it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-901) org.apache.deltaspike.data.impl.builder.postprocessor.CountQueryPostProcessor doesn't respect order by
[
https://issues.apache.org/jira/browse/DELTASPIKE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Cunha (soro) updated DELTASPIKE-901:
---
Attachment: (was: DELTASPIKE-901.patch)
org.apache.deltaspike.data.impl.builder.postprocessor.CountQueryPostProcessor
doesn't respect order by
--
Key: DELTASPIKE-901
URL: https://issues.apache.org/jira/browse/DELTASPIKE-901
Project: DeltaSpike
Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Romain Manni-Bucau
Attachments: DELTASPIKE-901_2.patch
using select p from MyEntity p order by p.someString
and
{code}
@Query(named = MyEntity.findAll)
QueryResultMyEntity all(@FirstResult int start, @MaxResults int
pageSize);
{code}
I get
{code}
org.apache.openjpa.lib.jdbc.ReportingSQLException: expression not in
aggregate or GROUP BY columns: T0.PROPERTY_KEY {SELECT
COUNT(t0.property_key), t0.property_key FROM properties t0} [code=-5574,
state=42574]
{code}
the count post processor doesn't handle the order by correctly.
Wonder if we should add order by parameters in the select clause or just
ignore it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-901) org.apache.deltaspike.data.impl.builder.postprocessor.CountQueryPostProcessor doesn't respect order by
[
https://issues.apache.org/jira/browse/DELTASPIKE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14551476#comment-14551476
]
Daniel Cunha (soro) commented on DELTASPIKE-901:
Updated patch. Improvement in test. : )
org.apache.deltaspike.data.impl.builder.postprocessor.CountQueryPostProcessor
doesn't respect order by
--
Key: DELTASPIKE-901
URL: https://issues.apache.org/jira/browse/DELTASPIKE-901
Project: DeltaSpike
Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Romain Manni-Bucau
Attachments: DELTASPIKE-901_2.patch
using select p from MyEntity p order by p.someString
and
{code}
@Query(named = MyEntity.findAll)
QueryResultMyEntity all(@FirstResult int start, @MaxResults int
pageSize);
{code}
I get
{code}
org.apache.openjpa.lib.jdbc.ReportingSQLException: expression not in
aggregate or GROUP BY columns: T0.PROPERTY_KEY {SELECT
COUNT(t0.property_key), t0.property_key FROM properties t0} [code=-5574,
state=42574]
{code}
the count post processor doesn't handle the order by correctly.
Wonder if we should add order by parameters in the select clause or just
ignore it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-901) org.apache.deltaspike.data.impl.builder.postprocessor.CountQueryPostProcessor doesn't respect order by
[
https://issues.apache.org/jira/browse/DELTASPIKE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Cunha (soro) updated DELTASPIKE-901:
---
Attachment: DELTASPIKE-901_2.patch
org.apache.deltaspike.data.impl.builder.postprocessor.CountQueryPostProcessor
doesn't respect order by
--
Key: DELTASPIKE-901
URL: https://issues.apache.org/jira/browse/DELTASPIKE-901
Project: DeltaSpike
Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Romain Manni-Bucau
Attachments: DELTASPIKE-901_2.patch
using select p from MyEntity p order by p.someString
and
{code}
@Query(named = MyEntity.findAll)
QueryResultMyEntity all(@FirstResult int start, @MaxResults int
pageSize);
{code}
I get
{code}
org.apache.openjpa.lib.jdbc.ReportingSQLException: expression not in
aggregate or GROUP BY columns: T0.PROPERTY_KEY {SELECT
COUNT(t0.property_key), t0.property_key FROM properties t0} [code=-5574,
state=42574]
{code}
the count post processor doesn't handle the order by correctly.
Wonder if we should add order by parameters in the select clause or just
ignore it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (DELTASPIKE-906) Extract debug information in pom.xml and put in documentation.
Daniel Cunha (soro) created DELTASPIKE-906: -- Summary: Extract debug information in pom.xml and put in documentation. Key: DELTASPIKE-906 URL: https://issues.apache.org/jira/browse/DELTASPIKE-906 Project: DeltaSpike Issue Type: Task Reporter: Daniel Cunha (soro) Priority: Trivial In parent/code/pom.xml we have this: * DEBUGGING: * mvn test -Ptomee-build-managed -Dtest=UnitTestName -Dopenejb.server.debug=true * then use remote debuggig at port 5005 Maybe this information should be in DeltaSpike documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-901) org.apache.deltaspike.data.impl.builder.postprocessor.CountQueryPostProcessor doesn't respect order by
[
https://issues.apache.org/jira/browse/DELTASPIKE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Cunha (soro) updated DELTASPIKE-901:
---
Attachment: DELTASPIKE-901.patch
org.apache.deltaspike.data.impl.builder.postprocessor.CountQueryPostProcessor
doesn't respect order by
--
Key: DELTASPIKE-901
URL: https://issues.apache.org/jira/browse/DELTASPIKE-901
Project: DeltaSpike
Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Romain Manni-Bucau
Attachments: DELTASPIKE-901.patch
using select p from MyEntity p order by p.someString
and
{code}
@Query(named = MyEntity.findAll)
QueryResultMyEntity all(@FirstResult int start, @MaxResults int
pageSize);
{code}
I get
{code}
org.apache.openjpa.lib.jdbc.ReportingSQLException: expression not in
aggregate or GROUP BY columns: T0.PROPERTY_KEY {SELECT
COUNT(t0.property_key), t0.property_key FROM properties t0} [code=-5574,
state=42574]
{code}
the count post processor doesn't handle the order by correctly.
Wonder if we should add order by parameters in the select clause or just
ignore it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-901) org.apache.deltaspike.data.impl.builder.postprocessor.CountQueryPostProcessor doesn't respect order by
[
https://issues.apache.org/jira/browse/DELTASPIKE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546225#comment-14546225
]
Daniel Cunha (soro) commented on DELTASPIKE-901:
Hi [~romain.manni-bucau],
I tested here on snapshot version and it seem work fine.
https://github.com/danielsoro/deltaspike/commit/6f9a03155ecc7ff387b8613ab487f003bc710ea8
I'll put this patch to add this test in data module if you validate as ok.
See you. :)
org.apache.deltaspike.data.impl.builder.postprocessor.CountQueryPostProcessor
doesn't respect order by
--
Key: DELTASPIKE-901
URL: https://issues.apache.org/jira/browse/DELTASPIKE-901
Project: DeltaSpike
Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Romain Manni-Bucau
using select p from MyEntity p order by p.someString
and
{code}
@Query(named = MyEntity.findAll)
QueryResultMyEntity all(@FirstResult int start, @MaxResults int
pageSize);
{code}
I get
{code}
org.apache.openjpa.lib.jdbc.ReportingSQLException: expression not in
aggregate or GROUP BY columns: T0.PROPERTY_KEY {SELECT
COUNT(t0.property_key), t0.property_key FROM properties t0} [code=-5574,
state=42574]
{code}
the count post processor doesn't handle the order by correctly.
Wonder if we should add order by parameters in the select clause or just
ignore it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-603) removeBy* - similiar to findBy*
[ https://issues.apache.org/jira/browse/DELTASPIKE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) updated DELTASPIKE-603: --- Attachment: DELTASPIKE-603.patch removeBy* - similiar to findBy* --- Key: DELTASPIKE-603 URL: https://issues.apache.org/jira/browse/DELTASPIKE-603 Project: DeltaSpike Issue Type: Improvement Components: Data-Module Reporter: Thomas Andraschko Assignee: Thomas Hug Attachments: DELTASPIKE-603.patch It would be great to allow a removeBy* - simliar to findBy* e.g. void removeByBrandId(String brandId); -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-902) Test for EntityRepository#removeAndFlush(entity)
[ https://issues.apache.org/jira/browse/DELTASPIKE-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) updated DELTASPIKE-902: --- Affects Version/s: 1.3.0 Test for EntityRepository#removeAndFlush(entity) Key: DELTASPIKE-902 URL: https://issues.apache.org/jira/browse/DELTASPIKE-902 Project: DeltaSpike Issue Type: Test Components: Data-Module Affects Versions: 1.3.0 Reporter: Daniel Cunha (soro) Priority: Minor Attachments: DELTASPIKE-902.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-701) Add method in EntityRepository to merge a detached entity and remove it
[
https://issues.apache.org/jira/browse/DELTASPIKE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Cunha (soro) updated DELTASPIKE-701:
---
Attachment: DELTASPIKE-701.patch
Add method in EntityRepository to merge a detached entity and remove it
---
Key: DELTASPIKE-701
URL: https://issues.apache.org/jira/browse/DELTASPIKE-701
Project: DeltaSpike
Issue Type: Improvement
Components: Data-Module
Reporter: Juliano Marques
Assignee: Thomas Hug
Attachments: DELTASPIKE-701.patch
It will be nice if EntityRepository has a method like:
public void attachAndRemove(Entity entity) {
if (entityManager.contains(entity)) {
entityManager.remove(entity);
} else {
entityManager.remove(entityManager.merge(entity));
}
}
This method will be useful to handle java.lang.IllegalArgumentException:
Removing a detached instance exceptions.
Workaround: Create a query delegate with this method.
http://mail-archives.apache.org/mod_mbox/deltaspike-users/201408.mbox/%3CCAAuOd%3DXhb%3D-ssdzU%3DTdxWg8d18XXC15U7EjNiGya9eEgaA%2BUpA%40mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (DELTASPIKE-902) Test for EntityRepository#removeAndFlush(entity)
Daniel Cunha (soro) created DELTASPIKE-902: -- Summary: Test for EntityRepository#removeAndFlush(entity) Key: DELTASPIKE-902 URL: https://issues.apache.org/jira/browse/DELTASPIKE-902 Project: DeltaSpike Issue Type: Test Reporter: Daniel Cunha (soro) Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-902) Test for EntityRepository#removeAndFlush(entity)
[ https://issues.apache.org/jira/browse/DELTASPIKE-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) updated DELTASPIKE-902: --- Attachment: DELTASPIKE-902.patch Test for EntityRepository#removeAndFlush(entity) Key: DELTASPIKE-902 URL: https://issues.apache.org/jira/browse/DELTASPIKE-902 Project: DeltaSpike Issue Type: Test Reporter: Daniel Cunha (soro) Priority: Minor Attachments: DELTASPIKE-902.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-902) Test for EntityRepository#removeAndFlush(entity)
[ https://issues.apache.org/jira/browse/DELTASPIKE-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) updated DELTASPIKE-902: --- Component/s: Data-Module Test for EntityRepository#removeAndFlush(entity) Key: DELTASPIKE-902 URL: https://issues.apache.org/jira/browse/DELTASPIKE-902 Project: DeltaSpike Issue Type: Test Components: Data-Module Affects Versions: 1.3.0 Reporter: Daniel Cunha (soro) Priority: Minor Attachments: DELTASPIKE-902.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DELTASPIKE-894) Trim for CriteriaSupport API
Daniel Cunha (soro) created DELTASPIKE-894: -- Summary: Trim for CriteriaSupport API Key: DELTASPIKE-894 URL: https://issues.apache.org/jira/browse/DELTASPIKE-894 Project: DeltaSpike Issue Type: New Feature Components: Data-Module Reporter: Daniel Cunha (soro) Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-894) Trim for CriteriaSupport API
[ https://issues.apache.org/jira/browse/DELTASPIKE-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Cunha (soro) updated DELTASPIKE-894: --- Attachment: DELTASPIKE-894.patch Trim for CriteriaSupport API Key: DELTASPIKE-894 URL: https://issues.apache.org/jira/browse/DELTASPIKE-894 Project: DeltaSpike Issue Type: New Feature Components: Data-Module Reporter: Daniel Cunha (soro) Priority: Minor Attachments: DELTASPIKE-894.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-890) deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final
[
https://issues.apache.org/jira/browse/DELTASPIKE-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14523546#comment-14523546
]
Daniel Cunha (soro) commented on DELTASPIKE-890:
It seem some problem in your module configuration.
The wildfly cannot loading the javax.faces.event.PhaseListener class.
deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final
Key: DELTASPIKE-890
URL: https://issues.apache.org/jira/browse/DELTASPIKE-890
Project: DeltaSpike
Issue Type: Bug
Affects Versions: 1.3.0
Environment: Wildfly 8.2.0.Final
Java 8u45
DS 1.3.0
Reporter: The Alchemist
h3. Stack Trace
{noformat}
17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-3) WELD-000119:
Not generating any bean definitions from
org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$3
because of underlying class loading error: Type javax.faces.event.PhaseId
from [Module org.apache.deltaspike.modules:main from local module loader
@4973813a (finder: local module finder @6321e813 (roots:
/usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))]
not found. If this is unexpected, enable DEBUG logging to see the full
error.
17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-4) WELD-000119:
Not generating any bean definitions from
org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$2
because of underlying class loading error: Type javax.faces.event.PhaseId
from [Module org.apache.deltaspike.modules:main from local module loader
@4973813a (finder: local module finder @6321e813 (roots:
/usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))]
not found. If this is unexpected, enable DEBUG logging to see the full
error.
17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-5) WELD-000119:
Not generating any bean definitions from
org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$1
because of underlying class loading error: Type
javax.faces.event.PhaseListener from [Module
org.apache.deltaspike.modules:main from local module loader @4973813a
(finder: local module finder @6321e813 (roots:
/usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))]
not found. If this is unexpected, enable DEBUG logging to see the full
error.
17:46:46,961 INFO [org.jboss.weld.Bootstrap] (weld-worker-8) WELD-000119:
Not generating any bean definitions from
org.apache.deltaspike.jsf.impl.injection.ManagedArtifactResolver because of
underlying class loading error: Type javax.faces.validator.Validator from
[Module org.apache.deltaspike.modules:main from local module loader
@4973813a (finder: local module finder @6321e813 (roots:
/usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))]
not found. If this is unexpected, enable DEBUG logging to see the full
error.
17:46:46,954 WARN [org.jboss.modules] (weld-worker-7) Failed to define class
org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener
in Module org.apache.deltaspike.modules:main from local module loader
@4973813a (finder: local module finder @6321e813 (roots:
/usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base)):
java.lang.LinkageError: Failed to link
org/apache/deltaspike/jsf/impl/listener/phase/JsfRequestLifecyclePhaseListener
(Module org.apache.deltaspike.modules:main from local module loader
@4973813a (finder: local module finder @6321e813 (roots:
/usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base)))
at
org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:487)
[jboss-modules.jar:1.3.3.Final]
at
org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:277)
[jboss-modules.jar:1.3.3.Final]
at
org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:92)
[jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.Module.loadModuleClass(Module.java:568)
[jboss-modules.jar:1.3.3.Final]
at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205)
[jboss-modules.jar:1.3.3.Final]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459)
[jboss-modules.jar:1.3.3.Final]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408)
[jboss-modules.jar:1.3.3.Final]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389)
[jira] [Comment Edited] (DELTASPIKE-890) deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final
[
https://issues.apache.org/jira/browse/DELTASPIKE-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14523546#comment-14523546
]
Daniel Cunha (soro) edited comment on DELTASPIKE-890 at 5/1/15 6:05 PM:
It seem some problem in your module configuration.
The wildfly cannot loading the javax.faces.* classes.
was (Author: danielsoro):
It seem some problem in your module configuration.
The wildfly cannot loading the javax.faces.event.PhaseListener class.
deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final
Key: DELTASPIKE-890
URL: https://issues.apache.org/jira/browse/DELTASPIKE-890
Project: DeltaSpike
Issue Type: Bug
Affects Versions: 1.3.0
Environment: Wildfly 8.2.0.Final
Java 8u45
DS 1.3.0
Reporter: The Alchemist
h3. Stack Trace
{noformat}
17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-3) WELD-000119:
Not generating any bean definitions from
org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$3
because of underlying class loading error: Type javax.faces.event.PhaseId
from [Module org.apache.deltaspike.modules:main from local module loader
@4973813a (finder: local module finder @6321e813 (roots:
/usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))]
not found. If this is unexpected, enable DEBUG logging to see the full
error.
17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-4) WELD-000119:
Not generating any bean definitions from
org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$2
because of underlying class loading error: Type javax.faces.event.PhaseId
from [Module org.apache.deltaspike.modules:main from local module loader
@4973813a (finder: local module finder @6321e813 (roots:
/usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))]
not found. If this is unexpected, enable DEBUG logging to see the full
error.
17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-5) WELD-000119:
Not generating any bean definitions from
org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$1
because of underlying class loading error: Type
javax.faces.event.PhaseListener from [Module
org.apache.deltaspike.modules:main from local module loader @4973813a
(finder: local module finder @6321e813 (roots:
/usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))]
not found. If this is unexpected, enable DEBUG logging to see the full
error.
17:46:46,961 INFO [org.jboss.weld.Bootstrap] (weld-worker-8) WELD-000119:
Not generating any bean definitions from
org.apache.deltaspike.jsf.impl.injection.ManagedArtifactResolver because of
underlying class loading error: Type javax.faces.validator.Validator from
[Module org.apache.deltaspike.modules:main from local module loader
@4973813a (finder: local module finder @6321e813 (roots:
/usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))]
not found. If this is unexpected, enable DEBUG logging to see the full
error.
17:46:46,954 WARN [org.jboss.modules] (weld-worker-7) Failed to define class
org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener
in Module org.apache.deltaspike.modules:main from local module loader
@4973813a (finder: local module finder @6321e813 (roots:
/usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base)):
java.lang.LinkageError: Failed to link
org/apache/deltaspike/jsf/impl/listener/phase/JsfRequestLifecyclePhaseListener
(Module org.apache.deltaspike.modules:main from local module loader
@4973813a (finder: local module finder @6321e813 (roots:
/usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base)))
at
org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:487)
[jboss-modules.jar:1.3.3.Final]
at
org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:277)
[jboss-modules.jar:1.3.3.Final]
at
org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:92)
[jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.Module.loadModuleClass(Module.java:568)
[jboss-modules.jar:1.3.3.Final]
at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205)
[jboss-modules.jar:1.3.3.Final]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459)
[jboss-modules.jar:1.3.3.Final]
at
[jira] [Commented] (DELTASPIKE-890) deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final
[
https://issues.apache.org/jira/browse/DELTASPIKE-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14523981#comment-14523981
]
Daniel Cunha (soro) commented on DELTASPIKE-890:
[~the_alchemist], That will help you:
http://deltaspike.apache.org/documentation/configure.html
deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final
Key: DELTASPIKE-890
URL: https://issues.apache.org/jira/browse/DELTASPIKE-890
Project: DeltaSpike
Issue Type: Bug
Affects Versions: 1.3.0
Environment: Wildfly 8.2.0.Final
Java 8u45
DS 1.3.0
Reporter: The Alchemist
h3. Stack Trace
{noformat}
17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-3) WELD-000119:
Not generating any bean definitions from
org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$3
because of underlying class loading error: Type javax.faces.event.PhaseId
from [Module org.apache.deltaspike.modules:main from local module loader
@4973813a (finder: local module finder @6321e813 (roots:
/usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))]
not found. If this is unexpected, enable DEBUG logging to see the full
error.
17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-4) WELD-000119:
Not generating any bean definitions from
org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$2
because of underlying class loading error: Type javax.faces.event.PhaseId
from [Module org.apache.deltaspike.modules:main from local module loader
@4973813a (finder: local module finder @6321e813 (roots:
/usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))]
not found. If this is unexpected, enable DEBUG logging to see the full
error.
17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-5) WELD-000119:
Not generating any bean definitions from
org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$1
because of underlying class loading error: Type
javax.faces.event.PhaseListener from [Module
org.apache.deltaspike.modules:main from local module loader @4973813a
(finder: local module finder @6321e813 (roots:
/usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))]
not found. If this is unexpected, enable DEBUG logging to see the full
error.
17:46:46,961 INFO [org.jboss.weld.Bootstrap] (weld-worker-8) WELD-000119:
Not generating any bean definitions from
org.apache.deltaspike.jsf.impl.injection.ManagedArtifactResolver because of
underlying class loading error: Type javax.faces.validator.Validator from
[Module org.apache.deltaspike.modules:main from local module loader
@4973813a (finder: local module finder @6321e813 (roots:
/usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))]
not found. If this is unexpected, enable DEBUG logging to see the full
error.
17:46:46,954 WARN [org.jboss.modules] (weld-worker-7) Failed to define class
org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener
in Module org.apache.deltaspike.modules:main from local module loader
@4973813a (finder: local module finder @6321e813 (roots:
/usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base)):
java.lang.LinkageError: Failed to link
org/apache/deltaspike/jsf/impl/listener/phase/JsfRequestLifecyclePhaseListener
(Module org.apache.deltaspike.modules:main from local module loader
@4973813a (finder: local module finder @6321e813 (roots:
/usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base)))
at
org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:487)
[jboss-modules.jar:1.3.3.Final]
at
org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:277)
[jboss-modules.jar:1.3.3.Final]
at
org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:92)
[jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.Module.loadModuleClass(Module.java:568)
[jboss-modules.jar:1.3.3.Final]
at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205)
[jboss-modules.jar:1.3.3.Final]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459)
[jboss-modules.jar:1.3.3.Final]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408)
[jboss-modules.jar:1.3.3.Final]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389)
[jboss-modules.jar:1.3.3.Final]
at
