Re: [Proposal] CdiManagedRunnable

[Romain Manni-Bucau]

Le 21 sept. 2015 01:59, "Martin Kouba"  a écrit :
>
> Dne 18.9.2015 v 16:28 Romain Manni-Bucau napsal(a):
>
>> Hi
>>
>> I like the idea but isnt it close enough of concurrency utilities to kind
>> of put it in this spec? There is this proxy factory which could/should
>> support scopes IMO.
>>
>> CDI has few thread requirements which is good IMO so I would put it in
the
>> "thread" spec.
>
>
> Hm, is there any "Concurrency Utilities for Java EE" update planned for
Java EE 8? I can't find any info.
>

Dont think so but spec are updated when needed so if can be a need.

> Also the feature I was talking about is targeted solely to Java SE. I
misread the original message from Thomas.
>

EE is very badly used in this spec. Think it has been used to differentiate
to se = the jvm. It is just a lib.

>
>>
>> Romain
>> Le 18 sept. 2015 07:23, "Martin Kouba"  a écrit :
>>
>>> Hi Thomas,
>>>
>>> I think it's a good idea. Weld has a similar API [1], except it's
focused
>>> solely on the "thread-local-based context". We are also considering the
use
>>> of an interceptor to active/deactivate the ThreadContext per business
>>> method invocation [2].
>>>
>>> I wonder, whether this should be standardized in CDI 2.0. It seems to me
>>> that CDI SE lacks some built-in contexts. Unlike Java EE where the
built-in
>>> scopes align with the lifecycle of EE components (@RequestScoped,
>>> @SessionScoped, etc.).
>>>
>>> Martin
>>>
>>> [1]
>>>
>>>
http://docs.jboss.org/weld/reference/latest/en-US/html/environments.html#_thread_context
>>>
>>> [2]
>>> https://issues.jboss.org/browse/WELD-1905
>>>
>>>
>>> Dne 10.9.2015 v 18:02 Thomas Andraschko napsal(a):
>>>
 Hi,

 it's often required to manual activate scopes in a async
threads/runnables
 if you don't use JavaEE 7.
 I already used this in 3-4 projects in the last 3 years.

 My current API looks like:

 CdiManagedRunnable - A abstract class with implements Runnable and
starts
 the RequestScoped via ContextControl and a new scope called ThreadScope
 RequestScoped is optional, CdiManagedRunnable#isRequestScopedSupported
 return false per default and can be overwritten by the user.

 ThreadContext - A AbstractContext implementation which a static static
 ThreadLocal

 ThreadContextExtension
 ThreadScoped

 WDYT? Is this useful for other people too?

 Regards,
 Thomas


>>> --
>>> Martin Kouba
>>> Software Engineer
>>> Red Hat, Czech Republic
>>>
>>

[jira] [Updated] (DELTASPIKE-724) upgrade version of the tomee-arquillian adapter

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek updated DELTASPIKE-724:

Fix Version/s: (was: 1.5.1)
   1.5.2

> upgrade version of the tomee-arquillian adapter
> ---
>
> Key: DELTASPIKE-724
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-724
> Project: DeltaSpike
>  Issue Type: Task
>  Components: Build, Tests
>Reporter: Gerhard Petracek
>Assignee: Romain Manni-Bucau
> Fix For: 1.5.2
>
>
> to test against tomee 1.7.1



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

[jira] [Updated] (DELTASPIKE-978) ClassCastException with Native Queries

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek updated DELTASPIKE-978:

Fix Version/s: (was: 1.5.1)
   1.5.2

> ClassCastException with Native Queries
> --
>
> Key: DELTASPIKE-978
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-978
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Data-Module
>Affects Versions: 1.5.0
>Reporter: Amita Mehta
>Assignee: Thomas Hug
>Priority: Minor
> Fix For: 1.5.2
>
>
> Native Query does not return a correct result type of entity but returns an 
> object which causes ClassCastException
> details:
> http://mail-archives.apache.org/mod_mbox/deltaspike-dev/201508.mbox/%3C1438890740891-4661333.post%40n4.nabble.com%3E
> workaround:
> http://mail-archives.apache.org/mod_mbox/deltaspike-dev/201508.mbox/%3CCAJEn2S5FzMaSOavkOu36fmF8WOGSun%2BRTxDRziSFPvV1eWOGmQ%40mail.gmail.com%3E



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

[jira] [Updated] (DELTASPIKE-872) Support mocking on proxied beans

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek updated DELTASPIKE-872:

Fix Version/s: (was: 1.5.1)
   1.5.2

> Support mocking on proxied beans
> 
>
> Key: DELTASPIKE-872
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-872
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: TestControl
>Affects Versions: 1.3.0
>Reporter: Rafael
>Assignee: Thomas Andraschko
> Fix For: 1.5.2
>
>
> Currently test control mock feature is not supported on proxies (e.g: beans 
> with interceptors), a sample test which fails because of this limitation can 
> be found here: 
> https://github.com/rmpestano/ee6-ds-demo/blob/master/src/test/java/org/os890/demo/ee6/test/MockTest.java
>  
> .
>  



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

