Re: [VOTE] Release Apache DeltaSpike-1.9.6

[Daniel Cunha]

+1

Em sex., 8 de abr. de 2022 às 13:29, Daniel Dias Dos Santos <
daniel.dias.analist...@gmail.com> escreveu:

> +1
>
> On Fri, Apr 8, 2022, 13:27 Mark Struberg 
> wrote:
>
> > Hi lords and ladies!
> >
> > I'd like to call a VOTE on releasing Apache DeltaSpike-1.9.6
> >
> > The following tickets got resolved:
> >
> >
> > Bug
> > [DELTASPIKE-1133] - Don't override the log level
> > [DELTASPIKE-1427] - JUL Logging with {} as param leeds to
> > NumberFormatException
> > [DELTASPIKE-1433] - EntityManagerFactoryProducer should also provide
> a
> > @Disposes method
> > [DELTASPIKE-1453] - injecting config of Class got broken
> >
> > New Feature
> > [DELTASPIKE-1431] - add easy way to disable InvocationResultLogger
> > [DELTASPIKE-1444] - Create POJO and Record based Config
> > [DELTASPIKE-1445] - Dynamic Config injection via a Supplier
> >
> > Improvement
> > [DELTASPIKE-1426] - DeltaSpikeProxyFactory is slow on start
> > [DELTASPIKE-1432] - Proxy class definition does not work
> > [DELTASPIKE-1454] - Upgrade ASM to 9.3
> >
> > Task
> > [DELTASPIKE-1452] - upgrade to apache-parent 25
> >
> >
> >
> > The staging repository can be found here:
> >
> >
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1058/
> > <
> >
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1058/
> > >
> >
> > The source repo is located at:
> >
> >
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1058/org/apache/deltaspike/deltaspike/1.9.6/
> > <
> >
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1058/org/apache/deltaspike/deltaspike/1.9.6/
> > >
> > sha512 is
> >
> ae2b2b183a54b9dff00d78a8f3a60fc87bde701599390a437970b218c208cb636d058fa596d0ab0ac3dfa9dd022c383c59f9ac6f5bab4e3bfe47db0a063af490
> >
> > Please VOTE
> >
> > [+1] yeah, ship it!
> > [+0] meh, don't care
> > [-1]  stop there is a ${showstopper}
> >
> > The VOTE is open for 72h.
> >
> > txs and LieGrue,
> > strub
> >
> >
> >
>


-- 
Daniel Cunha
https://github.com/danielsoro
https://twitter.com/danielvlcunha
https://www.linkedin.com/in/danielvlcunha/

Re: [VOTE] Release Apache DeltaSpike-1.9.5

[Daniel Cunha]

+1

Em sáb., 6 de mar. de 2021 às 07:01, Thomas Andraschko <
andraschko.tho...@gmail.com> escreveu:

> +1
>
> Romain Manni-Bucau  schrieb am Sa., 6. März 2021,
> 10:13:
>
> > +1
> >
> > Le sam. 6 mars 2021 à 01:08, Daniel Dias Dos Santos <
> > daniel.dias.analist...@gmail.com> a écrit :
> >
> > > Hello ,
> > >
> > > +1
> > >
> > > On Fri, Mar 5, 2021, 19:45 Mark Struberg 
> > > wrote:
> > >
> > > > Hi Lords and Ladies!
> > > >
> > > > I'd like to call a VOTE for releasing Apache DeltaSpike-1.9.5
> > > >
> > > > The following tickets got closed:
> > > > Bug
> > > >
> > > > [DELTASPIKE-1314 <
> > https://issues.apache.org/jira/browse/DELTASPIKE-1314
> > > >]
> > > > - ContainerCtrlTckTest fails with tomee7-build-managed
> > > > [DELTASPIKE-1413 <
> > https://issues.apache.org/jira/browse/DELTASPIKE-1413
> > > >]
> > > > - dsrwid cookie should not be set to sameSite="None"
> > > > [DELTASPIKE-1416 <
> > https://issues.apache.org/jira/browse/DELTASPIKE-1416
> > > >]
> > > > - deltaspike-core-impl.jar does not contain the Main class to execute
> > in
> > > > your Manifest.MF to Crypto
> > > > [DELTASPIKE-1423 <
> > https://issues.apache.org/jira/browse/DELTASPIKE-1423
> > > >]
> > > > - JSF-2.3 managed() in FacesValidator and FacesConverter break CDI
> > > > integration
> > > > Improvement
> > > >
> > > > [DELTASPIKE-1420 <
> > https://issues.apache.org/jira/browse/DELTASPIKE-1420
> > > >]
> > > > - Update ASM to 9.1
> > > >
> > > >
> > > > The staging repository is
> > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1056/
> > > > <
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1056/
> > > > >
> > > >
> > > > The source zip can be found at
> > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1056/org/apache/deltaspike/deltaspike/1.9.5/
> > > > <
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1056/org/apache/deltaspike/deltaspike/1.9.5/
> > > > >
> > > > sha1 is fa8779819026c86320959ffb7d1ce6546b6ad1e2
> > > >
> > > > Please VOTE
> > > >
> > > > [+1] yikes, go ship it!
> > > > [+0] meh, don't care
> > > > [-1] nah stop, there is a ${showstopper}
> > > >
> > > > The VOTE is open for 72h.
> > > >
> > > > LieGrue,
> > > > strub
> > > >
> > > >
> > >
> >
>


-- 
Daniel "soro" Cunha
https://twitter.com/dvlc_

Re: [VOTE] Release Apache DeltaSpike-1.9.3

[Daniel Cunha]

+1

Em ter., 28 de jan. de 2020 às 12:17, Mark Struberg
 escreveu:

> Hi!
>
> We are about to release Apache DeltaSpike-1.9.3.
> This release fixes a security issue for our ClientSideWindowHandler.
>
> The staging repo can be found here:
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1054
>
> The source release can be found here
>
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1054/org/apache/deltaspike/deltaspike/1.9.3/
> sha1
> 
> is 6c822278d187dee6f9167dbdf630feab633ec4f3
>
> Please VOTE
>
> [+1] go ship it
> [+0] meh, don't care
> [-1] stop, there is a ${showstopper}
>
> The VOTE is open for 72h
>
> txs and LieGrue,
> strub
>
>

-- 
Daniel "soro" Cunha
https://twitter.com/dvlc_

Re: [VOTE] Move our git repo to Apache gitbox

[Daniel Cunha]

+1

Em ter, 8 de jan de 2019 às 12:27, Rafael Benevides 
escreveu:

> +1
>
> On Tue, Jan 8, 2019 at 4:03 AM Rudy De Busscher 
> wrote:
>
> > +1
> >
> > Rudy
> >
> > On Mon, 7 Jan 2019 at 23:38, Gerhard Petracek 
> > wrote:
> >
> > > +1
> > >
> > > regards,
> > > gerhard
> > >
> > >
> > >
> > > Am Mo., 7. Jan. 2019 um 18:08 Uhr schrieb Mark Struberg
> > > :
> > >
> > > > Hi folks!
> > > >
> > > > I've made good experience with gitbox in other ASF projects.
> > > > I'd say we just call it 'deltaspike' as is. We just have one repo, so
> > > that
> > > > would be a 1:1 migration.
> > > > As with everything GIT the sha1 doesn'T change anyway...
> > > >
> > > > Can I pull the trigger?
> > > >
> > > > Here is my +1
> > > >
> > > > The VOTE is open for 72h
> > > >
> > > > LieGrue,
> > > > strub
> > > >
> > > > > Am 03.01.2019 um 14:19 schrieb Apache Infrastructure Team <
> > > > infrastruct...@apache.org>:
> > > > >
> > > > > Hello, deltaspike folks.
> > > > > As stated earlier in 2018, all git repositories must be migrated
> from
> > > > > the git-wip-us.apache.org URL to gitbox.apache.org, as the old
> > service
> > > > > is being decommissioned. Your project is receiving this email
> because
> > > > > you still have repositories on git-wip-us that needs to be
> migrated.
> > > > >
> > > > > The following repositories on git-wip-us belong to your project:
> > > > > - deltaspike.git
> > > > >
> > > > >
> > > > > We are now entering the mandated (coordinated) move stage of the
> > > roadmap,
> > > > > and you are asked to please coordinate migration with the Apache
> > > > > Infrastructure Team before February 7th. All repositories not
> > migrated
> > > > > on February 7th will be mass migrated without warning, and we'd
> > > > appreciate
> > > > > it if we could work together to avoid a big mess that day :-).
> > > > >
> > > > > Moving to gitbox means you will get full write access on GitHub as
> > > well,
> > > > > and be able to close/merge pull requests and much more.
> > > > >
> > > > > To have your repositories moved, please follow these steps:
> > > > >
> > > > > - Ensure consensus on the move (a link to a lists.apache.org
> thread
> > > will
> > > > >  suffice for us as evidence).
> > > > > - Create a JIRA ticket at
> > https://issues.apache.org/jira/browse/INFRA
> > > > >
> > > > > Your migration should only take a few minutes. If you wish to
> migrate
> > > > > at a specific time of day or date, please do let us know in the
> > ticket.
> > > > >
> > > > > As always, we appreciate your understanding and patience as we move
> > > > > things around and work to provide better services and features for
> > > > > the Apache Family.
> > > > >
> > > > > Should you wish to contact us with feedback or questions, please do
> > so
> > > > > at: us...@infra.apache.org.
> > > > >
> > > > >
> > > > > With regards,
> > > > > Apache Infrastructure
> > > > >
> > > >
> > > >
> > >
> >
>
>
> --
> *Rafael Benevides | Senior Product Manager*
> Director of Developer Experience
> Follow me at Twitter: @rafabene 
> M: +1-407-401-3555
> Register today at https://developers.redhat.com/
>


-- 
Daniel "soro" Cunha
https://twitter.com/dvlc_

Re: Merge PRs

[Daniel Cunha]

Hi Daniel,

Is that your PR: https://github.com/apache/deltaspike/pull/77 ?
Easily you can create a patch. Just add .patch in the end of the URL.
https://github.com/apache/deltaspike/pull/77.patch

Hope that helps. :)

Em seg, 26 de nov de 2018 às 13:25, Daniel Dias Dos Santos <
daniel.dias.analist...@gmail.com> escreveu:

> hi
>
> cool, I try to do this with the PR I sent .
>
> thanks .
> --
>
> *Daniel Dias dos Santos*
> Java Developer
> SouJava & JCP Member
> GitHub: https://github.com/Daniel-Dos
> Linkedin: www.linkedin.com/in/danieldiasjava
> Twitter: http://twitter.com/danieldiasjava
>
>
> Em seg, 26 de nov de 2018 às 14:20, Thomas Andraschko <
> andraschko.tho...@gmail.com> escreveu:
>
> > Hi,
> >
> > as long as we don't use gitbox, it's really awkward to apply them.
> > I would prefer a issue + attaching a patch.
> >
> > Am Mo., 26. Nov. 2018 um 16:37 Uhr schrieb Daniel Dias Dos Santos <
> > daniel.dias.analist...@gmail.com>:
> >
> > > HI ,
> > >
> > > the best way is to send via github the PR?
> > >
> > > because I was following the instructions here :
> > >
> > > https://deltaspike.apache.org/suggested-git-workflows.html
> > >
> > > thanks,
> > > --
> > >
> > > *Daniel Dias dos Santos*
> > > Java Developer
> > > SouJava & JCP Member
> > > GitHub: https://github.com/Daniel-Dos
> > > Linkedin: www.linkedin.com/in/danieldiasjava
> > > Twitter: http://twitter.com/danieldiasjava
> > >
> > >
> > > Em seg, 12 de nov de 2018 às 07:55, Romain Manni-Bucau <
> > > rmannibu...@gmail.com> escreveu:
> > >
> > > > You pull them locally, merge and then push on asf, once "ok" you can
> > ask
> > > > the author to close it on github
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau  |  Blog
> > > >  | Old Blog
> > > >  | Github <
> > > > https://github.com/rmannibucau> |
> > > > LinkedIn  | Book
> > > > <
> > > >
> > >
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > > > >
> > > >
> > > >
> > > > Le lun. 12 nov. 2018 à 10:53, Thomas Andraschko <
> > > > andraschko.tho...@gmail.com>
> > > > a écrit :
> > > >
> > > > > hmmm, how should we handle those pull requests then?
> > > > >
> > > > > Am Mo., 12. Nov. 2018 um 10:40 Uhr schrieb Mark Struberg
> > > > > :
> > > > >
> > > > > > Hi Thomas!
> > > > > >
> > > > > > DeltaSpike is not managed via gitbox but as a classic GIT repo.
> > > > > > Thus merging via github simply does not work.
> > > > > >
> > > > > > LieGrue,
> > > > > > strub
> > > > > >
> > > > > >
> > > > > > > Am 12.11.2018 um 09:37 schrieb Thomas Andraschko <
> > > > > > andraschko.tho...@gmail.com>:
> > > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > i would like to merge 2 PRs and close 1 PRs but it seems that i
> > > don't
> > > > > > have
> > > > > > > write access.
> > > > > > > However, i have write access to MF + OWB. So i wonder what
> > > additional
> > > > > > steps
> > > > > > > i need to do, to get write access?
> > > > > > >
> > > > > > > Best regards,
> > > > > > > Thomas
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>


