[jira] [Commented] (DELTASPIKE-1377) issue with @Repository + @Query annotation and clustered wildfly

2019-06-20 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1377:
---

Yep i think so
feel free to work on a patch :)

> issue with @Repository + @Query annotation and clustered wildfly 
> -
>
> Key: DELTASPIKE-1377
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1377
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Data-Module
>Affects Versions: 1.9.0
>Reporter: Andrew Schmidt
>Priority: Major
> Attachments: cdri-test.zip, stack.txt
>
>
> Setup:   2 x wildfly 15.0.1.Final (weld-core updated to 3.0.6)
> Clustered standalone-full-ha setup,  same machine with a port offset for the 
> second machine.
>  
> Repo:
> {code:java}
> @Repository
> @ApplicationScoped
> public interface AnimalRepo extends EntityRepository
> {
>@Query( value = "select a from Animal a where ?1 = a.name" )
>Animal findByName(String name);
> }
> {code}
> Session bean:
> {code:java}
> @SessionScoped
> @Named
> public class MyBean implements Serializable
> {
>   private static final long serialVersionUID = 1L;
>   @Inject
>   private AnimalRepo animalRepo;
>   public Long getTest()
>   {
> return animalRepo.count();
>   }
> }
> {code}
> index.xhtml
> {code:java}
> 
> #{myBean.test}
> 
> {code}
> Visiting the first server yields no error, but upon visiting the second 
> server:
> {code:java}
> WELD-001500: Failed to deserialize proxy object with beanId 
> org.apache.deltaspike.core.util.bean.ImmutableBeanWrapper:AnimalRepo[@javax.enterprise.context.ApplicationScoped()@org.apache.deltaspike.data.api.Repository(forEntity=class
>  
> java.lang.Object,methodPrefix=)]{AnimalRepo.findByName[@org.apache.deltaspike.data.api.Query(hints=[Ljavax.persistence.QueryHint;@774c6737,isNative=false,lock=NONE,max=0,named=,singleResult=JPA,value=select
>  a from Animal where ?1 = a.name)](java.lang.String);}
> {code}
> Interestingly,  If the @Query annotation is removed from the findByName 
> query, there is no issue.
> See attached project.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1377) issue with @Repository + @Query annotation and clustered wildfly

2019-06-12 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1377:
---

[~struberg] [~romain.manni-bucau] WDYT?

> issue with @Repository + @Query annotation and clustered wildfly 
> -
>
> Key: DELTASPIKE-1377
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1377
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Data-Module
>Affects Versions: 1.9.0
>Reporter: Andrew Schmidt
>Priority: Major
> Attachments: cdri-test.zip, stack.txt
>
>
> Setup:   2 x wildfly 15.0.1.Final (weld-core updated to 3.0.6)
> Clustered standalone-full-ha setup,  same machine with a port offset for the 
> second machine.
>  
> Repo:
> {code:java}
> @Repository
> @ApplicationScoped
> public interface AnimalRepo extends EntityRepository
> {
>@Query( value = "select a from Animal where ?1 = a.name" )
>Animal findByName(String name);
> }
> {code}
> Session bean:
> {code:java}
> @SessionScoped
> @Named
> public class MyBean implements Serializable
> {
>   private static final long serialVersionUID = 1L;
>   @Inject
>   private AnimalRepo animalRepo;
>   public Long getTest()
>   {
> return animalRepo.count();
>   }
> }
> {code}
> index.xhtml
> {code:java}
> 
> #{myBean.test}
> 
> {code}
> Visiting the first server yields no error, but upon visiting the second 
> server:
> {code:java}
> WELD-001500: Failed to deserialize proxy object with beanId 
> org.apache.deltaspike.core.util.bean.ImmutableBeanWrapper:AnimalRepo[@javax.enterprise.context.ApplicationScoped()@org.apache.deltaspike.data.api.Repository(forEntity=class
>  
> java.lang.Object,methodPrefix=)]{AnimalRepo.findByName[@org.apache.deltaspike.data.api.Query(hints=[Ljavax.persistence.QueryHint;@774c6737,isNative=false,lock=NONE,max=0,named=,singleResult=JPA,value=select
>  a from Animal where ?1 = a.name)](java.lang.String);}
> {code}
> Interestingly,  If the @Query annotation is removed from the findByName 
> query, there is no issue.
> See attached project.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1377) issue with @Repository + @Query annotation and clustered wildfly

2019-06-11 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1377:
---

[~andrew.schmidt] Could you do a bit debug-work to find the reason?
I would assume that we instantiate a ImmutablePassivationCapableBeanWrapper 
instead of ImmutableBeanWrapper; see WrappingBeanBuilder#create

> issue with @Repository + @Query annotation and clustered wildfly 
> -
>
> Key: DELTASPIKE-1377
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1377
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Data-Module
>Affects Versions: 1.9.0
>Reporter: Andrew Schmidt
>Priority: Major
> Attachments: cdri-test.zip, stack.txt
>
>
> Setup:   2 x wildfly 15.0.1.Final (weld-core updated to 3.0.6)
> Clustered standalone-full-ha setup,  same machine with a port offset for the 
> second machine.
>  
> Repo:
> {code:java}
> @Repository
> @ApplicationScoped
> public interface AnimalRepo extends EntityRepository
> {
>@Query( value = "select a from Animal where ?1 = a.name" )
>Animal findByName(String name);
> }
> {code}
> Session bean:
> {code:java}
> @SessionScoped
> @Named
> public class MyBean implements Serializable
> {
>   private static final long serialVersionUID = 1L;
>   @Inject
>   private AnimalRepo animalRepo;
>   public Long getTest()
>   {
> return animalRepo.count();
>   }
> }
> {code}
> index.xhtml
> {code:java}
> 
> #{myBean.test}
> 
> {code}
> Visiting the first server yields no error, but upon visiting the second 
> server:
> {code:java}
> WELD-001500: Failed to deserialize proxy object with beanId 
> org.apache.deltaspike.core.util.bean.ImmutableBeanWrapper:AnimalRepo[@javax.enterprise.context.ApplicationScoped()@org.apache.deltaspike.data.api.Repository(forEntity=class
>  
> java.lang.Object,methodPrefix=)]{AnimalRepo.findByName[@org.apache.deltaspike.data.api.Query(hints=[Ljavax.persistence.QueryHint;@774c6737,isNative=false,lock=NONE,max=0,named=,singleResult=JPA,value=select
>  a from Animal where ?1 = a.name)](java.lang.String);}
> {code}
> Interestingly,  If the @Query annotation is removed from the findByName 
> query, there is no issue.
> See attached project.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1381) Method Expressions not validated at deployment time

2019-06-11 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1381:
---

Can you provide the full stacktrace with caused by?

> Method Expressions not validated at deployment time
> ---
>
> Key: DELTASPIKE-1381
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1381
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Data-Module
>Affects Versions: 1.9.0
> Environment: JDK 8
> Postgres 10
> Hibernate 5.3.6
> WildFly 13.0.0
>Reporter: Ehsan Zaery Moghaddam
>Priority: Minor
>
> In the documentation it's explicitly mentioned that method expressions are 
> validated upon deployment to see if there is any typo in them: 
> *_Note that DeltaSpike will validate those expressions during startup, so you 
> will notice early in case you have a typo in those expressions_*.
>  
> But seems this validation doesn't happen during deployment and the code fails 
> when the given method is being called. In the following example, the 
> "LessThan" comparator is misspelled and the stack trace of the runtime error 
> is as below:
>  
> *Caused by: org.apache.deltaspike.data.api.QueryInvocationException: Failed 
> calling Repository: 
> [Repository=com.one.paymentgateway.persistence.repository.PendingCaptureRepository,entity=com.one.paymentgateway.persistence.entity.PendingCaptureEntity,method=findAnyByPendingTimeLesThanEqualsOrderByPendingTime,*
>  at 
> org.apache.deltaspike.data.impl.builder.DelegateQueryBuilder.execute(DelegateQueryBuilder.java:83)
>  at 
> org.apache.deltaspike.data.impl.builder.QueryBuilder.executeQuery(QueryBuilder.java:57)
>  at 
> org.apache.deltaspike.data.impl.builder.DelegateQueryBuilder$Proxy$_$$_WeldClientProxy.executeQuery(Unknown
>  Source)
>  at 
> org.apache.deltaspike.data.impl.tx.TransactionalQueryRunner.executeNonTransactional(TransactionalQueryRunner.java:62)
>  at 
> org.apache.deltaspike.data.impl.tx.TransactionalQueryRunner.executeQuery(TransactionalQueryRunner.java:57)
>  at 
> org.apache.deltaspike.data.impl.tx.TransactionalQueryRunner$Proxy$_$$_WeldClientProxy.executeQuery(Unknown
>  Source)
>  at 
> org.apache.deltaspike.data.impl.handler.QueryHandler.process(QueryHandler.java:151)
>  ... 161 more



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (DELTASPIKE-1382) ClientWindowRenderMode.CLIENTWINDOW breaks Back button in certain Browser/BrowserPlugin combinations

2019-06-11 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko resolved DELTASPIKE-1382.
---
Resolution: Fixed

> ClientWindowRenderMode.CLIENTWINDOW breaks Back button in certain 
> Browser/BrowserPlugin combinations
> 
>
> Key: DELTASPIKE-1382
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1382
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: JSF-Module
>Affects Versions: 1.9.0
> Environment: Tomcat 9.0.20
> MyFaces 2.3.2
> OpenWebBeans 2.0.8
> DeltaSpike JSF module 1.9.0
> Chrome/Chromium + uBlock Origin (just as one example)
>Reporter: Juri Berlanda
>Priority: Major
> Fix For: 1.9.1
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> It seems, that certain Browser / BrowserPlugin combinations start behaving 
> weird, if ClientWindowRenderMode.CLIENTWINDOW is used. Known affected 
> combinations are:
> * Firefox + Evernote Web Clipper
> * Chrome/Chromium + Evernote Web Clipper
> * Chrome/Chromium + uBlock Origin
> Note: Firefox + uBlock Origin for some reason is NOT affected.
> h1. Preconditions:
> * A JSF application with DeltaSpike JSF Modulke
> * ClientWindowRenderMode.CLIENTWINDOW
> * At least two pages (in the following they are referred to as "index.xhtml" 
> and "second.xhtml")
> h1. Steps to reproduce:
> # Load index.xhtml
> # In the same Browser window navigate to second.xhtml - make sure the URL 
> used for navigation does NOT contain dswid and dsrid
> # Hit the Back button
> h1. Expected:
> * Browser navigates back to index.xhtml
> h1. Actual (assuming the Browser/BrowserPlugin combination mentioned above):
> * Browser stays on second.xhtml same page (Actually, Browser navigates back 
> to second.xhtml without dswid and dsrid and then again to second.xhtml with 
> those paramter, but the user hardly notices that)
> h1. Reason / Potential Fix:
> This issue is caused by windowhandler.html using {{window.location = 
> redirectUrl;}} and can be fixed by replacing that with 
> {{window.location.replace(redirectUrl);}}. Referencing 
> https://www.w3schools.com/jsref/met_loc_replace.asp I would say the solution 
> is widely supported.
> h1. Further notes:
> * I will shortly create a PullRequest on GitHub referencing this issue
> * If there is need for it, I'd be happy to provide a minimal project 
> demonstrating the issue



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1382) ClientWindowRenderMode.CLIENTWINDOW breaks Back button in certain Browser/BrowserPlugin combinations

2019-06-11 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1382:
---

Thanks for the PR! i applied it

> ClientWindowRenderMode.CLIENTWINDOW breaks Back button in certain 
> Browser/BrowserPlugin combinations
> 
>
> Key: DELTASPIKE-1382
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1382
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: JSF-Module
>Affects Versions: 1.9.0
> Environment: Tomcat 9.0.20
> MyFaces 2.3.2
> OpenWebBeans 2.0.8
> DeltaSpike JSF module 1.9.0
> Chrome/Chromium + uBlock Origin (just as one example)
>Reporter: Juri Berlanda
>Priority: Major
> Fix For: 1.9.1
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> It seems, that certain Browser / BrowserPlugin combinations start behaving 
> weird, if ClientWindowRenderMode.CLIENTWINDOW is used. Known affected 
> combinations are:
> * Firefox + Evernote Web Clipper
> * Chrome/Chromium + Evernote Web Clipper
> * Chrome/Chromium + uBlock Origin
> Note: Firefox + uBlock Origin for some reason is NOT affected.
> h1. Preconditions:
> * A JSF application with DeltaSpike JSF Modulke
> * ClientWindowRenderMode.CLIENTWINDOW
> * At least two pages (in the following they are referred to as "index.xhtml" 
> and "second.xhtml")
> h1. Steps to reproduce:
> # Load index.xhtml
> # In the same Browser window navigate to second.xhtml - make sure the URL 
> used for navigation does NOT contain dswid and dsrid
> # Hit the Back button
> h1. Expected:
> * Browser navigates back to index.xhtml
> h1. Actual (assuming the Browser/BrowserPlugin combination mentioned above):
> * Browser stays on second.xhtml same page (Actually, Browser navigates back 
> to second.xhtml without dswid and dsrid and then again to second.xhtml with 
> those paramter, but the user hardly notices that)
> h1. Reason / Potential Fix:
> This issue is caused by windowhandler.html using {{window.location = 
> redirectUrl;}} and can be fixed by replacing that with 
> {{window.location.replace(redirectUrl);}}. Referencing 
> https://www.w3schools.com/jsref/met_loc_replace.asp I would say the solution 
> is widely supported.
> h1. Further notes:
> * I will shortly create a PullRequest on GitHub referencing this issue
> * If there is need for it, I'd be happy to provide a minimal project 
> demonstrating the issue



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1382) ClientWindowRenderMode.CLIENTWINDOW breaks Back button in certain Browser/BrowserPlugin combinations