[jira] [Updated] (DELTASPIKE-813) improve basic core documentation

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek updated DELTASPIKE-813:

Fix Version/s: (was: 1.5.1)
   1.5.2

> improve basic core documentation
> 
>
> Key: DELTASPIKE-813
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-813
> Project: DeltaSpike
>  Issue Type: Task
>  Components: Documentation
>Affects Versions: 1.2.1
>Reporter: Gerhard Petracek
>Assignee: Rafael Benevides
> Fix For: 1.5.2
>
>
> in this first step we should improve everything which is marked red or yellow 
> in the documentation column and green or yellow in the "importance for 
> average users" column ( see 
> https://cwiki.apache.org/confluence/display/DeltaSpike/DS-Core+Overview )



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

[jira] [Updated] (DELTASPIKE-440) discuss helper for adding deployment-problems

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek updated DELTASPIKE-440:

Fix Version/s: (was: 1.5.1)
   1.5.2

> discuss helper for adding deployment-problems
> -
>
> Key: DELTASPIKE-440
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-440
> Project: DeltaSpike
>  Issue Type: Task
>  Components: Core
>Reporter: Gerhard Petracek
>Assignee: Rafael Benevides
> Fix For: 1.5.2
>
>
> in many cases it's possible to detect deployment-problems before 
> AfterDeploymentValidation. it's possible to throw an exception at any time, 
> however, it might be useful to unify it. e.g. collecting problems via a 
> helper which adds all issues via 
> AfterDeploymentValidation#addDeploymentProblem



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

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

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek updated DELTASPIKE-680:

Fix Version/s: (was: 1.5.1)
   1.5.2