-- 
Daniel "soro" Cunha
https://twitter.com/dvlc_

Re: [VOTE] Release Apache DeltaSpike-1.8.2

[Daniel Cunha]

+1

On Tue, May 15, 2018, 18:36 Gerhard Petracek  wrote:

> +1
>
> regards,
> gerhard
>
>
>
> 2018-05-15 23:26 GMT+02:00 Mark Struberg :
>
> > Hi lords and ladies!
> >
> > I would like to call a VOTE on releasing Apache DeltaSpike-1.8.2.
> > This is a maintenance release with java6 compatibility.
> >
> > The following tickets got resolved:
> >
> > Bug
> >
> > [DELTASPIKE-1276] - Multiple license headers
> > [DELTASPIKE-1299] - Order by items are applied in alphabetic order
> > [DELTASPIKE-1310] - Please use https (SSL) for links to KEYS, hashes,
> > sigs
> > [DELTASPIKE-1313] - DeltaSpikeProxyInterceptorLookup fails on WAS
> > [DELTASPIKE-1316] - add dynamic annotations feature, configurable via
> > config
> > [DELTASPIKE-1317] - AnnotatedCallableImpl blows up with
> > ArrayOutofBounds when parsing enums
> > [DELTASPIKE-1344] - deltaspike-cdictrl-owb has a transient runtime
> > dependency on Shrinkwrap and Arquillian
> >
> > New Feature
> >
> > [DELTASPIKE-1319] - labeled alternatives
> > [DELTASPIKE-1320] - global alternative spi to support custom
> > (type-safe) mechanisms
> > [DELTASPIKE-1337] - optional ClassFilter spi
> > [DELTASPIKE-1338] - support class-filter per test
> >
> > Improvement
> >
> > [DELTASPIKE-1309] - Upgrade ASM
> > [DELTASPIKE-1311] - Allow Excluded Repositories
> > [DELTASPIKE-1329] - ProjectStageProducer should log changed values
> > [DELTASPIKE-1331] - minor type improvement of the ViewConfigNode spi
> > [DELTASPIKE-1332] - support further cases for custom view-meta-data
> > [DELTASPIKE-1334] - javadoc for ConfigPreProcessor#beforeAddToConfig
> > [DELTASPIKE-1339] - Add support for dynamic interceptor binding,
> added
> > via Extension
> >
> > Task
> >
> > [DELTASPIKE-1257] - Research why BOM isn't working right in a release
> > [DELTASPIKE-1312] - Upgrade to quartz-2.3.0
> >
> >
> > Here is the staging repo:
> > https://repository.apache.org/content/repositories/
> > orgapachedeltaspike-1047/
> >
> > The source zip can be found at
> > https://repository.apache.org/content/repositories/
> > orgapachedeltaspike-1047/org/apache/deltaspike/deltaspike/1.8.2/
> > sha1 is add349e89314d9384dc9dc08772af275048343ba
> >
> > Please VOTE:
> >
> > [+1] yes, ship it
> > [+0] meh, don't care
> > [-1] stop there is a ${showstopper}
> >
> > The VOTE is open for 72h
> >
> > txs and LieGrue,
> > strub
> >
> >
>

[jira] [Commented] (DELTASPIKE-1255) query.or

[Daniel Cunha (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006812#comment-16006812
 ] 

Daniel Cunha commented on DELTASPIKE-1255:
--

[~fradiati] can you share your sample and stacktrace?

> query.or
> 
>
> Key: DELTASPIKE-1255
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1255
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: JPA-Module
>Reporter: Pátkai Attila
>
> i have this query: query.or(query.eq(partnerAttributeA, 
> partner),query.eq(partnerAttributeB, partner));  
> and i get stackoverflow exception 
> how can i fix it? 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (DELTASPIKE-976) document handling of @PersistenceUnitName EntityManagerFactory

[Daniel Cunha (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394982#comment-15394982
 ] 

Daniel Cunha commented on DELTASPIKE-976:
-

I think so! +1

> document handling of @PersistenceUnitName EntityManagerFactory
> --
>
> Key: DELTASPIKE-976
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-976
> Project: DeltaSpike
>  Issue Type: Task
>  Components: Documentation
>Affects Versions: 1.5.0
>Reporter: Gerhard Petracek
>Assignee: Daniel Cunha
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [DISCUSS] PR Based Contributor Workflow

[Daniel Cunha]

Hi John,

Greate job. I think that we really need to have that. It's much more easy
and cool to work with PR.
Easy way to review, easy way to fix changes, the contributor does not need
to attach a new patch just need to update the PR and we'll have feedbacks
more fast with PR Builder Plugin and comments by line on PR.

I prefer this way, totally agree with your PR.

+1 :)

On Sat, Jul 23, 2016 at 1:04 PM, John D. Ament 
wrote:

> All,
>
> I put together a first pass PR on an improved contributor workflow that can
> leverage github PRs.  This is in addition to our existing patch approach.
>
> You can find the PR here, with the changes:
> https://github.com/apache/deltaspike/pull/61/files
>
> Using PRs gives us a bit of an advantage:
>
> - We don't lose the original author in the commit
> - We can run automated tests prior to the commit being merged in
>
> Please take a look, I'm happy to adjust as needed.  I also took the liberty
> to replace some of the to-be-retired links (e.g. people.a.o is retiring
> soon, mail archives are being moved to pony, ICLA is now PDF based)
>
> John
>



-- 
Daniel Cunha
https://twitter.com/dvlc_
http://www.tomitribe.com
http://www.tomitribe.io

Re: [GitHub] deltaspike pull request #61: DELTASPIKE-1188 Added some PR based contributio...

[Daniel Cunha]

+1 :)

On Sat, Jul 23, 2016 at 12:58 PM, johnament  wrote:

> GitHub user johnament opened a pull request:
>
> https://github.com/apache/deltaspike/pull/61
>
> DELTASPIKE-1188 Added some PR based contribution workflow.  Replaced …
>
> …the mail archive link with pony.
>
> You can merge this pull request into a Git repository by running:
>
> $ git pull https://github.com/johnament/deltaspike DELTASPIKE-1188
>
> Alternatively you can review and apply these changes as the patch at:
>
> https://github.com/apache/deltaspike/pull/61.patch
>
> To close this pull request, make a commit to your master/trunk branch
> with (at least) the following in the commit message:
>
> This closes #61
>
> 
> commit 4caa3f917670be22925fc926a9316c4ff5fc14e2
> Author: John D. Ament 
> Date:   2016-07-23T15:58:18Z
>
> DELTASPIKE-1188 Added some PR based contribution workflow.  Replaced
> the mail archive link with pony.
>
> 
>
>
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> with INFRA.
> ---
>



-- 
Daniel Cunha
https://twitter.com/dvlc_
http://www.tomitribe.com
http://www.tomitribe.io

Re: [DISCUSS] Tests for Payara?

[Daniel Cunha]

+1

On Wed, Jul 6, 2016 at 7:13 AM, Gerhard Petracek  wrote:

> back then it worked with v4.1, however, v4.1.1 failed.
>
> regards,
> gerhard
>
>
>
> 2016-07-06 11:58 GMT+02:00 John D. Ament :
>
> > The glassfish one doesn't work on Payara?
> >
> > John
> >
> > On Wed, Jul 6, 2016 at 5:56 AM Gerhard Petracek 
> > wrote:
> >
> > > i asked them already (last year), however, they have(/had) an issue
> with
> > > their arquillian-adapter.
> > >
> > > regards,
> > > gerhard
> > >
> > >
> > >
> > > 2016-07-06 11:42 GMT+02:00 John D. Ament :
> > >
> > > > Hey guys
> > > >
> > > > Should we setup jenkins jobs/build profiles to test against Payara?
> > > Seems
> > > > like it may be useful.
> > > >
> > > > John
> > > >
> > >
> >
>



-- 
Daniel Cunha
https://twitter.com/dvlc_
http://www.tomitribe.com
http://www.tomitribe.io

Re: [DISCUSS] GitHub PR Builder

[Daniel Cunha]

Hi John,

When we're following the steps presented by asg-git, the PR is marked like
merged.
For example:
https://github.com/apache/deltaspike/pull/57

The steps:
https://issues.apache.org/jira/browse/DELTASPIKE-1180?focusedCommentId=15361289&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15361289


On Wed, Jul 6, 2016 at 6:50 AM, John D. Ament  wrote:

> Short answer is you can't.  You need to pull the branch and push to our
> master.  You need to make the commit message include the "This closes #123"
> line to make github know to close it.  Or ask the requestor to close it.
>
> There is an open git-dual POC from infra.  Last I looked, it wasn't doing
> well.  May be worth raising to the board?
>
> John
>
> On Wed, Jul 6, 2016 at 4:44 AM Thomas Andraschko <
> andraschko.tho...@gmail.com> wrote:
>
> > +1
> >
> > Stupid question but how can i merge PRs from github?
> > The last PRs from georgekankava
> > <
> >
> https://github.com/apache/deltaspike/issues?q=is%3Apr+is%3Aopen+author%3Ageorgekankava
> > >
> > are looking good.
> >
> > 2016-07-06 8:54 GMT+02:00 Christian Kaltepoth :
> >
> > > I think such build jobs are very valuable. So +1 for them.
> > >
> > >
> > >
> > > 2016-07-06 4:06 GMT+02:00 John D. Ament :
> > >
> > > > Hey guys
> > > >
> > > > We've been getting a few more PRs over github.  Its IMHO easier to
> > merge
> > > > those instead of patches in JIRA tickets.
> > > >
> > > > I went ahead and created a PR build job.  When someone raises a PR
> > > against
> > > > us in github, it will trigger a build.  Right now that build only
> runs
> > > OWB
> > > > 1.6.x, but I think it would be good to get more tests in there.  Say
> > one
> > > > embedded container and one full container?
> > > >
> > > > What do others think? Useful? Not useful?
> > > >
> > > > John
> > > >
> > >
> > >
> > >
> > > --
> > > Christian Kaltepoth
> > > Blog: http://blog.kaltepoth.de/
> > > Twitter: http://twitter.com/chkal
> > > GitHub: https://github.com/chkal
> > >
> >
>



-- 
Daniel Cunha
https://twitter.com/dvlc_
http://www.tomitribe.com
http://www.tomitribe.io

[jira] [Assigned] (DELTASPIKE-1180) Remove unused imports