2019-06-11 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko updated DELTASPIKE-1382:
--
Fix Version/s: 1.9.1

> ClientWindowRenderMode.CLIENTWINDOW breaks Back button in certain 
> Browser/BrowserPlugin combinations
> 
>
> Key: DELTASPIKE-1382
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1382
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: JSF-Module
>Affects Versions: 1.9.0
> Environment: Tomcat 9.0.20
> MyFaces 2.3.2
> OpenWebBeans 2.0.8
> DeltaSpike JSF module 1.9.0
> Chrome/Chromium + uBlock Origin (just as one example)
>Reporter: Juri Berlanda
>Priority: Major
> Fix For: 1.9.1
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> It seems, that certain Browser / BrowserPlugin combinations start behaving 
> weird, if ClientWindowRenderMode.CLIENTWINDOW is used. Known affected 
> combinations are:
> * Firefox + Evernote Web Clipper
> * Chrome/Chromium + Evernote Web Clipper
> * Chrome/Chromium + uBlock Origin
> Note: Firefox + uBlock Origin for some reason is NOT affected.
> h1. Preconditions:
> * A JSF application with DeltaSpike JSF Modulke
> * ClientWindowRenderMode.CLIENTWINDOW
> * At least two pages (in the following they are referred to as "index.xhtml" 
> and "second.xhtml")
> h1. Steps to reproduce:
> # Load index.xhtml
> # In the same Browser window navigate to second.xhtml - make sure the URL 
> used for navigation does NOT contain dswid and dsrid
> # Hit the Back button
> h1. Expected:
> * Browser navigates back to index.xhtml
> h1. Actual (assuming the Browser/BrowserPlugin combination mentioned above):
> * Browser stays on second.xhtml same page (Actually, Browser navigates back 
> to second.xhtml without dswid and dsrid and then again to second.xhtml with 
> those paramter, but the user hardly notices that)
> h1. Reason / Potential Fix:
> This issue is caused by windowhandler.html using {{window.location = 
> redirectUrl;}} and can be fixed by replacing that with 
> {{window.location.replace(redirectUrl);}}. Referencing 
> https://www.w3schools.com/jsref/met_loc_replace.asp I would say the solution 
> is widely supported.
> h1. Further notes:
> * I will shortly create a PullRequest on GitHub referencing this issue
> * If there is need for it, I'd be happy to provide a minimal project 
> demonstrating the issue



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (DELTASPIKE-1380) Concurrently initialization causes "Argument bean must not be null"

2019-05-22 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko resolved DELTASPIKE-1380.
---
Resolution: Fixed

> Concurrently initialization causes "Argument bean must not be null"
> ---
>
> Key: DELTASPIKE-1380
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1380
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Proxy-Module
>Affects Versions: 1.9.0
>Reporter: Jixing Wang
>Assignee: Thomas Andraschko
>Priority: Major
> Fix For: 1.9.1
>
>
> lazyInit() is called concurrently, the first thread should be the only one to 
> initialize it; however, deltaSpikeProxyInvocationHandler has been assigned 
> before all initialization jobs are completed, which sometimes causes issue.
> Caused by: org.jboss.weld.exceptions.IllegalArgumentException: WELD-001456: 
> Argument bean must not be null
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.util.Preconditions.checkArgumentNotNull(Preconditions.java:40)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:708)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.util.ForwardingBeanManager.getReference(ForwardingBeanManager.java:64)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.bean.builtin.BeanManagerProxy.getReference(BeanManagerProxy.java:87)
>  at 
> deployment.nyx.war//org.apache.deltaspike.proxy.api.DeltaSpikeProxyContextualLifecycle.instantiateDelegateInvocationHandler(DeltaSpikeProxyContextualLifecycle.java:177)
>  at 
> deployment.nyx.war//org.apache.deltaspike.proxy.api.DeltaSpikeProxyContextualLifecycle.create(DeltaSpikeProxyContextualLifecycle.java:94)
>  at 
> deployment.nyx.war//org.apache.deltaspike.core.util.bean.ImmutableBean.create(ImmutableBean.java:72)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.contexts.unbound.DependentContextImpl.get(DependentContextImpl.java:70)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:694)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.manager.BeanManagerImpl.getInjectableReference(BeanManagerImpl.java:794)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:92)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.util.Beans.injectBoundFields(Beans.java:336)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:347)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:71)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:73)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.module.ejb.DynamicInjectionPointInjector.inject(DynamicInjectionPointInjector.java:61)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.module.ejb.SessionBeanInjectionTarget.inject(SessionBeanInjectionTarget.java:138)
>  at 
> org.jboss.as.weld@16.0.0.Final//org.jboss.as.weld.injection.WeldInjectionContext.inject(WeldInjectionContext.java:39)
>  at 
> org.jboss.as.weld@16.0.0.Final//org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:51)
>  at 
> org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
>  at 
> org.jboss.as.ee@16.0.0.Final//org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28)
>  at 
> org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
>  at 
> org.jboss.as.weld@16.0.0.Final//org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56)
>  at 
> org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
>  at 
> org.jboss.as.ee@16.0.0.Final//org.jboss.as.ee.component.ComponentInsta

[jira] [Updated] (DELTASPIKE-1380) Concurrently initialization causes "Argument bean must not be null"

2019-05-22 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko updated DELTASPIKE-1380:
--
Fix Version/s: 1.9.1

> Concurrently initialization causes "Argument bean must not be null"
> ---
>
> Key: DELTASPIKE-1380
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1380
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Proxy-Module
>Affects Versions: 1.9.0
>Reporter: Jixing Wang
>Assignee: Thomas Andraschko
>Priority: Major
> Fix For: 1.9.1
>
>
> lazyInit() is called concurrently, the first thread should be the only one to 
> initialize it; however, deltaSpikeProxyInvocationHandler has been assigned 
> before all initialization jobs are completed, which sometimes causes issue.
> Caused by: org.jboss.weld.exceptions.IllegalArgumentException: WELD-001456: 
> Argument bean must not be null
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.util.Preconditions.checkArgumentNotNull(Preconditions.java:40)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:708)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.util.ForwardingBeanManager.getReference(ForwardingBeanManager.java:64)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.bean.builtin.BeanManagerProxy.getReference(BeanManagerProxy.java:87)
>  at 
> deployment.nyx.war//org.apache.deltaspike.proxy.api.DeltaSpikeProxyContextualLifecycle.instantiateDelegateInvocationHandler(DeltaSpikeProxyContextualLifecycle.java:177)
>  at 
> deployment.nyx.war//org.apache.deltaspike.proxy.api.DeltaSpikeProxyContextualLifecycle.create(DeltaSpikeProxyContextualLifecycle.java:94)
>  at 
> deployment.nyx.war//org.apache.deltaspike.core.util.bean.ImmutableBean.create(ImmutableBean.java:72)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.contexts.unbound.DependentContextImpl.get(DependentContextImpl.java:70)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:694)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.manager.BeanManagerImpl.getInjectableReference(BeanManagerImpl.java:794)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:92)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.util.Beans.injectBoundFields(Beans.java:336)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:347)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:71)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:73)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.module.ejb.DynamicInjectionPointInjector.inject(DynamicInjectionPointInjector.java:61)
>  at 
> org.jboss.weld.core@3.1.0.Final//org.jboss.weld.module.ejb.SessionBeanInjectionTarget.inject(SessionBeanInjectionTarget.java:138)
>  at 
> org.jboss.as.weld@16.0.0.Final//org.jboss.as.weld.injection.WeldInjectionContext.inject(WeldInjectionContext.java:39)
>  at 
> org.jboss.as.weld@16.0.0.Final//org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:51)
>  at 
> org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
>  at 
> org.jboss.as.ee@16.0.0.Final//org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28)
>  at 
> org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
>  at 
> org.jboss.as.weld@16.0.0.Final//org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56)
>  at 
> org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
>  at 
> org.jboss.as.ee@16.0.0.Final//org.jboss.as.ee.component.ComponentInsta

[jira] [Resolved] (DELTASPIKE-1379) DisableClientWindowHtmlRenderer init incomplete

2019-05-22 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko resolved DELTASPIKE-1379.
---
Resolution: Fixed

> DisableClientWindowHtmlRenderer init incomplete
> ---
>
> Key: DELTASPIKE-1379
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1379
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: JSF-Module
>Affects Versions: 1.9.0
>    Reporter: Thomas Andraschko
>    Assignee: Thomas Andraschko
>Priority: Major
> Fix For: 1.9.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (DELTASPIKE-1379) DisableClientWindowHtmlRenderer init incomplete

2019-05-22 Thread Thomas Andraschko (JIRA)
Thomas Andraschko created DELTASPIKE-1379:
-

 Summary: DisableClientWindowHtmlRenderer init incomplete
 Key: DELTASPIKE-1379
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1379
 Project: DeltaSpike
  Issue Type: Improvement
  Components: JSF-Module
Affects Versions: 1.9.0
Reporter: Thomas Andraschko
Assignee: Thomas Andraschko
 Fix For: 1.9.1






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Order by nested property in criteria

2019-04-24 Thread Thomas Andraschko
Hi,

do you mean our Criteria(Support) API or the JPA criteria?

Am Mi., 24. Apr. 2019 um 11:52 Uhr schrieb Arthur Gregório <
arthursha...@gmail.com>:

> Hello,
>
> I was trying to find a answer for a really simple question about put an
> order in queries when the property is nested (an entity linked to the root
> entity) but i can't find a answer...
>
> Did you guys here already tryed do make something like this? Is this
> possible using Criteria?
>
> *Arthur P. Gregório*
> *+55 45 99958-0302*
> @gregorioarthur
> http://webbudget.com.br/ 
> http://arthurgregorio.eti.br/blog/ 
>


[jira] [Closed] (DELTASPIKE-645) review sonar findings

2019-04-18 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko closed DELTASPIKE-645.

Resolution: Not A Problem

> review sonar findings
> -
>
> Key: DELTASPIKE-645
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-645
> Project: DeltaSpike
>  Issue Type: Task
>Affects Versions: 1.0.0
>Reporter: Gerhard Petracek
>Assignee: Rafael Benevides
>Priority: Major
>
> a lot of the sonar findings are wrong, because sonar isn't aware of cdi and 
> there are still some old rules in there. however, we should review the 
> findings on a regular basis. see http://deltaspike.apache.org/build.html#sonar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-645) review sonar findings

2019-04-18 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-645:
--

lets close it for now

> review sonar findings
> -
>
> Key: DELTASPIKE-645
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-645
> Project: DeltaSpike
>  Issue Type: Task
>Affects Versions: 1.0.0
>Reporter: Gerhard Petracek
>Assignee: Rafael Benevides
>Priority: Major
>
> a lot of the sonar findings are wrong, because sonar isn't aware of cdi and 
> there are still some old rules in there. however, we should review the 
> findings on a regular basis. see http://deltaspike.apache.org/build.html#sonar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1376) Warning on CDI 2.0

2019-04-10 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko updated DELTASPIKE-1376:
--
Fix Version/s: 2.0