> 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
> Fix For: 1.5.2
>
>
> 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
(v6.3.4#6332)

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

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek updated DELTASPIKE-645:

Fix Version/s: (was: 1.5.1)
   1.5.2

> 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
> Fix For: 1.5.2
>
>
> 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
(v6.3.4#6332)

[jira] [Updated] (DELTASPIKE-982) improve internal description of our release-steps

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek updated DELTASPIKE-982:

Fix Version/s: (was: 1.5.1)
   1.5.2

> improve internal description of our release-steps
> -
>
> Key: DELTASPIKE-982
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-982
> Project: DeltaSpike
>  Issue Type: Task
>  Components: Documentation
>Affects Versions: 1.5.0
>Reporter: Gerhard Petracek
>Assignee: Gerhard Petracek
>Priority: Minor
> Fix For: 1.5.2
>
>




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

[jira] [Resolved] (DELTASPIKE-983) Investigate issue with DeltaSpike Validation Module

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek resolved DELTASPIKE-983.
-
Resolution: Fixed

> Investigate issue with DeltaSpike Validation Module
> ---
>
> Key: DELTASPIKE-983
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-983
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: BeanValidation-Module
>Affects Versions: 1.5.0
>Reporter: Rafael Benevides
>Assignee: Rafael Benevides
> Fix For: 1.5.1
>
>
> Using BV with Java EE 7 libs causes the following exception:
> {code}
> Exception in thread "Thread-0" java.lang.AbstractMethodError: 
> org.apache.deltaspike.beanvalidation.impl.CDIAwareConstraintValidatorFactory.releaseInstance(Ljavax/validation/ConstraintValidator;)V
>  at 
> org.hibernate.validator.internal.engine.constraintvalidation.ConstraintValidatorManager.clear(ConstraintValidatorManager.java:201)
>  at 
> org.hibernate.validator.internal.engine.ValidatorFactoryImpl.close(ValidatorFactoryImpl.java:315)
>  at 
> org.hibernate.validator.internal.cdi.ValidatorFactoryBean.destroy(ValidatorFactoryBean.java:125)
>  at 
> org.hibernate.validator.internal.cdi.ValidatorFactoryBean.destroy(ValidatorFactoryBean.java:45)
>  at 
> org.jboss.weld.util.bean.IsolatedForwardingBean.destroy(IsolatedForwardingBean.java:50)
>  at 
> org.jboss.weld.context.AbstractContext.destroyContextualInstance(AbstractContext.java:147)
>  at org.jboss.weld.context.AbstractContext.destroy(AbstractContext.java:161) 
> at 
> org.jboss.weld.context.AbstractSharedContext.destroy(AbstractSharedContext.java:61)
>  at 
> org.jboss.weld.context.AbstractSharedContext.invalidate(AbstractSharedContext.java:56)
>  at org.jboss.weld.bootstrap.WeldRuntime.shutdown(WeldRuntime.java:54) at 
> org.jboss.weld.bootstrap.WeldBootstrap.shutdown(WeldBootstrap.java:113) at 
> org.jboss.weld.environment.se.ShutdownManager.shutdown(ShutdownManager.java:50)
>  at org.jboss.weld.environment.se.Weld.shutdown(Weld.java:259) at 
> org.jboss.weld.environment.se.StartMain$ShutdownHook.run(StartMain.java:84)
> {code}
> Example project: https://github.com/jpangamarca/bean-validation-shutdown-issue



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

[jira] [Resolved] (DELTASPIKE-992) optional support for bv 1.1

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek resolved DELTASPIKE-992.
-
Resolution: Fixed

> optional support for bv 1.1
> ---
>
> Key: DELTASPIKE-992
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-992
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: BeanValidation-Module
>Affects Versions: 1.5.0
>Reporter: Rafael Benevides
> Fix For: 1.5.1
>
>
> the bv module isn't needed for bv 1.1+, however, if an application needs to 
> get deployed to ee6 as well as ee7 servers there shouldn't be the need to 
> modify the application.



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

[jira] [Updated] (DELTASPIKE-983) Investigate issue with DeltaSpike Validation Module

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek updated DELTASPIKE-983:

Issue Type: Task  (was: Bug)

> Investigate issue with DeltaSpike Validation Module
> ---
>
> Key: DELTASPIKE-983
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-983
> Project: DeltaSpike
>  Issue Type: Task
>  Components: BeanValidation-Module
>Affects Versions: 1.5.0
>Reporter: Rafael Benevides
>Assignee: Rafael Benevides
> Fix For: 1.5.1
>
>
> Using BV with Java EE 7 libs causes the following exception:
> {code}
> Exception in thread "Thread-0" java.lang.AbstractMethodError: 
> org.apache.deltaspike.beanvalidation.impl.CDIAwareConstraintValidatorFactory.releaseInstance(Ljavax/validation/ConstraintValidator;)V
>  at 
> org.hibernate.validator.internal.engine.constraintvalidation.ConstraintValidatorManager.clear(ConstraintValidatorManager.java:201)
>  at 
> org.hibernate.validator.internal.engine.ValidatorFactoryImpl.close(ValidatorFactoryImpl.java:315)
>  at 
> org.hibernate.validator.internal.cdi.ValidatorFactoryBean.destroy(ValidatorFactoryBean.java:125)
>  at 
> org.hibernate.validator.internal.cdi.ValidatorFactoryBean.destroy(ValidatorFactoryBean.java:45)
>  at 
> org.jboss.weld.util.bean.IsolatedForwardingBean.destroy(IsolatedForwardingBean.java:50)
>  at 
> org.jboss.weld.context.AbstractContext.destroyContextualInstance(AbstractContext.java:147)
>  at org.jboss.weld.context.AbstractContext.destroy(AbstractContext.java:161) 
> at 
> org.jboss.weld.context.AbstractSharedContext.destroy(AbstractSharedContext.java:61)
>  at 
> org.jboss.weld.context.AbstractSharedContext.invalidate(AbstractSharedContext.java:56)
>  at org.jboss.weld.bootstrap.WeldRuntime.shutdown(WeldRuntime.java:54) at 
> org.jboss.weld.bootstrap.WeldBootstrap.shutdown(WeldBootstrap.java:113) at 
> org.jboss.weld.environment.se.ShutdownManager.shutdown(ShutdownManager.java:50)
>  at org.jboss.weld.environment.se.Weld.shutdown(Weld.java:259) at 
> org.jboss.weld.environment.se.StartMain$ShutdownHook.run(StartMain.java:84)
> {code}
> Example project: https://github.com/jpangamarca/bean-validation-shutdown-issue



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

[jira] [Created] (DELTASPIKE-992) optional support for bv 1.1

[Gerhard Petracek (JIRA)]

Gerhard Petracek created DELTASPIKE-992:
---

 Summary: optional support for bv 1.1
 Key: DELTASPIKE-992
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-992
 Project: DeltaSpike
  Issue Type: Improvement
  Components: BeanValidation-Module
Affects Versions: 1.5.0
Reporter: Rafael Benevides
 Fix For: 1.5.1






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

[jira] [Updated] (DELTASPIKE-992) optional support for bv 1.1

[Gerhard Petracek (JIRA)]

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

Gerhard Petracek updated DELTASPIKE-992:

Description: the bv module isn't needed for bv 1.1+, however, if an 
application needs to get deployed to ee6 as well as ee7 servers there shouldn't 
be the need to modify the application.

> optional support for bv 1.1
> ---
>
> Key: DELTASPIKE-992
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-992
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: BeanValidation-Module
>Affects Versions: 1.5.0
>Reporter: Rafael Benevides
> Fix For: 1.5.1
>
>
> the bv module isn't needed for bv 1.1+, however, if an application needs to 
> get deployed to ee6 as well as ee7 servers there shouldn't be the need to 
> modify the application.



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