[Daniel Cunha (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Cunha reassigned DELTASPIKE-1180:


Assignee: Daniel Cunha  (was: Ivan Junckes Filho)

> Remove unused imports
> -
>
> Key: DELTASPIKE-1180
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1180
> Project: DeltaSpike
>  Issue Type: Improvement
>Reporter: Ivan Junckes Filho
>    Assignee: Daniel Cunha
>Priority: Trivial
> Fix For: 1.7.1
>
>
> There are several unused imports.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DELTASPIKE-1180) Remove unused imports

[Daniel Cunha (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Cunha resolved DELTASPIKE-1180.
--
Resolution: Fixed

> Remove unused imports
> -
>
> Key: DELTASPIKE-1180
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1180
> Project: DeltaSpike
>  Issue Type: Improvement
>Reporter: Ivan Junckes Filho
>    Assignee: Daniel Cunha
>Priority: Trivial
> Fix For: 1.7.1
>
>
> There are several unused imports.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (DELTASPIKE-1180) Remove unused imports

[Daniel Cunha (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361763#comment-15361763
 ] 

Daniel Cunha commented on DELTASPIKE-1180:
--

Thanks Ivan.

PR Merged. :)

> Remove unused imports
> -
>
> Key: DELTASPIKE-1180
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1180
> Project: DeltaSpike
>  Issue Type: Improvement
>Reporter: Ivan Junckes Filho
>Assignee: Ivan Junckes Filho
>Priority: Trivial
> Fix For: 1.7.1
>
>
> There are several unused imports.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: 1.6 to be the last release to support Java 1.6?

[Daniel Cunha]

+1 :)

On Sat, Mar 26, 2016 at 10:34 AM, John D. Ament 
wrote:

> All,
>
> Here's the announcement I'm going to post to the site.  Let me know if you
> have any comments on the change.
>
> == End of Support Announcement - Java 6
>
>
> The Apache DeltaSpike team has decided to begin dropping support for
>
> Java 6.  The next release, 1.6.0 is currently planned to be the last
>
> minor release to support Java 6.  Patch fixes on 1.6.x will continue
>
> to support it, but our next minor release (1.7.0) will require
>
> Java 7 at a minimum.
>
>
>
> On Fri, Mar 25, 2016 at 8:17 AM Harald Wellmann 
> wrote:
>
> > +1
> >
> > 2016-03-25 13:09 GMT+01:00 John D. Ament :
> >
> > > BTW, if we do agree to drop Java 6, do we create a 1.6 maintenance
> branch
> > > or just leave the tag, and if need be cut a bug fix release then?
> > >
> > > John
> > >
> > > On Fri, Mar 25, 2016 at 8:06 AM John D. Ament 
> > > wrote:
> > >
> > > > To me, dropping support for Java 6 doesn't mean rewriting the code
> base
> > > to
> > > > only be compliant with Java 7 and up.
> > > >
> > > > It does allow for some new stuff in our codebase, if we want to go
> back
> > > > and clean it up:
> > > >
> > > > - try-with-resources
> > > > - automatic type inference on generics.
> > > >
> > > > But those are just clean ups, no real new functionality.
> > > >
> > > > John
> > > >
> > > >
> > > > On Fri, Mar 25, 2016 at 4:24 AM Thomas Andraschko <
> > > > andraschko.tho...@gmail.com> wrote:
> > > >
> > > >> basically +1
> > > >> Most of our customers are using 1.7 since this year.
> > > >>
> > > >> I just wonder whats the benefit for us?
> > > >> I think there are no language features which would improve our code
> > > base.
> > > >>
> > > >> 2016-03-25 3:25 GMT+01:00 John D. Ament :
> > > >>
> > > >> > Hey guys,
> > > >> >
> > > >> > I've brought this topic up before without much positive
> response.  I
> > > >> figure
> > > >> > I'll bring it up again.
> > > >> >
> > > >> > I'd like to propose that DeltaSpike 1.6 be the last minor release
> to
> > > >> > support Java 1.6.  I suspect that most users are already using
> Java
> > 7
> > > or
> > > >> > higher.  None of our builds in CI (builds.apache.org) currently
> run
> > > on
> > > >> 1.6
> > > >> > either, so while we can say from a syntax standpoint we're 1.6
> > > compliant
> > > >> > I'm not sure we can say from a JDK Library standpoint we don't
> rely
> > on
> > > >> > anything from Java 7.
> > > >> >
> > > >> > We're one of the few projects that probably still supports Java 6
> > as a
> > > >> > mainline development, so I was hoping we could just cut 1.6 as 1.6
> > > >> > compliant, if we need to cut patch releases of 1.6 to apply
> patches,
> > > but
> > > >> > with DeltaSpike 1.7 and on, focus on Java 7 and up.
> > > >> >
> > > >> > John
> > > >> >
> > > >>
> > > >
> > >
> >
>



-- 
Daniel Cunha
https://twitter.com/dvlc_
http://www.tomitribe.com
http://www.tomitribe.io

Re: Donating Microscoped code

[Daniel Cunha]

Cool! +1

On Sat, Mar 26, 2016 at 12:19 PM, John D. Ament 
wrote:

> I have a backport of microscoped for Java 6 locally, I'm currently expanded
> the tests to be able to target other containers (to make sure there's no
> compatibility issues).
>
> I created a ticket in our JIRA as well -
> https://issues.apache.org/jira/browse/DELTASPIKE-1104
>
> John
>
> On Fri, Mar 25, 2016 at 8:03 AM John D. Ament 
> wrote:
>
> > Actually, the map functions aren't the problem.  Those were easy to cut
> > over.  The problem is the new ThreadLocal behavior in Java 8 that just
> > doesn't have an equivalent in older JDKs.
> >
> > I think I'm almost done, will raise a PR to prep it for inclusion.
> >
> > I do not envy the road warriors, mind you.
> >
> > John
> >
> >
> > On Thu, Mar 24, 2016 at 11:05 PM David Blevins 
> > wrote:
> >
> >> The code is significantly harder without the Java 8 computeIfAbsent on
> >> hashmap.
> >>
> >> In terms of time, I wish I had more to give.  I was on the road 49 out
> of
> >> 52 weeks last year and this year is no different.
> >>
> >> I've pretty much sacrificed every bit of time and work-life balance
> >> possible in hopes to produce more for others.  It's a work in
> progress
> >>
> >>
> >> -David
> >>
> >>
> >> On Thu, Mar 24, 2016 at 6:47 PM, John D. Ament 
> >> wrote:
> >>
> >> > I don't mind looking at it a bit further.  You're the only contributor
> >> and
> >> > you're a long standing ASF guy.  Of course one big issue is that
> you're
> >> > using a modern, supported JVM version.  We're still on the archaic 1.6
> >> JDK.
> >> >
> >> > One thing to point out, your license is already assigning ownership to
> >> the
> >> > ASF -
> >> >
> >> >
> >>
> https://github.com/tomitribe/microscoped/blob/master/microscoped-timer/pom.xml#L3
> >> > not
> >> > sure if that's intentional or not.
> >> >
> >> > Here's a reference to what it looks like when its not licensed to the
> >> ASF.
> >> > https://github.com/johnament/hammock/blob/master/pom.xml#L1
> >> >
> >> > The big difference - licensed under vs licensed to.
> >> >
> >> > John
> >> >
> >> > On Thu, Mar 24, 2016 at 9:39 PM David Blevins <
> david.blev...@gmail.com>
> >> > wrote:
> >> >
> >> > > John had asked on twitter if this code could be donated.
> Absolutely.
> >> > >
> >> > > https://tomitribe.io/projects/microscoped <
> >> > > https://tomitribe.io/projects/microscoped>
> >> > >
> >> > > I feel bad writing a “come and get it” email.  90% of the code was
> >> > written
> >> > > between 12am and 5am the night before the related JavaOne talk. Not
> by
> >> > > choice. :)
> >> > >
> >> > > Is there anyone with time to help?
> >> > >
> >> > >
> >> > > --
> >> > > David Blevins
> >> > > http://twitter.com/dblevins
> >> > > http://www.tomitribe.com
> >> > >
> >> > >
> >> >
> >>
> >
>



-- 
Daniel Cunha
https://twitter.com/dvlc_
http://www.tomitribe.com
http://www.tomitribe.io

[jira] [Commented] (DELTASPIKE-1100) Support remove expressions

[Daniel Cunha (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213044#comment-15213044
 ] 

Daniel Cunha commented on DELTASPIKE-1100:
--

Updated.

> Support remove expressions
> --
>
> Key: DELTASPIKE-1100
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1100
> Project: DeltaSpike
>  Issue Type: Sub-task
>  Components: Data-Module
>    Reporter: Daniel Cunha
>Assignee: Daniel Cunha
> Fix For: 1.6.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (DELTASPIKE-1101) Support aggregate functions

[Daniel Cunha (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Cunha updated DELTASPIKE-1101:
-
Description: 
Support aggregate functions. Examples:

{code:java}
Long countByName(String name);
Long countDistinctByName(String name);
Double sumPriceByCategory(Category category);
BigDecimal avgPriceByCategory(Category category);
{code}

> Support aggregate functions
> ---
>
> Key: DELTASPIKE-1101
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1101
> Project: DeltaSpike
>  Issue Type: Sub-task
>  Components: Data-Module
>    Reporter: Daniel Cunha
>Assignee: Daniel Cunha
>
> Support aggregate functions. Examples:
> {code:java}
> Long countByName(String name);
> Long countDistinctByName(String name);
> Double sumPriceByCategory(Category category);
> BigDecimal avgPriceByCategory(Category category);
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (DELTASPIKE-1103) Support GROUP BY and HAVING clauses

[Daniel Cunha (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Cunha updated DELTASPIKE-1103:
-
Description: 

Support GROUP BY and HAVING clauses. Examples:

{code:java}
List findByNameGroupByName(String name);
List findByNameGroupByNameHavingNameLike(String name);
{code}

> Support GROUP BY and HAVING clauses
> ---
>
> Key: DELTASPIKE-1103
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1103
> Project: DeltaSpike
>  Issue Type: Sub-task
>  Components: Data-Module
>    Reporter: Daniel Cunha
>Assignee: Daniel Cunha
>
> Support GROUP BY and HAVING clauses. Examples:
> {code:java}
> List findByNameGroupByName(String name);
> List findByNameGroupByNameHavingNameLike(String name);
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (DELTASPIKE-1102) Support TOP and FIRST

[Daniel Cunha (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Cunha updated DELTASPIKE-1102:
-
Description: 
Support TOP and FIRST. Examples:

{code:java}
void findTop10ByName(String name);
void findFirst10ByName(String name);
{code}

> Support TOP and FIRST
> -
>
> Key: DELTASPIKE-1102
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1102
> Project: DeltaSpike
>  Issue Type: Sub-task
>  Components: Data-Module
>    Reporter: Daniel Cunha
>Assignee: Daniel Cunha
>
> Support TOP and FIRST. Examples:
> {code:java}
> void findTop10ByName(String name);
> void findFirst10ByName(String name);
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (DELTASPIKE-1100) Support remove expressions

[Daniel Cunha (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212941#comment-15212941
 ] 

Daniel Cunha edited comment on DELTASPIKE-1100 at 3/26/16 10:29 AM:


This was implemented as deleteBy* -> 
https://issues.apache.org/jira/browse/DELTASPIKE-603
Just added support to use as removeBy*


was (Author: danielsoro):
This was implemented as removeBy* -> 
https://issues.apache.org/jira/browse/DELTASPIKE-603
Just added support to use as deleteBy*

> Support remove expressions
> --
>
> Key: DELTASPIKE-1100
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1100
> Project: DeltaSpike
>  Issue Type: Sub-task
>  Components: Data-Module
>Reporter: Daniel Cunha
>Assignee: Daniel Cunha
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (DELTASPIKE-1100) Support remove expressions

[Daniel Cunha (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212941#comment-15212941
 ] 

Daniel Cunha commented on DELTASPIKE-1100:
--

This was implemented as removeBy* -> 
https://issues.apache.org/jira/browse/DELTASPIKE-603
Just added support to use as deleteBy*

> Support remove expressions
> --
>
> Key: DELTASPIKE-1100
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1100
> Project: DeltaSpike
>  Issue Type: Sub-task
>  Components: Data-Module
>Reporter: Daniel Cunha
>Assignee: Daniel Cunha
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (DELTASPIKE-1103) Support GROUP BY and HAVING clauses

[Daniel Cunha (JIRA)]

Daniel Cunha created DELTASPIKE-1103:


 Summary: Support GROUP BY and HAVING clauses
 Key: DELTASPIKE-1103
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1103
 Project: DeltaSpike
  Issue Type: Sub-task
  Components: Data-Module
Reporter: Daniel Cunha
Assignee: Daniel Cunha






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (DELTASPIKE-1101) Support aggregate functions

[Daniel Cunha (JIRA)]

Daniel Cunha created DELTASPIKE-1101:


 Summary: Support aggregate functions
 Key: DELTASPIKE-1101
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1101
 Project: DeltaSpike
  Issue Type: Sub-task
  Components: Data-Module
Reporter: Daniel Cunha
Assignee: Daniel Cunha






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (DELTASPIKE-1102) Support TOP and FIRST

[Daniel Cunha (JIRA)]

Daniel Cunha created DELTASPIKE-1102:


 Summary: Support TOP and FIRST
 Key: DELTASPIKE-1102
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1102
 Project: DeltaSpike
  Issue Type: Sub-task
  Components: Data-Module
Reporter: Daniel Cunha
Assignee: Daniel Cunha






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DELTASPIKE-1100) Support remove expressions

[Daniel Cunha (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Cunha resolved DELTASPIKE-1100.
--
Resolution: Fixed

> Support remove expressions
> --
>
> Key: DELTASPIKE-1100
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1100
> Project: DeltaSpike
>  Issue Type: Sub-task
>  Components: Data-Module
>    Reporter: Daniel Cunha
>Assignee: Daniel Cunha
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (DELTASPIKE-1100) Support remove expressions

[Daniel Cunha (JIRA)]

Daniel Cunha created DELTASPIKE-1100:


 Summary: Support remove expressions
 Key: DELTASPIKE-1100
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1100
 Project: DeltaSpike
  Issue Type: Sub-task
  Components: Data-Module
Reporter: Daniel Cunha
Assignee: Daniel Cunha






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Move persistence.xml parser from DATA IMPL to JPA API

[Daniel Cunha]

Make sense having it on JPA module and not on Repository. IMHO.

+1 :)

On Wed, Mar 16, 2016 at 2:25 AM, Thomas Andraschko <
andraschko.tho...@gmail.com> wrote:

> Hi,
>
> currently it's not possible to access the persistence.xml properties via
> JPA API.
> As we have some code to do this (PersistenceUnitReader, PersistenceUnit,
> PersistenceUnits), we could provide it in the JPA module API.
>
> I would need it in my applications to check if HSQL used and switch the
> location.
>
> WDYT?
>
> Regards,
> Thomas
>



-- 
Daniel Cunha
https://twitter.com/dvlc_
http://www.tomitribe.com
http://www.tomitribe.io

Re: first steps for the next release

[Daniel Cunha]

+1

On Thu, Nov 26, 2015 at 8:09 AM, Christian Kaltepoth  wrote:

> +1
>
> 2015-11-26 11:37 GMT+01:00 Thomas Andraschko  >:
>
> > +1
> >
> > 2015-11-26 11:31 GMT+01:00 Gerhard Petracek  >:
> >
> > > hi @ all,
> > >
> > > if there are no objections, i will start with the first steps for the
> > next
> > > release (v1.5.2) by the end of next week.
> > >
> > > regards,
> > > gerhard
> > >
> >
>
>
>
> --
> Christian Kaltepoth
> Blog: http://blog.kaltepoth.de/
> Twitter: http://twitter.com/chkal
> GitHub: https://github.com/chkal
>



-- 
Daniel Cunha
https://twitter.com/dvlc_
http://www.tomitribe.com

[jira] [Resolved] (DELTASPIKE-839) Data module test deployments pack individual classes instead of JARs

[Daniel Cunha (soro) (JIRA)]

 [ 
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)

Re: [VOTE] Release of Apache DeltaSpike 1.5.1

[Daniel Cunha]

+1

On Sat, Oct 24, 2015 at 9:10 PM, Jason Porter 
wrote:

> Let's try this again +1
>
> On Saturday, October 24, 2015, Jason Porter 
> wrote:
>
> > +-
> >
> > On Saturday, October 24, 2015, Romain Manni-Bucau  > > wrote:
> >
> >> +1
> >> Le 24 oct. 2015 17:43, "Gerhard Petracek" 
> a
> >> écrit :
> >>
> >> > +1
> >> >
> >> > regards,
> >> > gerhard
> >> >
> >> >
> >> >
> >> > 2015-10-24 16:39 GMT+02:00 Gerhard Petracek <
> gerhard.petra...@gmail.com
> >> >:
> >> >
> >> > > Hi,
> >> > >
> >> > > I was running the needed tasks to get the 20th release of Apache
> >> > > DeltaSpike out.
> >> > > The artifacts are deployed to Nexus [1] (and [2]).
> >> > >
> >> > > The tag is available at [3] and the release-branch at [4].
> >> > > They will get pushed to the ASF repository once the vote passed.
> >> > >
> >> > > Please take a look at the 1.5.1 artifacts and vote!
> >> > >
> >> > > Please note:
> >> > > This vote is "majority approval" with a minimum of three +1 votes
> (see
> >> > > [5]).
> >> > >
> >> > > 
> >> > > [ ] +1 for community members who have reviewed the bits
> >> > > [ ] +0
> >> > > [ ] -1 for fatal flaws that should cause these bits not to be
> >> released,
> >> > > and why..
> >> > > 
> >> > >
> >> > > Thanks,
> >> > > Gerhard
> >> > >
> >> > > [1]
> >> > >
> >> >
> >>
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1030/
> >> > > [2]
> >> > >
> >> >
> >>
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1030/org/apache/deltaspike/deltaspike/1.5.1/deltaspike-1.5.1-source-release.zip
> >> > > [3] https://github.com/os890/deltaspike-vote/tree/deltaspike-1.5.1
> >> > > [4] https://github.com/os890/deltaspike-vote/tree/ds-1.5.1
> >> > > [5] http://www.apache.org/foundation/voting.html#ReleaseVotes
> >> > >
> >> >
> >>
> >
> >
> > --
> > Sent from Gmail Mobile
> >
>
>
> --
> Sent from Gmail Mobile
>



-- 
Daniel Cunha (soro)
https://twitter.com/dvlc_
http://www.tomitribe.com

Re: [VOTE] Release of Apache DeltaSpike 1.5.0

[Daniel Cunha]

+1

Em segunda-feira, 10 de agosto de 2015, Christian Kaltepoth <
christ...@kaltepoth.de> escreveu:

> +1
>
> 2015-08-10 4:35 GMT+02:00 Romain Manni-Bucau  >:
>
> > +1
> > Le 9 août 2015 19:03, "Gerhard Petracek"  > a écrit :
> >
> > > +1
> > >
> > > regards,
> > > gerhard
> > >
> > >
> > >
> > > 2015-08-10 4:02 GMT+02:00 Gerhard Petracek  >:
> > >
> > > > Hi,
> > > >
> > > > I was running the needed tasks to get the 19th release of Apache
> > > > DeltaSpike out.
> > > > The artifacts are deployed to Nexus [1] (and [2]).
> > > >
> > > > The tag is available at [3] and the release-branch at [4].
> > > > They will get pushed to the ASF repository once the vote passed.
> > > >
> > > > Please take a look at the 1.5.0 artifacts and vote!
> > > >
> > > > Please note:
> > > > This vote is "majority approval" with a minimum of three +1 votes
> (see
> > > > [5]).
> > > >
> > > > 
> > > > [ ] +1 for community members who have reviewed the bits
> > > > [ ] +0
> > > > [ ] -1 for fatal flaws that should cause these bits not to be
> released,
> > > > and why..
> > > > 
> > > >
> > > > Thanks,
> > > > Gerhard
> > > >
> > > > [1]
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1029/
> > > > [2]
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1029/org/apache/deltaspike/deltaspike/1.5.0/deltaspike-1.5.0-source-release.zip
> > > > [3] https://github.com/os890/deltaspike-vote/tree/deltaspike-1.5.0
> > > > [4] https://github.com/os890/deltaspike-vote/tree/ds-1.5.0
> > > > [5] http://www.apache.org/foundation/voting.html#ReleaseVotes
> > > >
> > >
> >
>
>
>
> --
> Christian Kaltepoth
> Blog: http://blog.kaltepoth.de/
> Twitter: http://twitter.com/chkal
> GitHub: https://github.com/chkal
>


-- 
Best regard,
Daniel Cunha (soro)

Re: Return type of Repository native query

[Daniel Cunha]

Very nice!!! :D

On Fri, Aug 7, 2015 at 5:45 PM, Thomas Hug  wrote:

> Hi Daniel
> Thnx yes I can take this one. It's about time I show up in Git history
> again :-)
>
> On Fri, Aug 7, 2015 at 6:19 PM, Daniel Cunha  wrote:
>
> > Thomas,
> >
> > if you don't have time to see it,  I can doing on next week.
> > Let me know if you have time to fix it
> >
> > On Fri, Aug 7, 2015 at 1:07 PM, akm  wrote:
> >
> > > Thanks Thomas for the response.
> > >
> > > It works with the workaround.
> > >
> > > Any idea if the bug will be fixed?
> > > Thanks
> > >
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > >
> >
> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Return-type-of-Repository-native-query-tp4661333p4661337.html
> > > Sent from the Apache DeltaSpike Incubator Discussions mailing list
> > archive
> > > at Nabble.com.
> > >
> >
> >
> >
> > --
> > Best regard,
> > Daniel Cunha (soro)
> >
>



-- 
Best regard,
Daniel Cunha (soro)

Re: Return type of Repository native query

[Daniel Cunha]

Hi Akm,

please, can you open an issue for it?
https://issues.apache.org/jira/browse/DELTASPIKE

Thank you.

On Fri, Aug 7, 2015 at 1:19 PM, Daniel Cunha  wrote:

> Thomas,
>
> if you don't have time to see it,  I can doing on next week.
> Let me know if you have time to fix it
>
> On Fri, Aug 7, 2015 at 1:07 PM, akm  wrote:
>
>> Thanks Thomas for the response.
>>
>> It works with the workaround.
>>
>> Any idea if the bug will be fixed?
>> Thanks
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Return-type-of-Repository-native-query-tp4661333p4661337.html
>> Sent from the Apache DeltaSpike Incubator Discussions mailing list
>> archive at Nabble.com.
>>
>
>
>
> --
> Best regard,
> Daniel Cunha (soro)
>



-- 
Best regard,
Daniel Cunha (soro)

Re: Return type of Repository native query

[Daniel Cunha]

Thomas,

if you don't have time to see it,  I can doing on next week.
Let me know if you have time to fix it

On Fri, Aug 7, 2015 at 1:07 PM, akm  wrote:

> Thanks Thomas for the response.
>
> It works with the workaround.
>
> Any idea if the bug will be fixed?
> Thanks
>
>
>
>
> --
> View this message in context:
> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Return-type-of-Repository-native-query-tp4661333p4661337.html
> Sent from the Apache DeltaSpike Incubator Discussions mailing list archive
> at Nabble.com.
>



-- 
Best regard,
Daniel Cunha (soro)

Re: v1.5.0 instead of v1.4.3

[Daniel Cunha]

+1

On Mon, Aug 3, 2015 at 6:33 PM, Romain Manni-Bucau 
wrote:

> +1
> Le 3 août 2015 22:44, "John D. Ament"  a écrit :
>
> > +0
> > These are all bug fixes, no major api changes that i can tell.
> >
> > On Mon, Aug 3, 2015 at 4:24 PM Gerhard Petracek 
> > wrote:
> >
> > > hi @ all,
> > >
> > > if there are no objections, i'll change the version number to 1.5.0
> > > >before< the next release.
> > >
> > > reasons:
> > >  - security fix
> > >  - changes for window-handling
> > >
> > > regards,
> > > gerhard
> > >
> >
>



-- 
Best regard,
Daniel Cunha (soro)

[jira] [Resolved] (DELTASPIKE-942) DeltaSpike fails to start with corrupted persistence.xml file.

[Daniel Cunha (soro) (JIRA)]

 [ 
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:
> {{META-INF/jpql/named-queries.xml}}
> # 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)

Re: first steps for the next release

[Daniel Cunha]

+1

On Tue, Jul 28, 2015 at 3:28 PM, Thomas Andraschko <
andraschko.tho...@gmail.com> wrote:

> +1
>
> 2015-07-28 19:52 GMT+02:00 Romain Manni-Bucau :
>
> > +1
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <http://rmannibucau.wordpress.com> | Github <
> > https://github.com/rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> > <http://www.tomitribe.com>
> >
> > 2015-07-28 10:21 GMT-07:00 Gerhard Petracek :
> >
> > > hi @ all,
> > >
> > > if there are no objections, i will start with the first steps for the
> > next
> > > release (v1.4.3) by the end of next week.
> > >
> > > regards,
> > > gerhard
> > >
> >
>



-- 
Best regard,
Daniel Cunha (soro)

[jira] [Resolved] (DELTASPIKE-853) Use @Stereotype for interface/enum discovery

[Daniel Cunha (soro) (JIRA)]

 [ 
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] [Commented] (DELTASPIKE-965) EntityRepository.save() is broken for entities with String ID

[Daniel Cunha (soro) (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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

[Daniel Cunha (soro) (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] [Assigned] (DELTASPIKE-965) EntityRepository.save() is broken for entities with String ID

[Daniel Cunha (soro) (JIRA)]

 [ 
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

[Daniel Cunha (soro) (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] [Resolved] (DELTASPIKE-943) Provide add() methods instead of save() methods in EntityRepository

[Daniel Cunha (soro) (JIRA)]

 [ 
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)

DELTASPIKE-943

[Daniel Cunha]

Hi folks,

https://issues.apache.org/jira/browse/DELTASPIKE-943

I think that save makes more sense IMHO, maybe the user can to extend
EntityRepository and create add(E entity) method if he wants.

I don't know if this is really cool create add(E entity).. WDYT? :)

-- 
Best regard,
Daniel Cunha (soro)

[jira] [Updated] (DELTASPIKE-943) Provide add() methods instead of save() methods in EntityRepository

[Daniel Cunha (soro) (JIRA)]

 [ 
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)

Re: [VOTE] Release of Apache DeltaSpike 1.4.2

[Daniel Cunha]

Hi @John,

I saw your comment, but Gerhard already reply.
If you have another things to check, let me know what you need.

My vote is: +1


On Mon, Jul 20, 2015 at 10:46 AM, Christian Kaltepoth <
christ...@kaltepoth.de> wrote:

> +1
>
> 2015-07-20 14:24 GMT+02:00 Rafael Benevides :
>
> > +1 for me.
> >
> > - Mensagem original -
> > De: "Gerhard Petracek" 
> > Para: dev@deltaspike.apache.org
> > Enviadas: Domingo, 19 de julho de 2015 14:11:10
> > Assunto: [VOTE] Release of Apache DeltaSpike 1.4.2
> >
> > Hi,
> >
> > I was running the needed tasks to get the 18th release of Apache
> DeltaSpike
> > out.
> > The artifacts are deployed to Nexus [1] (and [2]).
> >
> > The tag is available at [3] and the release-branch at [4].
> > They will get pushed to the ASF repository once the vote passed.
> >
> > Please take a look at the 1.4.2 artifacts and vote!
> >
> > Please note:
> > This vote is "majority approval" with a minimum of three +1 votes (see
> > [5]).
> >
> > 
> > [ ] +1 for community members who have reviewed the bits
> > [ ] +0
> > [ ] -1 for fatal flaws that should cause these bits not to be released,
> and
> > why..
> > 
> >
> > Thanks,
> > Gerhard
> >
> > [1]
> >
> >
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1028/
> > [2]
> >
> >
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1028/org/apache/deltaspike/deltaspike/1.4.2/deltaspike-1.4.2-source-release.zip
> > [3] https://github.com/os890/deltaspike-vote/tree/deltaspike-1.4.2
> > [4] https://github.com/os890/deltaspike-vote/tree/ds-1.4.2
> > [5] http://www.apache.org/foundation/voting.html#ReleaseVotes
> >
>
>
>
> --
> Christian Kaltepoth
> Blog: http://blog.kaltepoth.de/
> Twitter: http://twitter.com/chkal
> GitHub: https://github.com/chkal
>



-- 
Best regard,
Daniel Cunha (soro)

[jira] [Commented] (DELTASPIKE-942) DeltaSpike fails to start with corrupted persistence.xml file.

[Daniel Cunha (soro) (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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:
> {{META-INF/jpql/named-queries.xml}}
> # 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)

Re: Cascade persist and merge with Repository.

[Daniel Cunha]

You're welcome. :)

On Fri, Jul 10, 2015 at 4:18 PM, akm  wrote:

> Thanks for all the help you have provided, appreciate it a lot.
>
>
>
> --
> View this message in context:
> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Cascade-persist-and-merge-with-Repository-tp4661002p4661045.html
> Sent from the Apache DeltaSpike Incubator Discussions mailing list archive
> at Nabble.com.
>



-- 
Best regard,
Daniel Cunha (soro)

Re: Scope of Entity Manager

[Daniel Cunha]

Akm,

@RequestScoped:
EntityManager is producing it as request scoped bean means that the
disposer method will be called on finishing the request.

@TransactionScoped:
Will be closed after leaving the method annotated with @Transactional.

That will depend on the your architecture, you can select what is better
for you.


On Fri, Jul 10, 2015 at 4:15 PM, akm  wrote:

> Does DeltaSpike have any recommendation on the the scope of the Entity
> Manager that will be used by the Repository?
> I have tried both the @RequestScoped and the @TransactionScoped and would
> like to know which DeltaSpike recommends and why.
> Thanks
>
>
>
> --
> View this message in context:
> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Scope-of-Entity-Manager-tp4661043.html
> Sent from the Apache DeltaSpike Incubator Discussions mailing list archive
> at Nabble.com.
>



-- 
Best regard,
Daniel Cunha (soro)

Re: Cascade persist and merge with Repository.

[Daniel Cunha]

Akm,

CdiTestRunner could be some catch there, sorry I'm not expert with
test-control module.
About non-auto generated keys, you should not have problem, really was a
isolate bug.

On Fri, Jul 10, 2015 at 3:57 PM, akm  wrote:

> I had another question
> Since this was due to the non portability of non-auto generated keys, is
> there any other impact of using non-auto generated keys?
> We use uuids and was just wondering if you have any recommendations on the
> usage of generated sakeys versus uuids for primary key.
> Thanks
>
>
>
> --
> View this message in context:
> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Cascade-persist-and-merge-with-Repository-tp4661002p4661042.html
> Sent from the Apache DeltaSpike Incubator Discussions mailing list archive
> at Nabble.com.
>



-- 
Best regard,
Daniel Cunha (soro)

Re: Cascade persist and merge with Repository.

[Daniel Cunha]

Akm,

weird,

here deltaspike return this:

Failed calling Repository:
[Repository=com.myApp.entities.BookingRepository,entity=com.myApp.entities.Booking,method=save,exception=class
java.lang.IllegalStateException,message=During synchronization a new object
was found through a relationship that was not marked cascade PERSIST:
com.myApp.entities.Adventure@310f0653.

It's ok for me.
It shows the: repository, method, exception and message




On Fri, Jul 10, 2015 at 3:13 PM, Daniel Cunha  wrote:

> Akm,
>
> looking for it.
>
> On Fri, Jul 10, 2015 at 11:40 AM, akm  wrote:
>
>> Thanks. This works now.
>>
>> The exception that I get has a null message. Is this intentional or should
>> it have the EclipseLink error message?
>> *The EclipseLink error is -*
>> Caused by: java.lang.IllegalStateException: During synchronization a new
>> object was found through a relationship that was not marked cascade
>> PERSIST:
>> com.myApp.entities.Adventure@8e44be4.
>> at
>>
>> org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.discoverUnregisteredNewObjects(RepeatableWriteUnitOfWork.java:303)
>>
>>
>> *The Repository message is*
>> INFO: [failed]
>>
>> test.com.myApp.it.test.CascadeTestWithRepository#createBookingWithRepository
>> message: Failed calling Repository:
>>
>> [Repository=com.myApp.entities.BookingRepository,entity=com.myApp.entities.Booking,method=saveAndFlush,exception=class
>> org.apache.deltaspike.data.api.QueryInvocationException,message=Failed
>> calling Repository:
>>
>> [Repository=com.myApp.entities.BookingRepository,entity=com.myApp.entities.Booking,method=saveAndFlush,exception=class
>> org.apache.deltaspike.data.api.QueryInvocationException,message=Failed
>> calling Repository:
>>
>> [Repository=com.myApp.entities.BookingRepository,entity=com.myApp.entities.Booking,method=saveAndFlush,exception=class
>> java.lang.reflect.InvocationTargetException,*message=null*
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Cascade-persist-and-merge-with-Repository-tp4661002p4661037.html
>> Sent from the Apache DeltaSpike Incubator Discussions mailing list
>> archive at Nabble.com.
>>
>
>
>
> --
> Best regard,
> Daniel Cunha (soro)
>



-- 
Best regard,
Daniel Cunha (soro)

Re: Cascade persist and merge with Repository.

[Daniel Cunha]

Akm,

looking for it.

On Fri, Jul 10, 2015 at 11:40 AM, akm  wrote:

> Thanks. This works now.
>
> The exception that I get has a null message. Is this intentional or should
> it have the EclipseLink error message?
> *The EclipseLink error is -*
> Caused by: java.lang.IllegalStateException: During synchronization a new
> object was found through a relationship that was not marked cascade
> PERSIST:
> com.myApp.entities.Adventure@8e44be4.
> at
>
> org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.discoverUnregisteredNewObjects(RepeatableWriteUnitOfWork.java:303)
>
>
> *The Repository message is*
> INFO: [failed]
>
> test.com.myApp.it.test.CascadeTestWithRepository#createBookingWithRepository
> message: Failed calling Repository:
>
> [Repository=com.myApp.entities.BookingRepository,entity=com.myApp.entities.Booking,method=saveAndFlush,exception=class
> org.apache.deltaspike.data.api.QueryInvocationException,message=Failed
> calling Repository:
>
> [Repository=com.myApp.entities.BookingRepository,entity=com.myApp.entities.Booking,method=saveAndFlush,exception=class
> org.apache.deltaspike.data.api.QueryInvocationException,message=Failed
> calling Repository:
>
> [Repository=com.myApp.entities.BookingRepository,entity=com.myApp.entities.Booking,method=saveAndFlush,exception=class
> java.lang.reflect.InvocationTargetException,*message=null*
>
>
>
> --
> View this message in context:
> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Cascade-persist-and-merge-with-Repository-tp4661002p4661037.html
> Sent from the Apache DeltaSpike Incubator Discussions mailing list archive
> at Nabble.com.
>



-- 
Best regard,
Daniel Cunha (soro)

Re: Cascade persist and merge with Repository.

[Daniel Cunha]

+1

On Fri, Jul 10, 2015 at 5:24 AM, Gerhard Petracek 
wrote:

> fyi:
> the snapshot-deployment via ci-job is active again.
>
> regards,
> gerhard
>
>
>
> 2015-07-09 19:18 GMT+02:00 Gerhard Petracek :
>
> > i just deployed a new snapshot manually.
> >
> > regards,
> > gerhard
> >
> >
> >
> > 2015-07-09 17:03 GMT+02:00 akm :
> >
> >> Do you have any estimate on when the snapshot will be ready?
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Cascade-persist-and-merge-with-Repository-tp4661002p4661025.html
> >> Sent from the Apache DeltaSpike Incubator Discussions mailing list
> >> archive at Nabble.com.
> >>
> >
> >
>



-- 
Best regard,
Daniel Cunha (soro)

Re: Cascade persist and merge with Repository.

[Daniel Cunha]

Ah..

thanks Gerhard. :)

On Thu, Jul 9, 2015 at 10:54 AM, Daniel Cunha  wrote:

> Hmm,
>
> not deployed to nexus yet. (I don't have acknowledgment about this process
> [snapshot nexus deploy])
> You can build the source as well.
>
>
> On Thu, Jul 9, 2015 at 10:24 AM, akm  wrote:
>
>> I just got the 1.4.2-SNAPSHOT from the
>> http://repository.apache.org/snapshots
>> repository, but it still behavahes the same way.
>>
>> I do not see any change in the isNew method code.
>>
>>   public boolean isNew(Object entity)
>> {
>> try
>> {
>> return
>>
>> entityManager.getEntityManagerFactory().getPersistenceUnitUtil().getIdentifier(entity)
>> == null;
>> }
>> catch (IllegalArgumentException e)
>> {
>> // Not an entity
>> return false;
>> }
>> }
>>
>> Should I be getting the sanpshot from some another repo?
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Cascade-persist-and-merge-with-Repository-tp4661002p4661020.html
>> Sent from the Apache DeltaSpike Incubator Discussions mailing list
>> archive at Nabble.com.
>>
>
>
>
> --
> Best regard,
> Daniel Cunha (soro)
>



-- 
Best regard,
Daniel Cunha (soro)

Re: Cascade persist and merge with Repository.

[Daniel Cunha]

Hmm,

not deployed to nexus yet. (I don't have acknowledgment about this process
[snapshot nexus deploy])
You can build the source as well.


On Thu, Jul 9, 2015 at 10:24 AM, akm  wrote:

> I just got the 1.4.2-SNAPSHOT from the
> http://repository.apache.org/snapshots
> repository, but it still behavahes the same way.
>
> I do not see any change in the isNew method code.
>
>   public boolean isNew(Object entity)
> {
> try
> {
> return
>
> entityManager.getEntityManagerFactory().getPersistenceUnitUtil().getIdentifier(entity)
> == null;
> }
> catch (IllegalArgumentException e)
> {
> // Not an entity
> return false;
> }
> }
>
> Should I be getting the sanpshot from some another repo?
>
>
>
> --
> View this message in context:
> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Cascade-persist-and-merge-with-Repository-tp4661002p4661020.html
> Sent from the Apache DeltaSpike Incubator Discussions mailing list archive
> at Nabble.com.
>



-- 
Best regard,
Daniel Cunha (soro)

Re: Cascade persist and merge with Repository.

[Daniel Cunha]

Hi Akm,

Fixed in SNAPSHOT.
you can test with it (1.4.2-SNAPSHOT).

Thank you for reporting.

On Wed, Jul 8, 2015 at 5:21 PM, akm  wrote:

> I will try to override the isNew method.
>
> We have non auto generated keys for what we consider "Lookup" type of
> Entities. example country, city, state.
>
>
>
> --
> View this message in context:
> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Cascade-persist-and-merge-with-Repository-tp4661002p4661011.html
> Sent from the Apache DeltaSpike Incubator Discussions mailing list archive
> at Nabble.com.
>



-- 
Best regard,
Daniel Cunha (soro)

[jira] [Resolved] (DELTASPIKE-948) CdiQueryInvocationContext#isNew isn't portable across jpa providers

[Daniel Cunha (soro) (JIRA)]

 [ 
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] [Updated] (DELTASPIKE-948) CdiQueryInvocationContext#isNew isn't portable across jpa providers

[Daniel Cunha (soro) (JIRA)]

 [ 
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] [Updated] (DELTASPIKE-948) CdiQueryInvocationContext#isNew isn't portable across jpa providers

[Daniel Cunha (soro) (JIRA)]

 [ 
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

[Daniel Cunha (soro) (JIRA)]

 [ 
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

[Daniel Cunha (soro) (JIRA)]

 [ 
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] [Created] (DELTASPIKE-948) CdiQueryInvocationContext#isNew isn't portable across jpa providers

[Daniel Cunha (soro) (JIRA)]

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)

Re: Cascade persist and merge with Repository.

[Daniel Cunha]

Hi akm,

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 use 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.

you could use a specialized bean for
org.apache.deltaspike.data.impl.handler.CdiQueryInvocationContext and just
override #isNew if you can't wait for the next release.



On Wed, Jul 8, 2015 at 1:36 PM, Daniel Cunha  wrote:

> Akm,
>
> I'm looking for it.
> Thank you. :)
>
>
>
> On Wed, Jul 8, 2015 at 12:59 PM, akm  wrote:
>
>> I have attached a simple gradle  CascadeRefreshGradleTestProject.zip
>> <
>> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/file/n4661005/CascadeRefreshGradleTestProject.zip
>> >
>> project with unit tests.
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Cascade-persist-and-merge-with-Repository-tp4661002p4661005.html
>> Sent from the Apache DeltaSpike Incubator Discussions mailing list
>> archive at Nabble.com.
>>
>
>
>
> --
> Best regard,
> Daniel Cunha (soro)
>



-- 
Best regard,
Daniel Cunha (soro)

Re: Cascade persist and merge with Repository.

[Daniel Cunha]

Akm,

I'm looking for it.
Thank you. :)



On Wed, Jul 8, 2015 at 12:59 PM, akm  wrote:

> I have attached a simple gradle  CascadeRefreshGradleTestProject.zip
> <
> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/file/n4661005/CascadeRefreshGradleTestProject.zip
> >
> project with unit tests.
>
>
>
>
> --
> View this message in context:
> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Cascade-persist-and-merge-with-Repository-tp4661002p4661005.html
> Sent from the Apache DeltaSpike Incubator Discussions mailing list archive
> at Nabble.com.
>



-- 
Best regard,
Daniel Cunha (soro)

Re: Cascade persist and merge with Repository.

[Daniel Cunha]

DelegatingMethodAccessorImpl.java:37)
> > at java.lang.reflect.Method.invoke(Method.java:611)
> > at
> >
> >
> org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:40)
> > at
> >
> >
> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100)
> > at
> >
> >
> org.jboss.weld.proxies.EntityManager$1729017240$Proxy$_$$_WeldClientProxy.flush(Unknown
> > Source)
> > at
> >
> >
> com.myApp..booking.jpa.BookingDeJpaRelationshipAnnotationsIntTest.cannotCreateNewAdventureFromBookingJPA(BookingDeJpaRelationshipAnnotationsIntTest.java:132)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> >
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
> > at
> >
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
> > at java.lang.reflect.Method.invoke(Method.java:611)
> > at
> >
> >
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> > at
> >
> >
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> > at
> >
> >
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> > at
> >
> >
> org.apache.deltaspike.testcontrol.api.junit.CdiTestRunner$ContainerAwareMethodInvoker.invokeMethod(CdiTestRunner.java:340)
> > at
> >
> >
> org.apache.deltaspike.testcontrol.api.junit.CdiTestRunner$ContainerAwareMethodInvoker.evaluate(CdiTestRunner.java:312)
> > at
> >
> >
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> > at
> >
> >
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> > at
> >
> >
> org.apache.deltaspike.testcontrol.api.junit.CdiTestRunner.runChild(CdiTestRunner.java:174)
> > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> > at
> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> > at
> > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> > at
> org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> > at
> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> > at
> >
> >
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> > at
> >
> >
> org.apache.deltaspike.testcontrol.api.junit.CdiTestRunner$BeforeClassStatement.evaluate(CdiTestRunner.java:366)
> > at
> >
> >
> org.apache.deltaspike.testcontrol.api.junit.CdiTestRunner$AfterClassStatement.evaluate(CdiTestRunner.java:392)
> > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> > at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> > at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> > at
> >
> >
> org.apache.deltaspike.testcontrol.api.junit.CdiTestRunner.run(CdiTestRunner.java:141)
> > at
> >
> >
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> > at
> >
> >
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> > at
> >
> >
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> > at
> >
> >
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> > at
> >
> >
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> > at
> >
> >
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
> >
> >
> >
> >
> > --
> > View this message in context:
> >
> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Cascade-persist-and-merge-with-Repository-tp4661002.html
> > Sent from the Apache DeltaSpike Incubator Discussions mailing list
> archive
> > at Nabble.com.
> >
>



-- 
Best regard,
Daniel Cunha (soro)

Re: Data and JPA module

[Daniel Cunha]

Thomas,

I get it.
Thank you.

On Wed, Jul 1, 2015 at 6:51 AM, Thomas Hug  wrote:

> Hi Daniel
> AFAIR we have a hook in the JPA module [1][2] where we can propagate the
> repository EM to the transaction strategy (DefaultEntityManagerHolder and
> [3]). So EntityManagerResolver should have precedence, but it depends
> overall on the TransactionStrategy if it's picked up or not.
>
> Agree that it would be nice to be consistent here. EntityManagerConfig was
> introduced AFAIR to have the same concept as MessageContextConfig /
> Resolver in the JSF module. The current @Transactional way works not with
> qualifier attributes.
>
> [1]
>
> https://github.com/apache/deltaspike/blob/master/deltaspike/modules/jpa/api/src/main/java/org/apache/deltaspike/jpa/spi/entitymanager/ActiveEntityManagerHolder.java
> [2]
>
> https://github.com/apache/deltaspike/blob/master/deltaspike/modules/jpa/impl/src/main/java/org/apache/deltaspike/jpa/impl/transaction/ResourceLocalTransactionStrategy.java#L87
> [3]
>
> https://github.com/apache/deltaspike/blob/master/deltaspike/modules/data/impl/src/main/java/org/apache/deltaspike/data/impl/tx/TransactionalQueryRunner.java
>
> On Tue, Jun 30, 2015 at 9:40 PM, Daniel Cunha 
> wrote:
>
> > Hi folks,
> >
> > we have a new issue little bit weird.
> > https://issues.apache.org/jira/browse/DELTASPIKE-940
> >
> > My doubt is:
> > If we have define EntityManagerConfig in ours Repository, so.. Do we use
> > the @Transactional in some method, what is assumed?
> > @Transactional or the EntityManagerResolver in EntityManagerConfig?
> >
> > On Tue, Jun 30, 2015 at 4:38 PM, Daniel Cunha 
> > wrote:
> >
> > > Hi folks,
> > >
> > > we have a new issue little bit weird.
> > > https://issues.apache.org/jira/browse/DELTASPIKE-940
> > >
> > > My doubt is:
> > > If we have define EntityManagerConfig in ours Repository, so.. we does'
> > >
> > > --
> > > Best regard,
> > > Daniel Cunha (soro)
> > >
> >
> >
> >
> > --
> > Best regard,
> > Daniel Cunha (soro)
> >
>



-- 
Best regard,
Daniel Cunha (soro)

[jira] [Resolved] (DELTASPIKE-871) save() and findByxxx() in same transaction gives constraint violation exception

[Daniel Cunha (soro) (JIRA)]

 [ 
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] [Commented] (DELTASPIKE-871) save() and findByxxx() in same transaction gives constraint violation exception

[Daniel Cunha (soro) (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] [Updated] (DELTASPIKE-910) Add EntityRepository.getPrimaryKey(E entity)

[Daniel Cunha (soro) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Cunha (soro) updated DELTASPIKE-910:
---
Fix Version/s: 1.4.2

> 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
> Fix For: 1.4.2
>
>
> 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] [Updated] (DELTASPIKE-941) JPA link broken in Data Module documentation

[Daniel Cunha (soro) (JIRA)]

 [ 
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] [Updated] (DELTASPIKE-673) CdiQueryInvocationContext#isNew does not work well with OpenJpa and detached entities

[Daniel Cunha (soro) (JIRA)]

 [ 
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)

Re: [MARKETING] LinkedIn Group

[Daniel Cunha]

Hi folks,

typo fixed.
Site updated. :)

On Mon, Jun 29, 2015 at 4:55 PM, Daniel Cunha  wrote:

> Hi Marvin,
>
> it will be fixed with the next site-update.
>
> Thank you for reporting.
>
> On Sun, Jun 28, 2015 at 8:38 PM, MarvinToll 
> wrote:
>
>> By the way.. it would be great if the typo on the home page could be
>> fixed...
>> it has been incorrect for many months:
>>
>> In 2014, DeltaSpike become a Duke’s Choice Award winner.
>>
>> Should read:
>>
>> In 2014, DeltaSpike became a Duke’s Choice Award winner.
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/MARKETING-LinkedIn-Group-tp4660955p4660959.html
>> Sent from the Apache DeltaSpike Incubator Discussions mailing list
>> archive at Nabble.com.
>>
>
>
>
> --
> Best regard,
> Daniel Cunha (soro)
>



-- 
Best regard,
Daniel Cunha (soro)

[jira] [Resolved] (DELTASPIKE-941) JPA link broken in Data Module documentation

[Daniel Cunha (soro) (JIRA)]

 [ 
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) (JIRA)]

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-448) Review exception handling in Data module

[Daniel Cunha (soro) (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)

Re: Data and JPA module

[Daniel Cunha]

Hi folks,

we have a new issue little bit weird.
https://issues.apache.org/jira/browse/DELTASPIKE-940

My doubt is:
If we have define EntityManagerConfig in ours Repository, so.. Do we use
the @Transactional in some method, what is assumed?
@Transactional or the EntityManagerResolver in EntityManagerConfig?

On Tue, Jun 30, 2015 at 4:38 PM, Daniel Cunha  wrote:

> Hi folks,
>
> we have a new issue little bit weird.
> https://issues.apache.org/jira/browse/DELTASPIKE-940
>
> My doubt is:
> If we have define EntityManagerConfig in ours Repository, so.. we does'
>
> --
> Best regard,
> Daniel Cunha (soro)
>



-- 
Best regard,
Daniel Cunha (soro)

Data and JPA module

[Daniel Cunha]

Hi folks,

we have a new issue little bit weird.
https://issues.apache.org/jira/browse/DELTASPIKE-940

My doubt is:
If we have define EntityManagerConfig in ours Repository, so.. we does'

-- 
Best regard,
Daniel Cunha (soro)

Re: [MARKETING] LinkedIn Group

[Daniel Cunha]

Hi Marvin,

it will be fixed with the next site-update.

Thank you for reporting.

On Sun, Jun 28, 2015 at 8:38 PM, MarvinToll  wrote:

> By the way.. it would be great if the typo on the home page could be
> fixed...
> it has been incorrect for many months:
>
> In 2014, DeltaSpike become a Duke’s Choice Award winner.
>
> Should read:
>
> In 2014, DeltaSpike became a Duke’s Choice Award winner.
>
>
>
> --
> View this message in context:
> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/MARKETING-LinkedIn-Group-tp4660955p4660959.html
> Sent from the Apache DeltaSpike Incubator Discussions mailing list archive
> at Nabble.com.
>



-- 
Best regard,
Daniel Cunha (soro)

[jira] [Commented] (DELTASPIKE-871) save() and findByxxx() in same transaction gives constraint violation exception

[Daniel Cunha (soro) (JIRA)]

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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

[Daniel Cunha (soro) (JIRA)]

 [ 
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)

[Daniel Cunha (soro) (JIRA)]

 [ 
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] [Resolved] (DELTASPIKE-934) @Query metadata should be considered for any method expression

[Daniel Cunha (soro) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Cunha (soro) resolved DELTASPIKE-934.

Resolution: Fixed

> @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] [Created] (DELTASPIKE-934) @Query metadata should be considered for any method expression

[Daniel Cunha (soro) (JIRA)]

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)

Re: DeltaSpike Data Module Repository

[Daniel Cunha]

Thomas,

sounds good:
https://github.com/danielsoro/deltaspike/commit/ff9a42704547a7373421400960a09b056288ca1c
?

On Fri, Jun 12, 2015 at 5:32 PM, Daniel Cunha  wrote:

> +1
>
> On Fri, Jun 12, 2015 at 8:42 AM, Thomas Hug  wrote:
>
>> Oooh I see... I should really find time to code here more often. Looks
>> like
>> I forgot about a lot of this code :-D
>>
>> Maybe a little refactoring might help to clean this up. E.g. moving the
>> applyRestrictions into the QueryInvocationContext (resp. into a class
>> being
>> called by the context) so it is simpler to reuse it. Being forced to
>> extend
>> QueryBuilder seems not right to me. WDYT?
>>
>>
>> On Fri, Jun 12, 2015 at 10:52 AM, Daniel Cunha 
>> wrote:
>>
>> > Thomas,
>> >
>> > Sure!
>> >
>> > MethodQueryBuilder already do it. [1]
>> > I see for Delegate[2], but.. really, I don't know how to apply it here.
>> :(
>> >
>> > [1]
>> >
>> >
>> https://github.com/danielsoro/deltaspike/blob/applyRestrictions/deltaspike/modules/data/impl/src/main/java/org/apache/deltaspike/data/impl/builder/MethodQueryBuilder.java#L48
>> >
>> > [2]
>> >
>> >
>> https://github.com/danielsoro/deltaspike/blob/applyRestrictions/deltaspike/modules/data/impl/src/main/java/org/apache/deltaspike/data/impl/builder/DelegateQueryBuilder.java
>> >
>> > On Fri, Jun 12, 2015 at 4:39 AM, Thomas Hug 
>> wrote:
>> >
>> > > Thanks Daniel for checking! Different reason it doesn't work than I
>> had
>> > in
>> > > memory :-)
>> > > I think we should go for a general solution and not just for
>> > > EntityRepository methods, @Query metadata should be considered for any
>> > > method expression. The place to change this is probably somewhere in
>> > > Delegate- and MethodQueryBuilder.
>> > >
>> > > On Fri, Jun 12, 2015 at 4:19 AM, Daniel Cunha 
>> > > wrote:
>> > >
>> > > > Thomas,
>> > > >
>> > > > you're right, not work.
>> > > > I changed and works now[1], but I don't know if this is the better
>> way
>> > to
>> > > > fix it.
>> > > >
>> > > >
>> > > >
>> > >
>> >
>> https://github.com/danielsoro/deltaspike/commit/bb02f14731e9c7fd5d20c255bae2a2033617a9b8
>> > > >
>> > > > On Thu, Jun 11, 2015 at 4:11 PM, Thomas Hug 
>> > > wrote:
>> > > >
>> > > > > Using the @Query(hints...) is the place to set the hints with DS
>> > Data.
>> > > > > Unfortunately (hope my memory isn't wrong) this currently doesn't
>> > work
>> > > > with
>> > > > > a method expression. As soon as there's a @Query it's not
>> considered
>> > a
>> > > > > method expression anymore.
>> > > > >
>> > > > > Should not be too difficult to change - and should be changed as
>> the
>> > > > sample
>> > > > > from Daniel makes totally sense :-) Will check this tomorrow and
>> > > create a
>> > > > > JIRA issue.
>> > > > >
>> > > > >
>> > > > >
>> > > > > On Thu, Jun 11, 2015 at 5:42 PM, Daniel Cunha <
>> daniels...@gmail.com>
>> > > > > wrote:
>> > > > >
>> > > > > > Hmm..
>> > > > > >
>> > > > > > so, that's should work:
>> > > > > >
>> > > > > > ```
>> > > > > > @Repository
>> > > > > > public interface SimpleRepository extends
>> EntityRepository> > > > Long>
>> > > > > > {
>> > > > > >
>> > > > > > @Override
>> > > > > > @Query(hints = {@QueryHint(name =
>> > > > > "javax.persistence.cache.storeMode",
>> > > > > > value = BYPASS)})
>> > > > > > List findAll();
>> > > > > > }
>> > > > > > ```
>> > > > > >
>> > > > > > On Thu, Jun 11, 2015 at 11:53 AM, akm  wrote:
>> > > > > >
>> > > > > > > Thanks for the reply.
>> > > > > > >
>> > > > > &g

Re: [VOTE] Release of Apache DeltaSpike 1.4.1

[Daniel Cunha]

+1

On Sat, Jun 13, 2015 at 6:45 AM, Romain Manni-Bucau 
wrote:

> +1
> Le 13 juin 2015 10:56, "Harald Wellmann"  a écrit
> :
>
> > +1
> >
> > Regards,
> > Harald
> >
> > Am 12.06.2015 um 23:23 schrieb Gerhard Petracek:
> >
> >> Hi,
> >>
> >> I was running the needed tasks to get the 17th release of Apache
> >> DeltaSpike
> >> out.
> >> The artifacts are deployed to Nexus [1] (and [2]).
> >>
> >> The tag is available at [3] and the release-branch at [4].
> >> They will get pushed to the ASF repository once the vote passed.
> >>
> >> Please take a look at the 1.4.1 artifacts and vote!
> >>
> >> Please note:
> >> This vote is "majority approval" with a minimum of three +1 votes (see
> >> [5]).
> >>
> >> 
> >> [ ] +1 for community members who have reviewed the bits
> >> [ ] +0
> >> [ ] -1 for fatal flaws that should cause these bits not to be released,
> >> and
> >> why..
> >> 
> >>
> >> Thanks,
> >> Gerhard
> >>
> >> [1]
> >>
> >>
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1027/
> >> [2]
> >>
> >>
> https://repository.apache.org/content/repositories/orgapachedeltaspike-1027/org/apache/deltaspike/deltaspike/1.4.1/deltaspike-1.4.1-source-release.zip
> >> [3] https://github.com/os890/deltaspike-vote/tree/deltaspike-1.4.1
> >> [4] https://github.com/os890/deltaspike-vote/tree/ds-1.4.1
> >> [5] http://www.apache.org/foundation/voting.html#ReleaseVotes
> >>
> >>
> >
>



-- 
Best regard,
Daniel Cunha (soro)

Re: DeltaSpike Data Module Repository

[Daniel Cunha]

+1

On Fri, Jun 12, 2015 at 8:42 AM, Thomas Hug  wrote:

> Oooh I see... I should really find time to code here more often. Looks like
> I forgot about a lot of this code :-D
>
> Maybe a little refactoring might help to clean this up. E.g. moving the
> applyRestrictions into the QueryInvocationContext (resp. into a class being
> called by the context) so it is simpler to reuse it. Being forced to extend
> QueryBuilder seems not right to me. WDYT?
>
>
> On Fri, Jun 12, 2015 at 10:52 AM, Daniel Cunha 
> wrote:
>
> > Thomas,
> >
> > Sure!
> >
> > MethodQueryBuilder already do it. [1]
> > I see for Delegate[2], but.. really, I don't know how to apply it here.
> :(
> >
> > [1]
> >
> >
> https://github.com/danielsoro/deltaspike/blob/applyRestrictions/deltaspike/modules/data/impl/src/main/java/org/apache/deltaspike/data/impl/builder/MethodQueryBuilder.java#L48
> >
> > [2]
> >
> >
> https://github.com/danielsoro/deltaspike/blob/applyRestrictions/deltaspike/modules/data/impl/src/main/java/org/apache/deltaspike/data/impl/builder/DelegateQueryBuilder.java
> >
> > On Fri, Jun 12, 2015 at 4:39 AM, Thomas Hug 
> wrote:
> >
> > > Thanks Daniel for checking! Different reason it doesn't work than I had
> > in
> > > memory :-)
> > > I think we should go for a general solution and not just for
> > > EntityRepository methods, @Query metadata should be considered for any
> > > method expression. The place to change this is probably somewhere in
> > > Delegate- and MethodQueryBuilder.
> > >
> > > On Fri, Jun 12, 2015 at 4:19 AM, Daniel Cunha 
> > > wrote:
> > >
> > > > Thomas,
> > > >
> > > > you're right, not work.
> > > > I changed and works now[1], but I don't know if this is the better
> way
> > to
> > > > fix it.
> > > >
> > > >
> > > >
> > >
> >
> https://github.com/danielsoro/deltaspike/commit/bb02f14731e9c7fd5d20c255bae2a2033617a9b8
> > > >
> > > > On Thu, Jun 11, 2015 at 4:11 PM, Thomas Hug 
> > > wrote:
> > > >
> > > > > Using the @Query(hints...) is the place to set the hints with DS
> > Data.
> > > > > Unfortunately (hope my memory isn't wrong) this currently doesn't
> > work
> > > > with
> > > > > a method expression. As soon as there's a @Query it's not
> considered
> > a
> > > > > method expression anymore.
> > > > >
> > > > > Should not be too difficult to change - and should be changed as
> the
> > > > sample
> > > > > from Daniel makes totally sense :-) Will check this tomorrow and
> > > create a
> > > > > JIRA issue.
> > > > >
> > > > >
> > > > >
> > > > > On Thu, Jun 11, 2015 at 5:42 PM, Daniel Cunha <
> daniels...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hmm..
> > > > > >
> > > > > > so, that's should work:
> > > > > >
> > > > > > ```
> > > > > > @Repository
> > > > > > public interface SimpleRepository extends
> EntityRepository > > > Long>
> > > > > > {
> > > > > >
> > > > > > @Override
> > > > > > @Query(hints = {@QueryHint(name =
> > > > > "javax.persistence.cache.storeMode",
> > > > > > value = BYPASS)})
> > > > > > List findAll();
> > > > > > }
> > > > > > ```
> > > > > >
> > > > > > On Thu, Jun 11, 2015 at 11:53 AM, akm  wrote:
> > > > > >
> > > > > > > Thanks for the reply.
> > > > > > >
> > > > > > > We are creating a framework that all our enterprise
> applications
> > > will
> > > > > be
> > > > > > > using; so I am looking for a generic solution that I can add
> in a
> > > > > > abstract
> > > > > > > class that then all entities can use.
> > > > > > > Basically looking for something like just adding a hint to the
> > > > current
> > > > > > > AbstractEntityRepository's findAll.
> > > > > > > In the solution you mention all the applications would have to
> > &

Re: DeltaSpike Data Module Repository

[Daniel Cunha]

Thomas,

Sure!

MethodQueryBuilder already do it. [1]
I see for Delegate[2], but.. really, I don't know how to apply it here. :(

[1]
https://github.com/danielsoro/deltaspike/blob/applyRestrictions/deltaspike/modules/data/impl/src/main/java/org/apache/deltaspike/data/impl/builder/MethodQueryBuilder.java#L48

[2]
https://github.com/danielsoro/deltaspike/blob/applyRestrictions/deltaspike/modules/data/impl/src/main/java/org/apache/deltaspike/data/impl/builder/DelegateQueryBuilder.java

On Fri, Jun 12, 2015 at 4:39 AM, Thomas Hug  wrote:

> Thanks Daniel for checking! Different reason it doesn't work than I had in
> memory :-)
> I think we should go for a general solution and not just for
> EntityRepository methods, @Query metadata should be considered for any
> method expression. The place to change this is probably somewhere in
> Delegate- and MethodQueryBuilder.
>
> On Fri, Jun 12, 2015 at 4:19 AM, Daniel Cunha 
> wrote:
>
> > Thomas,
> >
> > you're right, not work.
> > I changed and works now[1], but I don't know if this is the better way to
> > fix it.
> >
> >
> >
> https://github.com/danielsoro/deltaspike/commit/bb02f14731e9c7fd5d20c255bae2a2033617a9b8
> >
> > On Thu, Jun 11, 2015 at 4:11 PM, Thomas Hug 
> wrote:
> >
> > > Using the @Query(hints...) is the place to set the hints with DS Data.
> > > Unfortunately (hope my memory isn't wrong) this currently doesn't work
> > with
> > > a method expression. As soon as there's a @Query it's not considered a
> > > method expression anymore.
> > >
> > > Should not be too difficult to change - and should be changed as the
> > sample
> > > from Daniel makes totally sense :-) Will check this tomorrow and
> create a
> > > JIRA issue.
> > >
> > >
> > >
> > > On Thu, Jun 11, 2015 at 5:42 PM, Daniel Cunha 
> > > wrote:
> > >
> > > > Hmm..
> > > >
> > > > so, that's should work:
> > > >
> > > > ```
> > > > @Repository
> > > > public interface SimpleRepository extends EntityRepository > Long>
> > > > {
> > > >
> > > > @Override
> > > > @Query(hints = {@QueryHint(name =
> > > "javax.persistence.cache.storeMode",
> > > > value = BYPASS)})
> > > > List findAll();
> > > > }
> > > > ```
> > > >
> > > > On Thu, Jun 11, 2015 at 11:53 AM, akm  wrote:
> > > >
> > > > > Thanks for the reply.
> > > > >
> > > > > We are creating a framework that all our enterprise applications
> will
> > > be
> > > > > using; so I am looking for a generic solution that I can add in a
> > > > abstract
> > > > > class that then all entities can use.
> > > > > Basically looking for something like just adding a hint to the
> > current
> > > > > AbstractEntityRepository's findAll.
> > > > > In the solution you mention all the applications would have to
> > > implement
> > > > > the
> > > > > findAll for all the entities.
> > > > >
> > > > > What I have currently is the below solution, but now the enterprise
> > > > > framework would have to implement this for all the find methods
> > > provided
> > > > by
> > > > > the DeltaSpike repository which leads to maintenance issues and
> thus
> > > > > negates
> > > > > a lot of positives that DeltaSpike would provide us.
> > > > >
> > > > > *Current solution -*
> > > > > public abstract class MyBaseEntityCrudRepository > > > > Serializable>
> > > > > extends AbstractEntityRepository implements
> > > > > Deactivatable {
> > > > >
> > > > > public List findAllFromDatabase() {
> > > > >
> > > > > CriteriaQuery query = this.criteriaQuery();
> > > > > Root root = query.from(entityClass());
> > > > > query = query.select(root);
> > > > > TypedQuery typedQuery =
> > > > > this.entityManager().createQuery(query);
> > > > > typedQuery.setHint("javax.persistence.cache.retrieveMode",
> > > > > CacheRetrieveMode.BYPASS);
> > > > >
> > > > > return typedQuery.getResultList();
> > > > >
> > > > > }
> > > > >
> > > > >
> > > > > *I am looking for something easier method to add like -*
> > > > > /**
> > > > >  * @see
> org.apache.deltaspike.data.api.EntityRepository#findAll()
> > > > >  */
> > > > > @Override
> > > > > @QueryHint("javax.persistence.cache.storeMode",
> > > > > CacheRetrieveMode.BYPASS)
> > > > > public List findAll() {
> > > > >  return super.findAll();
> > > > > }
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > View this message in context:
> > > > >
> > > >
> > >
> >
> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/DeltaSpike-Data-Module-Repository-tp4660831p4660840.html
> > > > > Sent from the Apache DeltaSpike Incubator Discussions mailing list
> > > > archive
> > > > > at Nabble.com.
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Best regard,
> > > > Daniel Cunha (soro)
> > > >
> > >
> >
> >
> >
> > --
> > Best regard,
> > Daniel Cunha (soro)
> >
>



-- 
Best regard,
Daniel Cunha (soro)

Re: DeltaSpike Data Module Repository

[Daniel Cunha]

Thomas,

you're right, not work.
I changed and works now[1], but I don't know if this is the better way to
fix it.

https://github.com/danielsoro/deltaspike/commit/bb02f14731e9c7fd5d20c255bae2a2033617a9b8

On Thu, Jun 11, 2015 at 4:11 PM, Thomas Hug  wrote:

> Using the @Query(hints...) is the place to set the hints with DS Data.
> Unfortunately (hope my memory isn't wrong) this currently doesn't work with
> a method expression. As soon as there's a @Query it's not considered a
> method expression anymore.
>
> Should not be too difficult to change - and should be changed as the sample
> from Daniel makes totally sense :-) Will check this tomorrow and create a
> JIRA issue.
>
>
>
> On Thu, Jun 11, 2015 at 5:42 PM, Daniel Cunha 
> wrote:
>
> > Hmm..
> >
> > so, that's should work:
> >
> > ```
> > @Repository
> > public interface SimpleRepository extends EntityRepository
> > {
> >
> > @Override
> > @Query(hints = {@QueryHint(name =
> "javax.persistence.cache.storeMode",
> > value = BYPASS)})
> > List findAll();
> > }
> > ```
> >
> > On Thu, Jun 11, 2015 at 11:53 AM, akm  wrote:
> >
> > > Thanks for the reply.
> > >
> > > We are creating a framework that all our enterprise applications will
> be
> > > using; so I am looking for a generic solution that I can add in a
> > abstract
> > > class that then all entities can use.
> > > Basically looking for something like just adding a hint to the current
> > > AbstractEntityRepository's findAll.
> > > In the solution you mention all the applications would have to
> implement
> > > the
> > > findAll for all the entities.
> > >
> > > What I have currently is the below solution, but now the enterprise
> > > framework would have to implement this for all the find methods
> provided
> > by
> > > the DeltaSpike repository which leads to maintenance issues and thus
> > > negates
> > > a lot of positives that DeltaSpike would provide us.
> > >
> > > *Current solution -*
> > > public abstract class MyBaseEntityCrudRepository > > Serializable>
> > > extends AbstractEntityRepository implements
> > > Deactivatable {
> > >
> > > public List findAllFromDatabase() {
> > >
> > > CriteriaQuery query = this.criteriaQuery();
> > > Root root = query.from(entityClass());
> > > query = query.select(root);
> > > TypedQuery typedQuery =
> > > this.entityManager().createQuery(query);
> > > typedQuery.setHint("javax.persistence.cache.retrieveMode",
> > > CacheRetrieveMode.BYPASS);
> > >
> > > return typedQuery.getResultList();
> > >
> > > }
> > >
> > >
> > > *I am looking for something easier method to add like -*
> > > /**
> > >  * @see org.apache.deltaspike.data.api.EntityRepository#findAll()
> > >  */
> > > @Override
> > > @QueryHint("javax.persistence.cache.storeMode",
> > > CacheRetrieveMode.BYPASS)
> > > public List findAll() {
> > >  return super.findAll();
> > > }
> > >
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > >
> >
> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/DeltaSpike-Data-Module-Repository-tp4660831p4660840.html
> > > Sent from the Apache DeltaSpike Incubator Discussions mailing list
> > archive
> > > at Nabble.com.
> > >
> >
> >
> >
> > --
> > Best regard,
> > Daniel Cunha (soro)
> >
>



-- 
Best regard,
Daniel Cunha (soro)

[jira] [Resolved] (DELTASPIKE-924) Adjust The AbstractEntityRepository Class secion.

[Daniel Cunha (soro) (JIRA)]

 [ 
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] [Created] (DELTASPIKE-924) Adjust The AbstractEntityRepository Class secion.

[Daniel Cunha (soro) (JIRA)]

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-923) Add #entityName() to AbstractEntityRepository

[Daniel Cunha (soro) (JIRA)]

 [ 
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)

Re: DeltaSpike Data Module Repository

[Daniel Cunha]

Hmm..

so, that's should work:

```
@Repository
public interface SimpleRepository extends EntityRepository
{

@Override
@Query(hints = {@QueryHint(name = "javax.persistence.cache.storeMode",
value = BYPASS)})
List findAll();
}
```

On Thu, Jun 11, 2015 at 11:53 AM, akm  wrote:

> Thanks for the reply.
>
> We are creating a framework that all our enterprise applications will be
> using; so I am looking for a generic solution that I can add in a abstract
> class that then all entities can use.
> Basically looking for something like just adding a hint to the current
> AbstractEntityRepository's findAll.
> In the solution you mention all the applications would have to implement
> the
> findAll for all the entities.
>
> What I have currently is the below solution, but now the enterprise
> framework would have to implement this for all the find methods provided by
> the DeltaSpike repository which leads to maintenance issues and thus
> negates
> a lot of positives that DeltaSpike would provide us.
>
> *Current solution -*
> public abstract class MyBaseEntityCrudRepository Serializable>
> extends AbstractEntityRepository implements
> Deactivatable {
>
> public List findAllFromDatabase() {
>
> CriteriaQuery query = this.criteriaQuery();
> Root root = query.from(entityClass());
> query = query.select(root);
> TypedQuery typedQuery =
> this.entityManager().createQuery(query);
> typedQuery.setHint("javax.persistence.cache.retrieveMode",
> CacheRetrieveMode.BYPASS);
>
> return typedQuery.getResultList();
>
> }
>
>
> *I am looking for something easier method to add like -*
> /**
>  * @see org.apache.deltaspike.data.api.EntityRepository#findAll()
>  */
> @Override
> @QueryHint("javax.persistence.cache.storeMode",
> CacheRetrieveMode.BYPASS)
> public List findAll() {
>  return super.findAll();
> }
>
>
>
>
> --
> View this message in context:
> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/DeltaSpike-Data-Module-Repository-tp4660831p4660840.html
> Sent from the Apache DeltaSpike Incubator Discussions mailing list archive
> at Nabble.com.
>



-- 
Best regard,
Daniel Cunha (soro)

Re: DeltaSpike Data Module Repository

[Daniel Cunha]

you also can do:
http://deltaspike.apache.org/documentation/data.html#QueryOptions21

On Thu, Jun 11, 2015 at 12:02 PM, Daniel Cunha  wrote:

> Ops,
>
> I wanted to say: NativeNamedQuery and the method should return a list, not
> a entity.
> I used a sample of the documentation and add the hint to show my example.
> (I'm fixing it in documentation now)
>
> On Thu, Jun 11, 2015 at 11:57 AM, Daniel Cunha 
> wrote:
>
>> Hi Akm,
>>
>> Maybe, you can do something like:
>>
>> ```
>> public abstract class PersonRepository extends
>> AbstractEntityRepository
>> {
>>
>> public Person findBySSN(String ssn)
>> {
>> return typedQuery("select p from Person p where p.ssn = ?1")
>> .setParameter(1, ssn)
>> .setHint("xpto","xpto-value")
>> .getResultList();
>> }
>>
>> }
>> ```
>>
>> Or, you can use NamedQuery/NativeQuery.
>>
>> We've this two solutions, ATM. (If I remember well, please DS guys, talk
>> more if I forget something)
>> If you have some another idea, please, share it and maybe we can discuss
>> and implement it or you can present a some solution with a patch/Pull
>> Request.
>>
>>
>> On Thu, Jun 11, 2015 at 10:37 AM, akm  wrote:
>>
>>> We are piloting DeltaSpike Data Module in our enterprise.
>>>
>>> Our requirements are to add a query hint to bypass cache for the find
>>> methods since most of our applications need to get the latest data from
>>> the
>>> database as the records may be directly inserted or updated in the
>>> database.
>>> I cannot find a way to add hints to the repository find method.
>>> Is there a way to do this?
>>>
>>> Thanks for the help.
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/DeltaSpike-Data-Module-Repository-tp4660831.html
>>> Sent from the Apache DeltaSpike Incubator Discussions mailing list
>>> archive at Nabble.com.
>>>
>>
>>
>>
>> --
>> Best regard,
>> Daniel Cunha (soro)
>>
>
>
>
> --
> Best regard,
> Daniel Cunha (soro)
>



-- 
Best regard,
Daniel Cunha (soro)

Re: DeltaSpike Data Module Repository

[Daniel Cunha]

Ops,

I wanted to say: NativeNamedQuery and the method should return a list, not
a entity.
I used a sample of the documentation and add the hint to show my example.
(I'm fixing it in documentation now)

On Thu, Jun 11, 2015 at 11:57 AM, Daniel Cunha  wrote:

> Hi Akm,
>
> Maybe, you can do something like:
>
> ```
> public abstract class PersonRepository extends
> AbstractEntityRepository
> {
>
> public Person findBySSN(String ssn)
> {
> return typedQuery("select p from Person p where p.ssn = ?1")
> .setParameter(1, ssn)
> .setHint("xpto","xpto-value")
> .getResultList();
> }
>
> }
> ```
>
> Or, you can use NamedQuery/NativeQuery.
>
> We've this two solutions, ATM. (If I remember well, please DS guys, talk
> more if I forget something)
> If you have some another idea, please, share it and maybe we can discuss
> and implement it or you can present a some solution with a patch/Pull
> Request.
>
>
> On Thu, Jun 11, 2015 at 10:37 AM, akm  wrote:
>
>> We are piloting DeltaSpike Data Module in our enterprise.
>>
>> Our requirements are to add a query hint to bypass cache for the find
>> methods since most of our applications need to get the latest data from
>> the
>> database as the records may be directly inserted or updated in the
>> database.
>> I cannot find a way to add hints to the repository find method.
>> Is there a way to do this?
>>
>> Thanks for the help.
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/DeltaSpike-Data-Module-Repository-tp4660831.html
>> Sent from the Apache DeltaSpike Incubator Discussions mailing list
>> archive at Nabble.com.
>>
>
>
>
> --
> Best regard,
> Daniel Cunha (soro)
>



-- 
Best regard,
Daniel Cunha (soro)

Re: DeltaSpike Data Module Repository

[Daniel Cunha]

Hi Akm,

Maybe, you can do something like:

```
public abstract class PersonRepository extends
AbstractEntityRepository
{

public Person findBySSN(String ssn)
{
return typedQuery("select p from Person p where p.ssn = ?1")
.setParameter(1, ssn)
.setHint("xpto","xpto-value")
.getResultList();
}

}
```

Or, you can use NamedQuery/NativeQuery.

We've this two solutions, ATM. (If I remember well, please DS guys, talk
more if I forget something)
If you have some another idea, please, share it and maybe we can discuss
and implement it or you can present a some solution with a patch/Pull
Request.


On Thu, Jun 11, 2015 at 10:37 AM, akm  wrote:

> We are piloting DeltaSpike Data Module in our enterprise.
>
> Our requirements are to add a query hint to bypass cache for the find
> methods since most of our applications need to get the latest data from the
> database as the records may be directly inserted or updated in the
> database.
> I cannot find a way to add hints to the repository find method.
> Is there a way to do this?
>
> Thanks for the help.
>
>
>
>
> --
> View this message in context:
> http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/DeltaSpike-Data-Module-Repository-tp4660831.html
> Sent from the Apache DeltaSpike Incubator Discussions mailing list archive
> at Nabble.com.
>



-- 
Best regard,
Daniel Cunha (soro)

[jira] [Updated] (DELTASPIKE-700) Add #tableName() to AbstractEntityRepository

[Daniel Cunha (soro) (JIRA)]

 [ 
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] [Updated] (DELTASPIKE-923) Add #entityName() to AbstractEntityRepository

[Daniel Cunha (soro) (JIRA)]

 [ 
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-923) Add #entityName() to AbstractEntityRepository

[Daniel Cunha (soro) (JIRA)]

 [ 
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)