> Warning on CDI 2.0
> --
>
> Key: DELTASPIKE-1376
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1376
> Project: DeltaSpike
>  Issue Type: Wish
>  Components: Data-Module
>Affects Versions: 1.9.0
>Reporter: Jordi Cabré
>Priority: Trivial
> Fix For: 2.0
>
>
> I'm getting these messages when I'm starting my service:
> Repository code is on g...@bitbucket.org:jeusdi/espaidoc.git
> It's configured using gradle and using [kumuluzee|[https://ee.kumuluz.com/]].
>  
> {{2019-04-10 09:19:25.628 INFO -- 
> org.jboss.weld.event.ExtensionObserverMethodImpl -- WELD-000411: Observer 
> method [BackedAnnotatedMethod] protected 
> org.apache.deltaspike.core.impl.exclude.extension.ExcludeExtension.vetoBeans(@Observes
>  ProcessAnnotatedType, BeanManager) receives events for all annotated types. 
> Consider restricting events using @WithAnnotations or a generic type with 
> bounds.}}
> {{2019-04-10 09:19:25.684 INFO -- 
> org.jboss.weld.event.ExtensionObserverMethodImpl -- WELD-000411: Observer 
> method [BackedAnnotatedMethod] 
> org.apache.deltaspike.data.impl.RepositoryExtension.processAnnotatedType(@Observes
>  ProcessAnnotatedType) receives events for all annotated types. Consider 
> restricting events using @WithAnnotations or a generic type with bounds.}}
> {{2019-04-10 09:19:25.693 INFO -- 
> org.jboss.weld.event.ExtensionObserverMethodImpl -- WELD-000411: Observer 
> method [BackedAnnotatedMethod] public 
> org.apache.deltaspike.core.impl.interceptor.interdyn.InterDynExtension.processAnnotatedType(@Observes
>  ProcessAnnotatedType) receives events for all annotated types. Consider 
> restricting events using @WithAnnotations or a generic type with bounds.}}
> {{2019-04-10 09:19:25.717 INFO -- 
> org.jboss.weld.event.ExtensionObserverMethodImpl -- WELD-000411: Observer 
> method [BackedAnnotatedMethod] public 
> org.apache.deltaspike.partialbean.impl.PartialBeanBindingExtension.findInvocationHandlerBindings(@Observes
>  ProcessAnnotatedType, BeanManager) receives events for all annotated 
> types. Consider restricting events using @WithAnnotations or a generic type 
> with bounds.}}
> {{2019-04-10 09:19:25.810 INFO -- 
> org.jboss.weld.event.ExtensionObserverMethodImpl -- WELD-000411: Observer 
> method [BackedAnnotatedMethod] public 
> org.apache.deltaspike.core.impl.config.ConfigurationExtension.findDynamicConfigurationBeans(@Observes
>  ProcessAnnotatedType) receives events for all annotated types. Consider 
> restricting events using @WithAnnotations or a generic type with bounds.}}
> {{2019-04-10 09:19:25.932 INFO -- 
> org.jboss.weld.event.ExtensionObserverMethodImpl -- WELD-000411: Observer 
> method [BackedAnnotatedMethod] private 
> org.glassfish.jersey.ext.cdi1x.internal.CdiComponentProvider.processAnnotatedType(@Observes
>  ProcessAnnotatedType) receives events for all annotated types. Consider 
> restricting events using @WithAnnotations or a generic type with bounds.}}
> {{2019-04-10 09:19:25.936 INFO -- 
> org.jboss.weld.event.ExtensionObserverMethodImpl -- WELD-000411: Observer 
> method [BackedAnnotatedMethod] protected 
> org.apache.deltaspike.core.impl.interceptor.GlobalInterceptorExtension.promoteInterceptors(@Observes
>  ProcessAnnotatedType) receives events for all annotated types. Consider 
> restricting events using @WithAnnotations or a generic type with bounds.}}
> {{2019-04-10 09:19:26.153 WARN -- 
> org.jboss.weld.bootstrap.events.BeforeBeanDiscoveryImpl -- WELD-000146: 
> BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class 
> org.glassfish.jersey.ext.cdi1x.internal.CdiComponentProvider$JaxRsParamProducer
>  is deprecated from CDI 1.1!}}
> {{2019-04-10 09:19:27.507 WARN -- org.jboss.weld.logging.ValidatorLogger -- 
> WELD-001478: Interceptor class 
> org.apache.deltaspike.jpa.impl.transaction.TransactionalInterceptor is 
> enabled for the application and for the bean archive 
> _/home/jeusdi/projects/espaidoc/frontoffice/build/libs/tmp/EeClassLoader/lib_deltaspike-jpa-module-impl-1.9.0.jar.
>  It will only be invoked in the @Priority part of the chain.}}
> {{2019-04-10 09:19:27.511 WARN -- org.jboss.weld.logging.ValidatorLogger -- 
> WELD-001478: Interceptor class 
> org.apache.deltaspike.core.impl.throttling.ThrottledInterceptor is enabled 
> for the application and for the bean archive 
> _/home/jeusdi/projects/espaidoc/frontoffice/build/l

[jira] [Updated] (DELTASPIKE-1328) Add a Java 8 base repository

2019-03-25 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko updated DELTASPIKE-1328:
--
Fix Version/s: (was: 1.9.1)

> Add a Java 8 base repository
> 
>
> Key: DELTASPIKE-1328
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1328
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Data-Module
>Reporter: John D. Ament
>Assignee: John D. Ament
>Priority: Major
>
> Add a base repository, like {{EntityRepository}} but for Java 8 
> {{Optional/Stream}} use cases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (DELTASPIKE-1367) JNDI Config Source should support alternate JNDI base names

2019-03-25 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko reassigned DELTASPIKE-1367:
-

Assignee: Mark Struberg  (was: Thomas Andraschko)

> JNDI Config Source should support alternate JNDI base names
> ---
>
> Key: DELTASPIKE-1367
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1367
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Configuration
>Affects Versions: 1.9.0
>Reporter: John Schneider
>Assignee: Mark Struberg
>Priority: Major
>
> JNDI Config is hard-coded to only support "java:comp/env/deltaspike/" as a 
> base name.  This doesn't work for EAR deployments where we must have the 
> DeltaSpike jars deployed in top-level app lib directory with JNDI resource 
> reference in application.xml, for which name prefix is java:app/env
> Furthermore, it's sometimes desirable to have server-level config, such as 
> for ProjectStage.  For example, a JNDI name 
> java:global/env/deltaspike/org.apache.deltaspike/ProjectStage might be 
> defined at the server level configuration.
> I understand a custom config source can be created to overcome this.  
> However, the standard JNDI config source should be more flexible.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1370) Deltaspike documentation states the latest release is 1.8.2

2019-03-25 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1370:
---

I changed it via the apache CMS now

> Deltaspike documentation states the latest release is 1.8.2
> ---
>
> Key: DELTASPIKE-1370
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1370
> Project: DeltaSpike
>  Issue Type: Task
>  Components: Documentation
>Reporter: Alexander Falb
>Priority: Trivial
>
> Our [Download|https://deltaspike.apache.org/download.html] page says the 
> latest version of DeltaSpike is 1.8.2, but it should be 1.9.0.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (DELTASPIKE-1367) JNDI Config Source should support alternate JNDI base names

2019-03-25 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko reassigned DELTASPIKE-1367:
-

Assignee: Thomas Andraschko

> JNDI Config Source should support alternate JNDI base names
> ---
>
> Key: DELTASPIKE-1367
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1367
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Configuration
>Affects Versions: 1.9.0
>Reporter: John Schneider
>    Assignee: Thomas Andraschko
>Priority: Major
>
> JNDI Config is hard-coded to only support "java:comp/env/deltaspike/" as a 
> base name.  This doesn't work for EAR deployments where we must have the 
> DeltaSpike jars deployed in top-level app lib directory with JNDI resource 
> reference in application.xml, for which name prefix is java:app/env
> Furthermore, it's sometimes desirable to have server-level config, such as 
> for ProjectStage.  For example, a JNDI name 
> java:global/env/deltaspike/org.apache.deltaspike/ProjectStage might be 
> defined at the server level configuration.
> I understand a custom config source can be created to overcome this.  
> However, the standard JNDI config source should be more flexible.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1368) Repository doesn't work in Java SE

2019-03-25 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1368:
---

Can you provide a example project? Otherwise hard to help.

> Repository doesn't work in Java SE
> --
>
> Key: DELTASPIKE-1368
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1368
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>Affects Versions: 1.9.0
>Reporter: Ehsan Zaery Moghaddam
>Priority: Minor
>
> Hi Guys
> I'm trying to use the repository implementation in a Java SE environment. I 
> start the Weld container using deltaspike cdi control module. When I try to 
> persist an entity using the repository class, it doesn't report any error, 
> but nothing get persisted in the DB.
> Is there any limitation/configuration in using repositories in Java SE? It 
> works fine when I try to persist it directly via JPA.
> I've already described it in more details in this 
> [stackoverflow|https://stackoverflow.com/questions/53783775/deltaspike-repository-transaction-commits-but-nothing-persists-in-db-in-java-se]
>  issue but got no answer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (DELTASPIKE-1370) Deltaspike documentation states the latest release is 1.8.2

2019-03-25 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko closed DELTASPIKE-1370.
-
Resolution: Fixed

> Deltaspike documentation states the latest release is 1.8.2
> ---
>
> Key: DELTASPIKE-1370
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1370
> Project: DeltaSpike
>  Issue Type: Task
>  Components: Documentation
>Reporter: Alexander Falb
>Priority: Trivial
>
> Our [Download|https://deltaspike.apache.org/download.html] page says the 
> latest version of DeltaSpike is 1.8.2, but it should be 1.9.0.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1366) Add Junit5 testing support

2019-03-25 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1366:
---

[~javatesting] it would be really great if you could work on it.

> Add Junit5 testing support
> --
>
> Key: DELTASPIKE-1366
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1366
> Project: DeltaSpike
>  Issue Type: Wish
>  Components: TestControl, Tests
>Affects Versions: 1.9.0
>Reporter: John Smith
>Priority: Major
>
> Are there any plans to provide a junit5 extension like the CdiTestRunner in 
> the test-control module for junit4? 
> {{Especially the feature of the DynamicMockManager that allows you to add 
> mocks on per test basis is pretty nice for testing.}}
> {{This would be highly appreciated.  }}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (DELTASPIKE-1372) Test-Control module has a undeclared and undocumented de-facto runtime dependency on core-impl

2019-03-25 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko resolved DELTASPIKE-1372.
---
   Resolution: Fixed
Fix Version/s: 1.9.1

> Test-Control module has a undeclared and undocumented de-facto runtime 
> dependency on core-impl
> --
>
> Key: DELTASPIKE-1372
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1372
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: TestControl
>Affects Versions: 1.9.0
>Reporter: Juri Berlanda
>Priority: Major
> Fix For: 1.9.1
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> When setting up Test-Control Module like described in 
> [http://deltaspike.apache.org/documentation/test-control.html] I end up with:
> {{java.lang.ExceptionInInitializerError}}
> {{ at 
> org.apache.deltaspike.testcontrol.api.junit.CdiTestRunner.(CdiTestRunner.java:87)}}
> {{ at 
> org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)}}
> {{ at 
> org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)}}
> {{ at 
> org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)}}
> {{ at 
> org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:33)}}
> {{ Caused by: java.lang.RuntimeException: Could not load ConfigProvider}}
> {{ at 
> org.apache.deltaspike.core.api.config.ConfigResolver.getConfigProvider(ConfigResolver.java:628)}}
> {{ at 
> org.apache.deltaspike.core.api.config.ConfigResolver.resolve(ConfigResolver.java:613)}}
> {{ at 
> org.apache.deltaspike.testcontrol.api.junit.TestBaseConfig$ContainerIntegration.(TestBaseConfig.java:29)}}
> {{ ... 15 more}}
> The reason is, that {{deltaspike-core-impl}} is missing on the classpath. 
> Adding it solves the problem.
> So imho. we should add a {{runtime}} dependency on {{deltaspike-core-impl}} 
> to {{deltaspike-test-control-module-impl}}. It should be a matter of 
> replacing {{test}} to {{runtime}} on 
> {{deltaspike-core-impl}} in {{deltaspike-test-control-module-impl}}'s 
> {{pom.xml}}.
> I'll create a pull-request doing exactly that in a moment.
> EDIT: Pull-request exists at https://github.com/apache/deltaspike/pull/86



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (DELTASPIKE-1375) Correctly spell futurable

2019-03-25 Thread Thomas Andraschko (JIRA)
Thomas Andraschko created DELTASPIKE-1375:
-

 Summary: Correctly spell futurable
 Key: DELTASPIKE-1375
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1375
 Project: DeltaSpike
  Issue Type: Improvement
Reporter: Thomas Andraschko
Assignee: Thomas Andraschko
 Fix For: 1.9.1






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (DELTASPIKE-1369) [Scheduler] Enable/Disable based on custom condition

2019-03-25 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko resolved DELTASPIKE-1369.
---
   Resolution: Fixed
Fix Version/s: 1.9.1

Looks like already applied

> [Scheduler] Enable/Disable based on custom condition
> 
>
> Key: DELTASPIKE-1369
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1369
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Scheduler
>Reporter: Juri Berlanda
>Priority: Major
> Fix For: 1.9.1
>
>
> As discussed on the mailing list, I propose to introduce some kind of 
> pluggable Bean, which would allow to control both whether the Scheduler as a 
> whole should start, as well as to provide a hook for controlling each single 
> task invocation.
> The default implementation would always return true on both, which makes sure 
> the default behavior is the same as it has always been. Being a Bean, it can 
> be customized via CDI mechanisms (Specializes, Alternative, etc.).
> The Bean should provide the following signature:
>  {{boolean isSchedulerEnabled();}}
>  {{boolean vetoJobExecution(Class);}}
> TBD:
>  * Provide support for multiple implementations of {{SchedulerControl}}
>  * -Better name for shouldJobBeStarted?- Found
>  * -Use JobName in shouldJobBeStarted?- Not needed as discussed on mailing 
> list
> Development takes place at 
> [https://github.com/j-be/deltaspike/tree/scheduler-control]
> Pull request can be found at https://github.com/apache/deltaspike/pull/84



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (DELTASPIKE-1375) Correctly spell futurable

2019-03-25 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko resolved DELTASPIKE-1375.
---
Resolution: Fixed

> Correctly spell futurable
> -
>
> Key: DELTASPIKE-1375
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1375
> Project: DeltaSpike
>  Issue Type: Improvement
>    Reporter: Thomas Andraschko
>    Assignee: Thomas Andraschko
>Priority: Major
> Fix For: 1.9.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (DELTASPIKE-1355) counfByXXX failed with deltaspike and thorntail arquillian test

2019-03-25 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko closed DELTASPIKE-1355.
-
Resolution: Cannot Reproduce

No response, will close it for now.
If you can provide a reproducer, feel free to create a new issue again.

> counfByXXX failed with deltaspike and thorntail arquillian test
> ---
>
> Key: DELTASPIKE-1355
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1355
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Data-Module
>Affects Versions: 1.8.2
> Environment: Windows 10 / Maven 3.5 / Java 8 
>Reporter: Sylvain Bonnemaison
>    Assignee: Thomas Andraschko
>Priority: Major
>
> The following Repository class is defined :
> {{@Repository public interface UserRepository extends EntityRepository Long> {}}
>  {{   long countByUid(String uid);}}
>  {{   Stream findByUid(String uid);}}
>  {{   ...}}
>  {{}}}
> {{Stackstrace :}}
> {{Caused by: org.apache.deltaspike.data.api.QueryInvocationException: Failed 
> calling Repository: 
> [Repository=com.timm.demo.thorntail.deltaspike.persistence.UserRepository,entity=com.timm.demo.thorntail.deltaspike.entity.User,method=countByUid,exception=class
>  org.apache.deltaspike.data.api.QueryInvocationException,message=Failed 
> calling Repository: 
> [Repository=com.timm.demo.thorntail.deltaspike.persistence.UserRepository,entity=com.timm.demo.thorntail.deltaspike.entity.User,method=countByUid,
>  at 
> org.apache.deltaspike.data.impl.handler.QueryHandler.process(QueryHandler.java:163)
>  at 
> org.apache.deltaspike.data.impl.handler.QueryHandler.invoke(QueryHandler.java:130)
>  at 
> org.apache.deltaspike.data.impl.handler.QueryHandler$Proxy$_$$_WeldClientProxy.invoke(Unknown
>  Source) at 
> org.apache.deltaspike.proxy.spi.invocation.DeltaSpikeProxyInvocationHandler.proceed(DeltaSpikeProxyInvocationHandler.java:97)
>  at 
> org.apache.deltaspike.proxy.spi.invocation.DeltaSpikeProxyInvocationHandler.invoke(DeltaSpikeProxyInvocationHandler.java:78)
>  at 
> org.apache.deltaspike.proxy.spi.invocation.DeltaSpikeProxyInvocationHandler$Proxy$_$$_WeldClientProxy.invoke(Unknown
>  Source) at 
> com.timm.demo.thorntail.deltaspike.persistence.UserRepository$$DSPartialBeanProxy.countByUid(Unknown
>  Source) ... 46 more Caused by: 
> org.apache.deltaspike.data.api.QueryInvocationException: Failed calling 
> Repository: 
> [Repository=com.timm.demo.thorntail.deltaspike.persistence.UserRepository,entity=com.timm.demo.thorntail.deltaspike.entity.User,method=countByUid,
>  at 
> org.apache.deltaspike.data.impl.builder.DelegateQueryBuilder.execute(DelegateQueryBuilder.java:85)
>  at 
> org.apache.deltaspike.data.impl.builder.QueryBuilder.executeQuery(QueryBuilder.java:57)
>  at 
> org.apache.deltaspike.data.impl.builder.DelegateQueryBuilder$Proxy$_$$_WeldClientProxy.executeQuery(Unknown
>  Source) at 
> org.apache.deltaspike.data.impl.tx.TransactionalQueryRunner.executeNonTransactional(TransactionalQueryRunner.java:62)}}
> The findByXXX method works fine.
> Source code is on GitHub : [https://github.com/ruddy32/thorntail-deltaspike].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (DELTASPIKE-1371) JPACriteriaAPISupport Documentation exemple wrong

2019-03-12 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko resolved DELTASPIKE-1371.
---
Resolution: Fixed

> JPACriteriaAPISupport Documentation exemple wrong
> -
>
> Key: DELTASPIKE-1371
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1371
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 1.9.0
>Reporter: Daniel Dias dos Santos
>Priority: Critical
>  Labels: documentation
> Fix For: 1.9.1
>
> Attachments: criteria.png
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> at the following address : 
>  
> [https://deltaspike.apache.org/documentation/data.html#JPACriteriaAPISupport]
> contains join and boolean examples using criteria, but using the repository 
> {{AbstractEntityRepository which does not support criteria ()}}
> {{since it is used with Full or abstractFull}}
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1371) JPACriteriaAPISupport Documentation exemple wrong

2019-03-12 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1371:
---

Thanks!

> JPACriteriaAPISupport Documentation exemple wrong
> -
>
> Key: DELTASPIKE-1371
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1371
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 1.9.0
>Reporter: Daniel Dias dos Santos
>Priority: Critical
>  Labels: documentation
> Fix For: 1.9.1
>
> Attachments: criteria.png
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> at the following address : 
>  
> [https://deltaspike.apache.org/documentation/data.html#JPACriteriaAPISupport]
> contains join and boolean examples using criteria, but using the repository 
> {{AbstractEntityRepository which does not support criteria ()}}
> {{since it is used with Full or abstractFull}}
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1365) Support extra JPQL comparators in method expressions

2019-01-08 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko updated DELTASPIKE-1365:
--
Fix Version/s: 1.9.1

> Support extra JPQL comparators in method expressions
> 
>
> Key: DELTASPIKE-1365
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1365
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>Reporter: Ehsan Zaery Moghaddam
>Priority: Minor
> Fix For: 1.9.1
>
>
> The method expressions is currently supporting primary JPQL operators while 
> it seems feasible to implement other operators like "In", "NotIn", 
> "StartingWith", "True", etc. 
> I tried to add some of them and seems they works (of course thanks to the way 
> they've been designed so that it's easy to extend them). I'm just curious if 
> there is any technical consideration/limitation preventing us to have these 
> operators or is it because they were never been requested?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1365) Support extra JPQL comparators in method expressions

2019-01-08 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1365:
---

Thanks for the great PR!

> Support extra JPQL comparators in method expressions
> 
>
> Key: DELTASPIKE-1365
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1365
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>Reporter: Ehsan Zaery Moghaddam
>Priority: Minor
> Fix For: 1.9.1
>
>
> The method expressions is currently supporting primary JPQL operators while 
> it seems feasible to implement other operators like "In", "NotIn", 
> "StartingWith", "True", etc. 
> I tried to add some of them and seems they works (of course thanks to the way 
> they've been designed so that it's easy to extend them). I'm just curious if 
> there is any technical consideration/limitation preventing us to have these 
> operators or is it because they were never been requested?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (DELTASPIKE-1365) Support extra JPQL comparators in method expressions

2019-01-08 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko resolved DELTASPIKE-1365.
---
Resolution: Fixed

> Support extra JPQL comparators in method expressions
> 
>
> Key: DELTASPIKE-1365
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1365
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>Reporter: Ehsan Zaery Moghaddam
>Priority: Minor
> Fix For: 1.9.1
>
>
> The method expressions is currently supporting primary JPQL operators while 
> it seems feasible to implement other operators like "In", "NotIn", 
> "StartingWith", "True", etc. 
> I tried to add some of them and seems they works (of course thanks to the way 
> they've been designed so that it's easy to extend them). I'm just curious if 
> there is any technical consideration/limitation preventing us to have these 
> operators or is it because they were never been requested?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


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

2019-01-07 Thread Thomas Andraschko
+1

Am Mo., 7. Jan. 2019 um 18:09 Uhr schrieb Romain Manni-Bucau <
rmannibu...@gmail.com>:

> +1
>
> 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. 7 janv. 2019 à 18:08, Mark Struberg  a
> écrit :
>
> > 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
> > >
> >
> >
>


[jira] [Commented] (DELTASPIKE-1365) Support extra JPQL operators in method expressions

2018-12-12 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1365:
---

Probably just never requested.
If you would like to contribute it, you can simple provide a patch for the 
implementations and with some unittests. We could then review it.

> Support extra JPQL operators in method expressions
> --
>
> Key: DELTASPIKE-1365
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1365
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>Reporter: Ehsan Zaery Moghaddam
>Priority: Minor
>
> The method expressions is currently supporting primary JPQL operators while 
> it seems feasible to implement other operators like "In", "NotIn", 
> "StartingWith", "True", etc. 
> I tried to add some of them and seems they works (of course thanks to the way 
> they've been designed so that it's easy to extend them). I'm just curious if 
> there is any technical consideration/limitation preventing us to have these 
> operators or is it because they were never been requested?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1363) news links to post and examples.

2018-12-03 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1363:
---

Applied it - Thanks!
[~danieldiasjava] It would be great if you could close the PR on github.

> news links to post and examples.
> 
>
> Key: DELTASPIKE-1363
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1363
> Project: DeltaSpike
>  Issue Type: Task
>  Components: Documentation
>Reporter: Daniel Dias dos Santos
>Priority: Minor
>  Labels: documentation
> Attachments: 77.patch
>
>
> HI,
> I created an PR in => https://github.com/apache/deltaspike/pull/77 ,
> but via github it gets kinda bad to merge from the sides of you, so I was 
> suggested to add a pacth around here.
> thanks. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (DELTASPIKE-1363) news links to post and examples.

2018-12-03 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko closed DELTASPIKE-1363.
-
Resolution: Fixed

> news links to post and examples.
> 
>
> Key: DELTASPIKE-1363
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1363
> Project: DeltaSpike
>  Issue Type: Task
>  Components: Documentation
>Reporter: Daniel Dias dos Santos
>Priority: Minor
>  Labels: documentation
> Attachments: 77.patch
>
>
> HI,
> I created an PR in => https://github.com/apache/deltaspike/pull/77 ,
> but via github it gets kinda bad to merge from the sides of you, so I was 
> suggested to add a pacth around here.
> thanks. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Merge PRs

2018-11-26 Thread Thomas Andraschko
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 <https://twitter.com/rmannibucau> |  Blog
> > <https://rmannibucau.metawerx.net/> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <
> > https://github.com/rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | 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
> > > >
> > > >
> > >
> >
>


[jira] [Updated] (DELTASPIKE-1357) Update ASM to 7.0

2018-11-22 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko updated DELTASPIKE-1357:
--
Summary: Update ASM to 7.0  (was: Update ASM to 6.2.1 for preliminary Java 
12 support)

> Update ASM to 7.0
> -
>
> Key: DELTASPIKE-1357
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1357
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Proxy-Module
>Affects Versions: 1.9.0
>Reporter: Christian Beikov
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.1
>
>
> Java 12 has a new class file version and ASM 6.2 does not yet have support 
> for that. ASM 6.2.1 on the other hand already does. Since it's a minor 
> update, please get that into 1.9.1 so we can start early testing with Java 12.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1357) Update ASM to 6.2.1 for preliminary Java 12 support

2018-11-22 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1357:
---

wiill update to ASM 7.0

> Update ASM to 6.2.1 for preliminary Java 12 support
> ---
>
> Key: DELTASPIKE-1357
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1357
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Proxy-Module
>Affects Versions: 1.9.0
>Reporter: Christian Beikov
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.1
>
>
> Java 12 has a new class file version and ASM 6.2 does not yet have support 
> for that. ASM 6.2.1 on the other hand already does. Since it's a minor 
> update, please get that into 1.9.1 so we can start early testing with Java 12.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (DELTASPIKE-1362) Very early JSF3.x support

2018-11-22 Thread Thomas Andraschko (JIRA)
Thomas Andraschko created DELTASPIKE-1362:
-

 Summary: Very early JSF3.x support
 Key: DELTASPIKE-1362
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1362
 Project: DeltaSpike
  Issue Type: Improvement
Reporter: Thomas Andraschko
Assignee: Thomas Andraschko
 Fix For: 1.9.1






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (DELTASPIKE-1362) Very early JSF3.x support

2018-11-22 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko resolved DELTASPIKE-1362.
---
Resolution: Fixed

> Very early JSF3.x support
> -
>
> Key: DELTASPIKE-1362
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1362
> Project: DeltaSpike
>  Issue Type: Improvement
>    Reporter: Thomas Andraschko
>    Assignee: Thomas Andraschko
>Priority: Minor
> Fix For: 1.9.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Merge PRs

2018-11-12 Thread Thomas Andraschko
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
>
>


Merge PRs

2018-11-12 Thread Thomas Andraschko
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


[jira] [Commented] (DELTASPIKE-1330) Criteria with OR generate AND on query

2018-09-25 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1330:
---

It would be great if you could implement a unittest for it + fix the bug :)

> Criteria with OR generate AND on query
> --
>
> Key: DELTASPIKE-1330
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1330
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Data-Module
>Affects Versions: 1.8.1
> Environment: JDK 8u161, Wildfly 11, JEE 7
>Reporter: Arthur Pereira Gregório
>Priority: Critical
>
> If I use a OR on criteria the generated query use AND instead of OR to mix 
> the properties after WHERE clause.
> Sample: 
> {code:java}
> // code placeholder
> default List findAllBy(String filter, Boolean blocked, int start, int 
> pageSize) {
> final Criteria criteria = criteria();
> if (isNotBlank(filter)) {
> criteria.or(this.criteria()
> .likeIgnoreCase(User_.name, filter)
> .likeIgnoreCase(User_.username, filter)
> .likeIgnoreCase(User_.email, filter));
> } 
> if (blocked != null) {
> criteria.eq(this.getBlockedProperty(), blocked);
> }
> criteria.orderDesc(PersistentEntity_.createdOn);
> return criteria.createQuery()
> .setFirstResult(start)
> .setMaxResults(pageSize)
> .getResultList();
> }
> {code}
>  
> Generate this hibernate query: 
> 17:41:24,813 INFO  [stdout] (default task-64) Hibernate: select user0_.id as 
> id1_4_, user0_.created_by as created_2_4_, user0_.created_on as created_3_4_, 
> user0_.modified_by as modified4_4_, user0_.modified_on as modified5_4_, 
> user0_.blocked as blocked6_4_, user0_.email as email7_4_, user0_.id_group as 
> id_grou12_4_, user0_.name as name8_4_, user0_.password as password9_4_, 
> user0_.store_type as store_t10_4_, user0_.username as usernam11_4_ from 
> security.users user0_ *where (upper(user0_.name) like ?) and 
> (upper(user0_.username) like ?) and (upper(user0_.email) like ?)* order by 
> user0_.created_on desc limit ?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1352) Support count in Criteria

2018-09-25 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko updated DELTASPIKE-1352:
--
Summary: Support count in Criteria  (was: Get count of items with Criteria 
after filtering.)

> Support count in Criteria
> -
>
> Key: DELTASPIKE-1352
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1352
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Data-Module
>Reporter: mojo code
>Priority: Minor
>
> Hi. I'm filtering using "Criteria" by some  conditions It works correctly and 
> get the list of item that meets the conditions. I would like to get the count 
> of items which meets the conditions without getting this list in memory, I 
> just want to query this count number.
> Thanks in advance.
> ""
>     int findUserByCriteria(String name, Boolean active,  Integer idrol){
>         Criteria c = criteria();
>          
>          if(name != null)
>              c.likeIgnoreCase(User_.name, name + "%");
>          
>          if(active != null)
>              c.eq(User_.active, active);
>          
>          if(idrol != null)
>              c.eq(User_.idRol, idrol);
> .
> {color:#ff}  int count = ¿?{color}
> .
> return count;
> }
> ""



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1352) Get count of items with Criteria after filtering.

2018-09-25 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko updated DELTASPIKE-1352:
--
Component/s: Data-Module

> Get count of items with Criteria after filtering.
> -
>
> Key: DELTASPIKE-1352
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1352
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Data-Module
>Reporter: mojo code
>Priority: Minor
>
> Hi. I'm filtering using "Criteria" by some  conditions It works correctly and 
> get the list of item that meets the conditions. I would like to get the count 
> of items which meets the conditions without getting this list in memory, I 
> just want to query this count number.
> Thanks in advance.
> ""
>     int findUserByCriteria(String name, Boolean active,  Integer idrol){
>         Criteria c = criteria();
>          
>          if(name != null)
>              c.likeIgnoreCase(User_.name, name + "%");
>          
>          if(active != null)
>              c.eq(User_.active, active);
>          
>          if(idrol != null)
>              c.eq(User_.idRol, idrol);
> .
> {color:#ff}  int count = ¿?{color}
> .
> return count;
> }
> ""



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1352) Get count of items with Criteria after filtering.

2018-09-25 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko updated DELTASPIKE-1352:
--
Priority: Minor  (was: Major)

> Get count of items with Criteria after filtering.
> -
>
> Key: DELTASPIKE-1352
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1352
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Data-Module
>Reporter: mojo code
>Priority: Minor
>
> Hi. I'm filtering using "Criteria" by some  conditions It works correctly and 
> get the list of item that meets the conditions. I would like to get the count 
> of items which meets the conditions without getting this list in memory, I 
> just want to query this count number.
> Thanks in advance.
> ""
>     int findUserByCriteria(String name, Boolean active,  Integer idrol){
>         Criteria c = criteria();
>          
>          if(name != null)
>              c.likeIgnoreCase(User_.name, name + "%");
>          
>          if(active != null)
>              c.eq(User_.active, active);
>          
>          if(idrol != null)
>              c.eq(User_.idRol, idrol);
> .
> {color:#ff}  int count = ¿?{color}
> .
> return count;
> }
> ""



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1352) Get count of items with Criteria after filtering.

2018-09-25 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko updated DELTASPIKE-1352:
--
Issue Type: New Feature  (was: Test)

> Get count of items with Criteria after filtering.
> -
>
> Key: DELTASPIKE-1352
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1352
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Data-Module
>Reporter: mojo code
>Priority: Major
>
> Hi. I'm filtering using "Criteria" by some  conditions It works correctly and 
> get the list of item that meets the conditions. I would like to get the count 
> of items which meets the conditions without getting this list in memory, I 
> just want to query this count number.
> Thanks in advance.
> ""
>     int findUserByCriteria(String name, Boolean active,  Integer idrol){
>         Criteria c = criteria();
>          
>          if(name != null)
>              c.likeIgnoreCase(User_.name, name + "%");
>          
>          if(active != null)
>              c.eq(User_.active, active);
>          
>          if(idrol != null)
>              c.eq(User_.idRol, idrol);
> .
> {color:#ff}  int count = ¿?{color}
> .
> return count;
> }
> ""



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1352) Get count of items with Criteria after filtering.

2018-09-25 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1352:
---

seems like not implemented

Feel free to implement it and provide a patch/PR

> Get count of items with Criteria after filtering.
> -
>
> Key: DELTASPIKE-1352
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1352
> Project: DeltaSpike
>  Issue Type: Test
>  Components: Data-Module
>Reporter: mojo code
>Priority: Major
>
> Hi. I'm filtering using "Criteria" by some  conditions It works correctly and 
> get the list of item that meets the conditions. I would like to get the count 
> of items which meets the conditions without getting this list in memory, I 
> just want to query this count number.
> Thanks in advance.
> ""
>     int findUserByCriteria(String name, Boolean active,  Integer idrol){
>         Criteria c = criteria();
>          
>          if(name != null)
>              c.likeIgnoreCase(User_.name, name + "%");
>          
>          if(active != null)
>              c.eq(User_.active, active);
>          
>          if(idrol != null)
>              c.eq(User_.idRol, idrol);
> .
> {color:#ff}  int count = ¿?{color}
> .
> return count;
> }
> ""



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1355) counfByXXX failed with deltaspike and thorntail arquillian test

2018-09-24 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1355:
---

[~ruddy32]
our unitests for this are working fine:
[https://github.com/apache/deltaspike/blob/02ae7e6ba3050fd93af031b7b880ce004c024520/deltaspike/modules/data/impl/src/test/java/org/apache/deltaspike/data/impl/handler/QueryHandlerTest.java#L520]

Could you please the full logfile? So i can check the root cause.

> counfByXXX failed with deltaspike and thorntail arquillian test
> ---
>
> Key: DELTASPIKE-1355
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1355
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Data-Module
>Affects Versions: 1.8.2
> Environment: Windows 10 / Maven 3.5 / Java 8 
>Reporter: Sylvain Bonnemaison
>    Assignee: Thomas Andraschko
>Priority: Major
>
> The following Repository class is defined :
> {{@Repository public interface UserRepository extends EntityRepository Long> {}}
>  {{   long countByUid(String uid);}}
>  {{   Stream findByUid(String uid);}}
>  {{   ...}}
>  {{}}}
> {{Stackstrace :}}
> {{Caused by: org.apache.deltaspike.data.api.QueryInvocationException: Failed 
> calling Repository: 
> [Repository=com.timm.demo.thorntail.deltaspike.persistence.UserRepository,entity=com.timm.demo.thorntail.deltaspike.entity.User,method=countByUid,exception=class
>  org.apache.deltaspike.data.api.QueryInvocationException,message=Failed 
> calling Repository: 
> [Repository=com.timm.demo.thorntail.deltaspike.persistence.UserRepository,entity=com.timm.demo.thorntail.deltaspike.entity.User,method=countByUid,
>  at 
> org.apache.deltaspike.data.impl.handler.QueryHandler.process(QueryHandler.java:163)
>  at 
> org.apache.deltaspike.data.impl.handler.QueryHandler.invoke(QueryHandler.java:130)
>  at 
> org.apache.deltaspike.data.impl.handler.QueryHandler$Proxy$_$$_WeldClientProxy.invoke(Unknown
>  Source) at 
> org.apache.deltaspike.proxy.spi.invocation.DeltaSpikeProxyInvocationHandler.proceed(DeltaSpikeProxyInvocationHandler.java:97)
>  at 
> org.apache.deltaspike.proxy.spi.invocation.DeltaSpikeProxyInvocationHandler.invoke(DeltaSpikeProxyInvocationHandler.java:78)
>  at 
> org.apache.deltaspike.proxy.spi.invocation.DeltaSpikeProxyInvocationHandler$Proxy$_$$_WeldClientProxy.invoke(Unknown
>  Source) at 
> com.timm.demo.thorntail.deltaspike.persistence.UserRepository$$DSPartialBeanProxy.countByUid(Unknown
>  Source) ... 46 more Caused by: 
> org.apache.deltaspike.data.api.QueryInvocationException: Failed calling 
> Repository: 
> [Repository=com.timm.demo.thorntail.deltaspike.persistence.UserRepository,entity=com.timm.demo.thorntail.deltaspike.entity.User,method=countByUid,
>  at 
> org.apache.deltaspike.data.impl.builder.DelegateQueryBuilder.execute(DelegateQueryBuilder.java:85)
>  at 
> org.apache.deltaspike.data.impl.builder.QueryBuilder.executeQuery(QueryBuilder.java:57)
>  at 
> org.apache.deltaspike.data.impl.builder.DelegateQueryBuilder$Proxy$_$$_WeldClientProxy.executeQuery(Unknown
>  Source) at 
> org.apache.deltaspike.data.impl.tx.TransactionalQueryRunner.executeNonTransactional(TransactionalQueryRunner.java:62)}}
> The findByXXX method works fine.
> Source code is on GitHub : [https://github.com/ruddy32/thorntail-deltaspike].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (DELTASPIKE-1193) Repository methods should consider Boolean and boolean the same

2018-09-23 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko closed DELTASPIKE-1193.
-
Resolution: Won't Fix

> Repository methods should consider Boolean and boolean the same
> ---
>
> Key: DELTASPIKE-1193
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1193
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>Reporter: John D. Ament
>Assignee: John D. Ament
>Priority: Minor
>
> https://github.com/apache/deltaspike/blob/master/deltaspike/modules/data/impl/src/main/java/org/apache/deltaspike/data/impl/property/MethodPropertyImpl.java#L79
> In this case, we're treating boolean as valid for is methods, the same is not 
> applied to Boolean types.  This means your entities can't have Boolean 
> methods.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (DELTASPIKE-1355) counfByXXX failed with deltaspike and thorntail arquillian test

2018-09-23 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko reassigned DELTASPIKE-1355:
-

Assignee: Thomas Andraschko

> counfByXXX failed with deltaspike and thorntail arquillian test
> ---
>
> Key: DELTASPIKE-1355
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1355
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Data-Module
>Affects Versions: 1.8.2
> Environment: Windows 10 / Maven 3.5 / Java 8 
>Reporter: Sylvain Bonnemaison
>    Assignee: Thomas Andraschko
>Priority: Major
>
> The following Repository class is defined :
> {{@Repository public interface UserRepository extends EntityRepository Long> {}}
>  {{   long countByUid(String uid);}}
>  {{   Stream findByUid(String uid);}}
>  {{   ...}}
>  {{}}}
> {{Stackstrace :}}
> {{Caused by: org.apache.deltaspike.data.api.QueryInvocationException: Failed 
> calling Repository: 
> [Repository=com.timm.demo.thorntail.deltaspike.persistence.UserRepository,entity=com.timm.demo.thorntail.deltaspike.entity.User,method=countByUid,exception=class
>  org.apache.deltaspike.data.api.QueryInvocationException,message=Failed 
> calling Repository: 
> [Repository=com.timm.demo.thorntail.deltaspike.persistence.UserRepository,entity=com.timm.demo.thorntail.deltaspike.entity.User,method=countByUid,
>  at 
> org.apache.deltaspike.data.impl.handler.QueryHandler.process(QueryHandler.java:163)
>  at 
> org.apache.deltaspike.data.impl.handler.QueryHandler.invoke(QueryHandler.java:130)
>  at 
> org.apache.deltaspike.data.impl.handler.QueryHandler$Proxy$_$$_WeldClientProxy.invoke(Unknown
>  Source) at 
> org.apache.deltaspike.proxy.spi.invocation.DeltaSpikeProxyInvocationHandler.proceed(DeltaSpikeProxyInvocationHandler.java:97)
>  at 
> org.apache.deltaspike.proxy.spi.invocation.DeltaSpikeProxyInvocationHandler.invoke(DeltaSpikeProxyInvocationHandler.java:78)
>  at 
> org.apache.deltaspike.proxy.spi.invocation.DeltaSpikeProxyInvocationHandler$Proxy$_$$_WeldClientProxy.invoke(Unknown
>  Source) at 
> com.timm.demo.thorntail.deltaspike.persistence.UserRepository$$DSPartialBeanProxy.countByUid(Unknown
>  Source) ... 46 more Caused by: 
> org.apache.deltaspike.data.api.QueryInvocationException: Failed calling 
> Repository: 
> [Repository=com.timm.demo.thorntail.deltaspike.persistence.UserRepository,entity=com.timm.demo.thorntail.deltaspike.entity.User,method=countByUid,
>  at 
> org.apache.deltaspike.data.impl.builder.DelegateQueryBuilder.execute(DelegateQueryBuilder.java:85)
>  at 
> org.apache.deltaspike.data.impl.builder.QueryBuilder.executeQuery(QueryBuilder.java:57)
>  at 
> org.apache.deltaspike.data.impl.builder.DelegateQueryBuilder$Proxy$_$$_WeldClientProxy.executeQuery(Unknown
>  Source) at 
> org.apache.deltaspike.data.impl.tx.TransactionalQueryRunner.executeNonTransactional(TransactionalQueryRunner.java:62)}}
> The findByXXX method works fine.
> Source code is on GitHub : [https://github.com/ruddy32/thorntail-deltaspike].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Welcome Alex Falb as new Apache DeltaSpike

2018-08-07 Thread Thomas Andraschko
welcome!

2018-08-07 8:56 GMT+02:00 Romain Manni-Bucau :

> Welcome!
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  rmannibucau> |
> LinkedIn  | Book
>  ee-8-high-performance>
>
>
> Le mar. 7 août 2018 à 08:53, Gerhard Petracek  a
> écrit :
>
> > welcome!
> >
> > regards,
> > gerhard
> >
> >
> >
> > Am Di., 7. Aug. 2018 um 08:09 Uhr schrieb Mark Struberg
> > :
> >
> > > Dear fellow Apache DeltaSpike users and devs.
> > >
> > > The Apache DeltaSpike PMC has voted on inviting Alex Falb as a new
> > > committer to our project and he has accepted our invitation.
> > >
> > >
> > > Welcome Alex!
> > >
> > >
> > > the Apache DeltaSpike PMC
> >
>


[jira] [Assigned] (DELTASPIKE-1333) Support default methods in interface based configuration

2018-06-28 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko reassigned DELTASPIKE-1333:
-

Assignee: Mark Struberg

> Support default methods in interface based configuration
> 
>
> Key: DELTASPIKE-1333
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1333
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Configuration
>Affects Versions: 1.8.1
> Environment: Java 8, DeltaSpike 1.8.1
>Reporter: Niels Ull Harremoes
>Assignee: Mark Struberg
>Priority: Minor
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> I wanted to implement a default method in one of my configuration methods as 
> a simple way to configure a Duration:
> {code:java}
> @Configuration
> interface CacheConfig {
>   @ConfigProperty(name = "cache.lifetime", defaultValue = "P1D")
>   String cacheLifetime();
>   default Duration getCacheLifetimeDuration() {
>     try {
>        return Duration.parse(cacheLifetime());
>     } catch (DateTimeParseException e) {
>         ...
>   }
> }
> {code}
> However, a runtime I get the error
> {quote}java.lang.UnsupportedOperationException: public default 
> java.time.Duration com.example.CacheConfig.getLifetimeDuration() doesn't have 
> @ConfigProperty and therefore is illegal
> {quote}
> It would be nice if default methods were not processed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1239) Add ability to return QueryResult without predicate

2018-06-28 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1239:
---

Do you put this method inside your PersonRepository?
Why not just "QueryResult findAll()" then?

> Add ability to return QueryResult without predicate
> ---
>
> Key: DELTASPIKE-1239
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1239
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>Reporter: Matti Tahvonen
>Priority: Minor
>
> A following method name in repository would be handy for dynamic sorting and 
> paging of all entities:
> QueryResult findAllBy();
> Currently the library don't know how to handle that and it requires one to 
> add @Query("from Person") annotation. It would be handy if the query 
> annotation could be left out.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (DELTASPIKE-680) Lazy init should not rely on BeanManagerProvider

2018-06-28 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko closed DELTASPIKE-680.

Resolution: Done

Should already be implemted, i also refactor this alot during ~2 years ago.

> Lazy init should not rely on BeanManagerProvider
> 
>
> Key: DELTASPIKE-680
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-680
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>Affects Versions: 1.0.1
>Reporter: Harald Wellmann
>Assignee: Harald Wellmann
>Priority: Major
>
> Trying to work with DeltaSpike Data in OSGi (with on-the-fly OSGification, 
> see DELTASPIKE-660), I found that things break when the TCCL is not set to 
> the classloader of the current repository.
> This is caused by lazy initialization of {{RepositoryComponent}} using 
> {{BeanManagerProvider}}.
> Now the current strategies of {{BeanManagerProvider}} to locate the "current" 
> {{BeanManager}} do not work in OSGi where each bundle may have its own 
> BeanManager and there is no obvious interpretation of "current", and the TCCL 
> is not by default set to anything useful for this problem.
> However, in the context of DeltaSpike Data, is it easy to avoid the 
> {{BeanManagerProvider}} even with lazy initialization. The correct 
> {{BeanManager}} is known when a {{RepositoryComponent}} is instantiated, so 
> its sufficient to keep a reference to this {{BeanManager}} to perform lazy 
> initialization.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1206) support for CDI 2.0 feature

2018-06-28 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko updated DELTASPIKE-1206:
--
Fix Version/s: 2.0

> support for CDI 2.0  feature
> ---
>
> Key: DELTASPIKE-1206
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1206
> Project: DeltaSpike
>  Issue Type: Test
>Affects Versions: 1.7.1
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 2.0
>
>
> CDI 2.0 will add support for only picking up beans with an explicit scope 
> annotation. This reduced the memory footprint while also speeding up the 
> bootstrapping.
> See https://issues.jboss.org/browse/CDI-420
> We should add this annotation to our beans.xml and verify that we still work. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1218) Backport CDI 2.0 Request Context Controller

2018-06-28 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1218:
---

[~johndament]
Will you still do it? Otherwise i would close as many containers already have 
cdi2.0 support.

> Backport CDI 2.0 Request Context Controller
> ---
>
> Key: DELTASPIKE-1218
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1218
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: CdiControl
>Reporter: John D. Ament
>Assignee: John D. Ament
>Priority: Major
>
> Backport the new features of context control to enable users to leverage the 
> functionality now.
> {{@ActivateRequestContext}}
> {{RequestContextController}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1238) Create a better default TransactionStrategy

2018-06-28 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko updated DELTASPIKE-1238:
--
Fix Version/s: 2.0

> Create a better default TransactionStrategy
> ---
>
> Key: DELTASPIKE-1238
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1238
> Project: DeltaSpike
>  Issue Type: Improvement
>Reporter: John D. Ament
>Assignee: John D. Ament
>Priority: Major
> Fix For: 2.0
>
>
> Create a better default TransactionStrategy that handles more use cases out 
> of the box.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


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

2018-06-28 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko closed DELTASPIKE-1255.
-
Resolution: Incomplete

No response and example since 1+ year, i will close it.

> 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
>Priority: Major
>
> 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
(v7.6.3#76005)


[jira] [Comment Edited] (DELTASPIKE-1265) Align JSF module to features provided by JSF 2.3

2018-06-28 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko edited comment on DELTASPIKE-1265 at 6/28/18 11:56 AM:
-

What features do you mean?
 I would target it 2.0


was (Author: tandraschko):
What features to you mean?
I would target it 2.0

> Align JSF module to features provided by JSF 2.3
> 
>
> Key: DELTASPIKE-1265
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1265
> Project: DeltaSpike
>  Issue Type: Improvement
>Reporter: John D. Ament
>Priority: Major
> Fix For: 2.0
>
>
> The JSF module provides a lot of functionality that overlaps with JSF 2.1/2.2 
> features.  We should review this content and see what can be removed vs what 
> is provided OOTB.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (DELTASPIKE-1265) Align JSF module to features provided by JSF 2.3

2018-06-28 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko edited comment on DELTASPIKE-1265 at 6/28/18 11:56 AM:
-

What features do you mean?
 I would target it 2.0 (it's already 2.0, sry)


was (Author: tandraschko):
What features do you mean?
 I would target it 2.0

> Align JSF module to features provided by JSF 2.3
> 
>
> Key: DELTASPIKE-1265
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1265
> Project: DeltaSpike
>  Issue Type: Improvement
>Reporter: John D. Ament
>Priority: Major
> Fix For: 2.0
>
>
> The JSF module provides a lot of functionality that overlaps with JSF 2.1/2.2 
> features.  We should review this content and see what can be removed vs what 
> is provided OOTB.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1265) Align JSF module to features provided by JSF 2.3

2018-06-28 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1265:
---

What features to you mean?
I would target it 2.0

> Align JSF module to features provided by JSF 2.3
> 
>
> Key: DELTASPIKE-1265
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1265
> Project: DeltaSpike
>  Issue Type: Improvement
>Reporter: John D. Ament
>Priority: Major
> Fix For: 2.0
>
>
> The JSF module provides a lot of functionality that overlaps with JSF 2.1/2.2 
> features.  We should review this content and see what can be removed vs what 
> is provided OOTB.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (DELTASPIKE-1318) Unsatisfied dependencies for type ApplicationContext (deltaspike-cdictrl-weld) in payara 4.1.2.174

2018-06-28 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko reassigned DELTASPIKE-1318:
-

Assignee: Mark Struberg

> Unsatisfied dependencies for type ApplicationContext 
> (deltaspike-cdictrl-weld) in payara 4.1.2.174
> --
>
> Key: DELTASPIKE-1318
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1318
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: CdiControl
>Affects Versions: 1.8.1
> Environment: payara 4.1.2.174
>Reporter: Andreas Keefer
>Assignee: Mark Struberg
>Priority: Major
>
> ApplicationContext can't be injected in WeldContextControl on payara 4.1.2.174
>  
> Maven dependencies
> {code:java}
> 
> org.apache.deltaspike.cdictrl
> deltaspike-cdictrl-api
> compile
> 
> 
> org.apache.deltaspike.cdictrl
> deltaspike-cdictrl-weld
> runtime
> 
> {code}
>  Sample Bean:
> {code:java}
> @Singleton
> @Startup
> public class KafkaVehicleReceiver {
>   @Inject
>   private ContextControl contextControl;
>   ...
> }{code}
>  payara log:
> {code:java}
> [2018-02-27T00:40:54.713+0100] [Payara 4.1] [SCHWERWIEGEND] [NCLS-CORE-00026] 
> [javax.enterprise.system.core] [tid: _ThreadID=47 
> _ThreadName=admin-thread-pool::admin-listener(1)] [timeMillis: 1519688454713] 
> [levelValue: 1000] [[
> Exception during lifecycle processing
> org.glassfish.deployment.common.DeploymentException: CDI deployment 
> failure:WELD-001408: Unsatisfied dependencies for type ApplicationContext 
> with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private 
> org.apache.deltaspike.cdise.weld.WeldContextControl.applicationContext
> at 
> org.apache.deltaspike.cdise.weld.WeldContextControl.applicationContext(WeldContextControl.java:0)
> at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:270)
> at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:131)
> at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:333)
> at 
> com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:497)
> at 
> com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:220)
> at 
> org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:508)
> at 
> com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:544)
> at 
> com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:540)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at 
> com.sun.enterprise.v3.admin.CommandRunnerImpl$2.execute(CommandRunnerImpl.java:539)
> at 
> com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:570)
> at 
> com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:562)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at 
> com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:561)
> at 
> com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1469)
> at 
> com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1300(CommandRunnerImpl.java:111)
> at 
> com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1851)
> at 
> com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1727)
> at 
> org.glassfish.admin.rest.resources.admin.CommandResource.executeCommand(CommandResource.java:407)
> at 
> org.glassfish.admin.rest.resources.admin.CommandResource.execCommandSimpInMultOut(CommandResource.java:234)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
> at 
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)
> at 
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)

[jira] [Closed] (DELTASPIKE-1007) test @Transactional and @TransactionScoped support for @Repository

2018-06-28 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko closed DELTASPIKE-1007.
-
Resolution: Later

> test @Transactional and @TransactionScoped support for @Repository
> --
>
> Key: DELTASPIKE-1007
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1007
> Project: DeltaSpike
>  Issue Type: Task
>  Components: Data-Module, Tests
>Affects Versions: 1.5.1
>Reporter: Gerhard Petracek
>Assignee: Harald Wellmann
>Priority: Major
>
> currently it's tested manually, but we should add a test to the test-suite.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (DELTASPIKE-1342) Upgrade to ASM 6.1 for Java 10 support

2018-06-28 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko closed DELTASPIKE-1342.
-

> Upgrade to ASM 6.1 for Java 10 support
> --
>
> Key: DELTASPIKE-1342
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1342
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module, PartialBean, Proxy-Module
>Reporter: Christian Beikov
>Priority: Major
> Fix For: 1.9.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (DELTASPIKE-1342) Upgrade to ASM 6.1 for Java 10 support

2018-06-28 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko resolved DELTASPIKE-1342.
---
   Resolution: Duplicate
Fix Version/s: 1.9.0

h2. DELTASPIKE-1351

> Upgrade to ASM 6.1 for Java 10 support
> --
>
> Key: DELTASPIKE-1342
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1342
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module, PartialBean, Proxy-Module
>Reporter: Christian Beikov
>Priority: Major
> Fix For: 1.9.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1351) Java 10: IllegalArgumentException in ClassReader.

2018-06-27 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko updated DELTASPIKE-1351:
--
Fix Version/s: 1.9.0

> Java 10: IllegalArgumentException in ClassReader.
> ---
>
> Key: DELTASPIKE-1351
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1351
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Proxy-Module
>Affects Versions: 1.8.2
>Reporter: Florian Lieb
>Priority: Major
> Fix For: 1.9.0
>
>
> With java10, we get an exception
> {code:java}
> Caused by: java.lang.IllegalArgumentException
> at org.apache.deltaspike.proxy.asm.ClassReader.(ClassReader.java:160)
> at org.apache.deltaspike.proxy.asm.ClassReader.(ClassReader.java:143)
> at org.apache.deltaspike.proxy.asm.ClassReader.(ClassReader.java:418)
> at 
> org.apache.deltaspike.proxy.impl.AsmDeltaSpikeProxyClassGenerator.generateProxyClassBytes(AsmDeltaSpikeProxyClassGenerator.java:154)
> ... 51 more
> at 
> org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:44)
> at 
> org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:61)
> at 
> org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:420){code}
>  
> Since ASM is shaded within deltaspike-proxy-asm, it is impossible to update 
> ASM to a more recent version.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (DELTASPIKE-1351) Java 10: IllegalArgumentException in ClassReader.

2018-06-27 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko resolved DELTASPIKE-1351.
---
Resolution: Fixed

> Java 10: IllegalArgumentException in ClassReader.
> ---
>
> Key: DELTASPIKE-1351
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1351
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Proxy-Module
>Affects Versions: 1.8.2
>Reporter: Florian Lieb
>Priority: Major
> Fix For: 1.9.0
>
>
> With java10, we get an exception
> {code:java}
> Caused by: java.lang.IllegalArgumentException
> at org.apache.deltaspike.proxy.asm.ClassReader.(ClassReader.java:160)
> at org.apache.deltaspike.proxy.asm.ClassReader.(ClassReader.java:143)
> at org.apache.deltaspike.proxy.asm.ClassReader.(ClassReader.java:418)
> at 
> org.apache.deltaspike.proxy.impl.AsmDeltaSpikeProxyClassGenerator.generateProxyClassBytes(AsmDeltaSpikeProxyClassGenerator.java:154)
> ... 51 more
> at 
> org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:44)
> at 
> org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:61)
> at 
> org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:420){code}
>  
> Since ASM is shaded within deltaspike-proxy-asm, it is impossible to update 
> ASM to a more recent version.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1351) Java 10: IllegalArgumentException in ClassReader.

2018-06-27 Thread Thomas Andraschko (JIRA)


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

Thomas Andraschko commented on DELTASPIKE-1351:
---

Upgraded master from 6.0 to 6.2.
Would be great if you can build by source/get a snapshot and give it a try.

> Java 10: IllegalArgumentException in ClassReader.
> ---
>
> Key: DELTASPIKE-1351
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1351
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Proxy-Module
>Affects Versions: 1.8.2
>Reporter: Florian Lieb
>Priority: Major
>
> With java10, we get an exception
> {code:java}
> Caused by: java.lang.IllegalArgumentException
> at org.apache.deltaspike.proxy.asm.ClassReader.(ClassReader.java:160)
> at org.apache.deltaspike.proxy.asm.ClassReader.(ClassReader.java:143)
> at org.apache.deltaspike.proxy.asm.ClassReader.(ClassReader.java:418)
> at 
> org.apache.deltaspike.proxy.impl.AsmDeltaSpikeProxyClassGenerator.generateProxyClassBytes(AsmDeltaSpikeProxyClassGenerator.java:154)
> ... 51 more
> at 
> org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:44)
> at 
> org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:61)
> at 
> org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:420){code}
>  
> Since ASM is shaded within deltaspike-proxy-asm, it is impossible to update 
> ASM to a more recent version.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1347) DeltaSpike Window Scope doesn't work with IE 11 sometimes

2018-05-24 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko commented on DELTASPIKE-1347:
---

A deeper analysis or patch would be great. The code should be very well 
commented.

> DeltaSpike Window Scope doesn't work with IE 11 sometimes
> -
>
> Key: DELTASPIKE-1347
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1347
> Project: DeltaSpike
>  Issue Type: Bug
>Affects Versions: 1.8.1
>Reporter: Udo Schnurpfeil
>Priority: Minor
>
> I found a problem with the window id and *IE11*, described in TOBAGO-1901.
> I've tested the example of deltaspike current version:
> {code}
> $ cd deltaspike/examples/jsf-playground
> $ mvn clean package tomee:run -Prun-tomee-1.7.2
> {code}
> Browse with IE to:
> {code}
> http://10.211.55.2:8080/ds/views/windowhandling/clientwindow/test.xhtml
> {code}
> Clicking "GET Link", "Postback" or "Postback with outcome" will generate a 
> new window id, every click.
> The bug doesn't happen, when opening the F12 tool, which make it tricky to 
> debug.
> The bug doesn't happen, when adding the URL in the trusted sites 
> configuration of IE. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [VOTE] Release Apache DeltaSpike-1.8.2

2018-05-16 Thread Thomas Andraschko
+1

2018-05-16 6:48 GMT+02:00 Romain Manni-Bucau :

> +1
>
> Le mer. 16 mai 2018 00:11, Daniel Cunha  a écrit :
>
> > +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] [Updated] (DELTASPIKE-1339) Add support for dynamic interceptor binding, added via Extension

2018-05-02 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko updated DELTASPIKE-1339:
--
Fix Version/s: 1.8.2

> Add support for dynamic interceptor binding, added via Extension
> 
>
> Key: DELTASPIKE-1339
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1339
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module, PartialBean, Proxy-Module
>    Reporter: Thomas Andraschko
>    Assignee: Thomas Andraschko
>Priority: Major
> Fix For: 1.8.2, 1.9.0
>
>
> JCache does something simliar to:
> public @interface CachedResult \{...}
> @CachedResult
>  public class CachedResultInterceptor \{...}
> and a Extension which does:
>  beforeBeanDiscoveryEvent.addInterceptorBinding(CachedResult .class);
> This currently doesn't work because we check for @InterceptorBinding on the 
> annotation



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (DELTASPIKE-1341) [perf] QueryProcessorFactory could reuse QueryProcessors

2018-04-25 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko resolved DELTASPIKE-1341.
---
Resolution: Fixed

> [perf] QueryProcessorFactory could reuse QueryProcessors
> 
>
> Key: DELTASPIKE-1341
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1341
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>    Reporter: Thomas Andraschko
>    Assignee: Thomas Andraschko
>Priority: Minor
> Fix For: 1.9.0
>
>
> currently there are recreated for each method can be easily be handled as 
> appscoped



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1341) [perf] QueryProcessorFactory could reuse QueryProcessors

2018-04-25 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko updated DELTASPIKE-1341:
--
Description: currently there are recreated for each method can be easily be 
handled as appscoped

> [perf] QueryProcessorFactory could reuse QueryProcessors
> 
>
> Key: DELTASPIKE-1341
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1341
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>    Reporter: Thomas Andraschko
>    Assignee: Thomas Andraschko
>Priority: Minor
> Fix For: 1.9.0
>
>
> currently there are recreated for each method can be easily be handled as 
> appscoped



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1341) [perf] QueryProcessorFactory could reuse QueryProcessors

2018-04-25 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko updated DELTASPIKE-1341:
--
Fix Version/s: (was: 2.0)
   1.9.0

> [perf] QueryProcessorFactory could reuse QueryProcessors
> 
>
> Key: DELTASPIKE-1341
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1341
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>    Reporter: Thomas Andraschko
>    Assignee: Thomas Andraschko
>Priority: Minor
> Fix For: 1.9.0
>
>
> currently there are recreated for each method can be easily be handled as 
> appscoped



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1341) [perf] QueryProcessorFactory could reuse QueryProcessors

2018-04-25 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko updated DELTASPIKE-1341:
--
Summary: [perf] QueryProcessorFactory could reuse QueryProcessors  (was: 
[perf] QueryProcessorFactory can handle QueryProcessor as static if possible)

> [perf] QueryProcessorFactory could reuse QueryProcessors
> 
>
> Key: DELTASPIKE-1341
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1341
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>    Reporter: Thomas Andraschko
>    Assignee: Thomas Andraschko
>Priority: Minor
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (DELTASPIKE-1340) Delegate to JPA 2.2 getResultStream

2018-04-25 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko resolved DELTASPIKE-1340.
---
Resolution: Fixed

> Delegate to JPA 2.2 getResultStream
> ---
>
> Key: DELTASPIKE-1340
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1340
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>    Reporter: Thomas Andraschko
>    Assignee: Thomas Andraschko
>Priority: Minor
> Fix For: 1.9.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (DELTASPIKE-1341) [perf] QueryProcessorFactory can handle QueryProcessor as static if possible

2018-04-25 Thread Thomas Andraschko (JIRA)
Thomas Andraschko created DELTASPIKE-1341:
-

 Summary: [perf] QueryProcessorFactory can handle QueryProcessor as 
static if possible
 Key: DELTASPIKE-1341
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1341
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Data-Module
Reporter: Thomas Andraschko
Assignee: Thomas Andraschko
 Fix For: 2.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (DELTASPIKE-1340) Delegate to JPA 2.2 getResultStream

2018-04-25 Thread Thomas Andraschko (JIRA)
Thomas Andraschko created DELTASPIKE-1340:
-

 Summary: Delegate to JPA 2.2 getResultStream
 Key: DELTASPIKE-1340
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1340
 Project: DeltaSpike
  Issue Type: Improvement
  Components: Data-Module
Reporter: Thomas Andraschko
Assignee: Thomas Andraschko
 Fix For: 1.9.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: InterceptorStrategy?

2018-04-24 Thread Thomas Andraschko
basically +1
but its still used currently


2018-04-23 11:46 GMT+02:00 Romain Manni-Bucau :

> Hi guys,
>
> Do we still need InterceptorStrategy?
>
> If not, can we deprecate it and remove it from our built-in interceptors?
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  rmannibucau> |
> LinkedIn  | Book
>  ee-8-high-performance>
>


[jira] [Updated] (DELTASPIKE-1339) Add support for dynamic interceptor binding, added via Extension

2018-04-24 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko updated DELTASPIKE-1339:
--
Description: 
JCache does something simliar to:

public @interface CachedResult \{...}

@CachedResult
 public class CachedResultInterceptor \{...}

and a Extension which does:
 beforeBeanDiscoveryEvent.addInterceptorBinding(CachedResult .class);

This currently doesn't work because we check for @InterceptorBinding on the 
annotation

  was:
JCache something simliar to:

public @interface CachedResult \{...}

@CachedResult
public class CachedResultInterceptor \{...}

and a Extension which does:
beforeBeanDiscoveryEvent.addInterceptorBinding(CachedResult .class);


This currently doesn't work because we check for @InterceptorBinding on the 
annotation


> Add support for dynamic interceptor binding, added via Extension
> 
>
> Key: DELTASPIKE-1339
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1339
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module, PartialBean, Proxy-Module
>    Reporter: Thomas Andraschko
>    Assignee: Thomas Andraschko
>Priority: Major
> Fix For: 1.9.0
>
>
> JCache does something simliar to:
> public @interface CachedResult \{...}
> @CachedResult
>  public class CachedResultInterceptor \{...}
> and a Extension which does:
>  beforeBeanDiscoveryEvent.addInterceptorBinding(CachedResult .class);
> This currently doesn't work because we check for @InterceptorBinding on the 
> annotation



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1339) Add support for dynamic interceptor binding, added via Extension

2018-04-24 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko updated DELTASPIKE-1339:
--
Description: 
JCache something simliar to:

public @interface CachedResult \{...}

@CachedResult
public class CachedResultInterceptor \{...}

and a Extension which does:
beforeBeanDiscoveryEvent.addInterceptorBinding(CachedResult .class);


This currently doesn't work because we check for @InterceptorBinding on the 
annotation

> Add support for dynamic interceptor binding, added via Extension
> 
>
> Key: DELTASPIKE-1339
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1339
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module, PartialBean, Proxy-Module
>    Reporter: Thomas Andraschko
>    Assignee: Thomas Andraschko
>Priority: Major
> Fix For: 1.9.0
>
>
> JCache something simliar to:
> public @interface CachedResult \{...}
> @CachedResult
> public class CachedResultInterceptor \{...}
> and a Extension which does:
> beforeBeanDiscoveryEvent.addInterceptorBinding(CachedResult .class);
> This currently doesn't work because we check for @InterceptorBinding on the 
> annotation



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1266) Remove != JavaEE8 workarounds

2018-04-23 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko updated DELTASPIKE-1266:
--
Description: 
* EntityGraphHelper
 * JSF module (e.g. remove all the reflection hacks for ClientWindow)
 * remove OWB 1.1.x workarounds in proxy module

  was:
* EntityGraphHelper
 * JSF module / e.g. optional ClientWindow


> Remove != JavaEE8 workarounds
> -
>
> Key: DELTASPIKE-1266
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1266
> Project: DeltaSpike
>  Issue Type: Improvement
>    Reporter: Thomas Andraschko
>Priority: Major
> Fix For: 2.0
>
>
> * EntityGraphHelper
>  * JSF module (e.g. remove all the reflection hacks for ClientWindow)
>  * remove OWB 1.1.x workarounds in proxy module



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1266) Remove != JavaEE8 workarounds

2018-04-23 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko updated DELTASPIKE-1266:
--
Summary: Remove != JavaEE8 workarounds  (was: Remove JavaEE8 Hacks)

> Remove != JavaEE8 workarounds
> -
>
> Key: DELTASPIKE-1266
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1266
> Project: DeltaSpike
>  Issue Type: Improvement
>    Reporter: Thomas Andraschko
>Priority: Major
> Fix For: 2.0
>
>
> * EntityGraphHelper
>  * JSF module / e.g. optional ClientWindow



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1239) Add ability to return QueryResult without predicate

2018-04-23 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko updated DELTASPIKE-1239:
--
Priority: Minor  (was: Major)

> Add ability to return QueryResult without predicate
> ---
>
> Key: DELTASPIKE-1239
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1239
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>Reporter: Matti Tahvonen
>Priority: Minor
>
> A following method name in repository would be handy for dynamic sorting and 
> paging of all entities:
> QueryResult findAllBy();
> Currently the library don't know how to handle that and it requires one to 
> add @Query("from Person") annotation. It would be handy if the query 
> annotation could be left out.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1193) Repository methods should consider Boolean and boolean the same

2018-04-23 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko commented on DELTASPIKE-1193:
---

i would say thats the default "beans" mechanism. "Boolean" get only be get via 
"get", "boolean" via "is...".
I would close it.

> Repository methods should consider Boolean and boolean the same
> ---
>
> Key: DELTASPIKE-1193
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1193
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>Reporter: John D. Ament
>Assignee: John D. Ament
>Priority: Major
>
> https://github.com/apache/deltaspike/blob/master/deltaspike/modules/data/impl/src/main/java/org/apache/deltaspike/data/impl/property/MethodPropertyImpl.java#L79
> In this case, we're treating boolean as valid for is methods, the same is not 
> applied to Boolean types.  This means your entities can't have Boolean 
> methods.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1193) Repository methods should consider Boolean and boolean the same

2018-04-23 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko updated DELTASPIKE-1193:
--
Priority: Minor  (was: Major)

> Repository methods should consider Boolean and boolean the same
> ---
>
> Key: DELTASPIKE-1193
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1193
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>Reporter: John D. Ament
>Assignee: John D. Ament
>Priority: Minor
>
> https://github.com/apache/deltaspike/blob/master/deltaspike/modules/data/impl/src/main/java/org/apache/deltaspike/data/impl/property/MethodPropertyImpl.java#L79
> In this case, we're treating boolean as valid for is methods, the same is not 
> applied to Boolean types.  This means your entities can't have Boolean 
> methods.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1280) Automatic support for count* methods in EntityRepository

2018-04-23 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko updated DELTASPIKE-1280:
--
Priority: Minor  (was: Major)

> Automatic support for count* methods in EntityRepository
> 
>
> Key: DELTASPIKE-1280
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1280
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Data-Module
>Reporter: Artur Signell
>Priority: Minor
> Fix For: 1.9.0
>
>
> Stream findByLocation(String location)
> will automatically create a query for finding all persons with the given 
> location.
> long countByLocation(String location);
> could automatically create a query for counting all persons with the given 
> location.
> This would be 1:1 with how Spring Data works: 
> http://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.core-concepts



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1280) Automatic support for count* methods in EntityRepository

2018-04-23 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko updated DELTASPIKE-1280:
--
Fix Version/s: 1.9.0

> Automatic support for count* methods in EntityRepository
> 
>
> Key: DELTASPIKE-1280
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1280
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Data-Module
>Reporter: Artur Signell
>Priority: Minor
> Fix For: 1.9.0
>
>
> Stream findByLocation(String location)
> will automatically create a query for finding all persons with the given 
> location.
> long countByLocation(String location);
> could automatically create a query for counting all persons with the given 
> location.
> This would be 1:1 with how Spring Data works: 
> http://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.core-concepts



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (DELTASPIKE-1280) Automatic support for count* methods in EntityRepository

2018-04-23 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko resolved DELTASPIKE-1280.
---
Resolution: Fixed
  Assignee: Thomas Andraschko

> Automatic support for count* methods in EntityRepository
> 
>
> Key: DELTASPIKE-1280
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1280
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Data-Module
>Reporter: Artur Signell
>    Assignee: Thomas Andraschko
>Priority: Minor
> Fix For: 1.9.0
>
>
> Stream findByLocation(String location)
> will automatically create a query for finding all persons with the given 
> location.
> long countByLocation(String location);
> could automatically create a query for counting all persons with the given 
> location.
> This would be 1:1 with how Spring Data works: 
> http://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.core-concepts



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1315) EntityRepository should offer an findOptionalBy

2018-04-23 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko updated DELTASPIKE-1315:
--
Priority: Minor  (was: Major)

> EntityRepository should offer an findOptionalBy
> ---
>
> Key: DELTASPIKE-1315
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1315
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Data-Module
>Reporter: Kevin Grüneberg
>Priority: Minor
> Fix For: 1.9.0
>
>
> The EntityRepository interface offers an findBy(PK id) method, that returns 
> the entity based on the ID. It would be great to also have an 
> findOptionalBy(PK id) that returns an optional.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (DELTASPIKE-1315) EntityRepository should offer an findOptionalBy

2018-04-23 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko resolved DELTASPIKE-1315.
---
Resolution: Fixed
  Assignee: Thomas Andraschko

> EntityRepository should offer an findOptionalBy
> ---
>
> Key: DELTASPIKE-1315
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1315
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Data-Module
>Reporter: Kevin Grüneberg
>    Assignee: Thomas Andraschko
>Priority: Minor
> Fix For: 1.9.0
>
>
> The EntityRepository interface offers an findBy(PK id) method, that returns 
> the entity based on the ID. It would be great to also have an 
> findOptionalBy(PK id) that returns an optional.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1315) EntityRepository should offer an findOptionalBy

2018-04-23 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko updated DELTASPIKE-1315:
--
Fix Version/s: 1.9.0

> EntityRepository should offer an findOptionalBy
> ---
>
> Key: DELTASPIKE-1315
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1315
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Data-Module
>Reporter: Kevin Grüneberg
>Priority: Major
> Fix For: 1.9.0
>
>
> The EntityRepository interface offers an findBy(PK id) method, that returns 
> the entity based on the ID. It would be great to also have an 
> findOptionalBy(PK id) that returns an optional.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1286) Support save multiple entities

2018-04-23 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko updated DELTASPIKE-1286:
--
Fix Version/s: (was: 1.8.2)

> Support save multiple entities
> --
>
> Key: DELTASPIKE-1286
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1286
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>Affects Versions: 1.7.2, 1.8.0
>Reporter: Gilberto C Andrade
>Priority: Minor
>  Labels: jpa
>
> I see a common pattern appearing in our code that it iterates the list of 
> entities and calls save(S).
> I would like to propose another save method to *EntityRepository* class:
> {code:java}
> public abstract  List save(Iterable entities) {
> List result = new ArrayList();
> if (entities == null) {
> return result;
> }
> for (S entity : entities) {
> result.add(save(entity));
> }
> return result;
> }
> {code}
> I don't know what is the impact on transaction - I've not worked with batch 
> yet.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1286) Support save multiple entities

2018-04-23 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko updated DELTASPIKE-1286:
--
Issue Type: Improvement  (was: Bug)

> Support save multiple entities
> --
>
> Key: DELTASPIKE-1286
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1286
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>Affects Versions: 1.7.2, 1.8.0
>Reporter: Gilberto C Andrade
>Priority: Minor
>  Labels: jpa
>
> I see a common pattern appearing in our code that it iterates the list of 
> entities and calls save(S).
> I would like to propose another save method to *EntityRepository* class:
> {code:java}
> public abstract  List save(Iterable entities) {
> List result = new ArrayList();
> if (entities == null) {
> return result;
> }
> for (S entity : entities) {
> result.add(save(entity));
> }
> return result;
> }
> {code}
> I don't know what is the impact on transaction - I've not worked with batch 
> yet.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1007) test @Transactional and @TransactionScoped support for @Repository

2018-04-23 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko commented on DELTASPIKE-1007:
---

We maybe don't have tests for Transactional but we have many many tests for 
interceptors. I think it's ok to close. WDYT [~gpetracek]?

> test @Transactional and @TransactionScoped support for @Repository
> --
>
> Key: DELTASPIKE-1007
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1007
> Project: DeltaSpike
>  Issue Type: Task
>  Components: Data-Module, Tests
>Affects Versions: 1.5.1
>Reporter: Gerhard Petracek
>Assignee: Harald Wellmann
>Priority: Major
>
> currently it's tested manually, but we should add a test to the test-suite.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DELTASPIKE-1315) EntityRepository should offer an findOptionalBy

2018-04-23 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko commented on DELTASPIKE-1315:
---

Could you maybe provide a patch for this feature?

> EntityRepository should offer an findOptionalBy
> ---
>
> Key: DELTASPIKE-1315
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1315
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Data-Module
>Reporter: Kevin Grüneberg
>Priority: Major
>
> The EntityRepository interface offers an findBy(PK id) method, that returns 
> the entity based on the ID. It would be great to also have an 
> findOptionalBy(PK id) that returns an optional.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (DELTASPIKE-1339) Add support for dynamic interceptor binding, added via Extension

2018-04-23 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko resolved DELTASPIKE-1339.
---
Resolution: Fixed

> Add support for dynamic interceptor binding, added via Extension
> 
>
> Key: DELTASPIKE-1339
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1339
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module, PartialBean, Proxy-Module
>    Reporter: Thomas Andraschko
>    Assignee: Thomas Andraschko
>Priority: Major
> Fix For: 1.9.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DELTASPIKE-1339) Add support for dynamic interceptor binding, added via Extension

2018-04-23 Thread Thomas Andraschko (JIRA)

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

Thomas Andraschko updated DELTASPIKE-1339:
--
Component/s: Proxy-Module
 PartialBean
 Data-Module

> Add support for dynamic interceptor binding, added via Extension
> 
>
> Key: DELTASPIKE-1339
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1339
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module, PartialBean, Proxy-Module
>    Reporter: Thomas Andraschko
>    Assignee: Thomas Andraschko
>Priority: Major
> Fix For: 1.9.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


  1   2   3   4   5   6   7   8   9   >