[jira] [Resolved] (DELTASPIKE-862) document JsfMessage
[ https://issues.apache.org/jira/browse/DELTASPIKE-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael Benevides resolved DELTASPIKE-862. - Resolution: Fixed Published: http://deltaspike.apache.org/documentation/jsf.html#_jsf_messages > document JsfMessage > --- > > Key: DELTASPIKE-862 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-862 > Project: DeltaSpike > Issue Type: Task > Components: JSF-Module >Affects Versions: 1.3.0 >Reporter: Gerhard Petracek >Assignee: Rafael Benevides > Fix For: 1.3.1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-867) Clarify that Test-Control module has manual dependencies on CDI implementations
[ https://issues.apache.org/jira/browse/DELTASPIKE-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393016#comment-14393016 ] Ron Smeral commented on DELTASPIKE-867: --- https://github.com/apache/deltaspike/pull/25 > Clarify that Test-Control module has manual dependencies on CDI > implementations > --- > > Key: DELTASPIKE-867 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-867 > Project: DeltaSpike > Issue Type: Bug > Components: Documentation >Reporter: Ron Smeral >Priority: Minor > > It is kind of obvious, but it may be easier for beginners to start with > DeltaSpike Test-Control module if this is mentioned - that openwebbeans-impl > or weld-se-core needs to be added as a dependency manually. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DELTASPIKE-867) Clarify that Test-Control module has manual dependencies on CDI implementations
Ron Smeral created DELTASPIKE-867: - Summary: Clarify that Test-Control module has manual dependencies on CDI implementations Key: DELTASPIKE-867 URL: https://issues.apache.org/jira/browse/DELTASPIKE-867 Project: DeltaSpike Issue Type: Bug Components: Documentation Reporter: Ron Smeral Priority: Minor It is kind of obvious, but it may be easier for beginners to start with DeltaSpike Test-Control module if this is mentioned - that openwebbeans-impl or weld-se-core needs to be added as a dependency manually. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-228) Make @MessageBundle annotated type available via EL
[
https://issues.apache.org/jira/browse/DELTASPIKE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392771#comment-14392771
]
Ron Smeral commented on DELTASPIKE-228:
---
A bean annotated just {{@Named @MessageBundle}} doesn't get discovered in the
"annotated" mode, since neither @Named nor @MessageBundle is bean-defining
annotation:
http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#bean_defining_annotations
As per CDI 1.1, 12.4, only beans with bean-defining annotations are discovered
in archives with "annotated" mode:
http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#bean_discovery
You could solve it by annotating your message bean e.g. @Dependent,
@ApplicationScoped, etc.
This _could_ be added to docs, but I'm not sure it makes sense for it to be
there, since this is governed by the CDI spec.
Though, as you say, it could be there as a hint, just as in the "Type-safe
View-Configs" section. Feel free to make a Documentation JIRA and issue a PR
against github.com/apache/deltaspike.
> Make @MessageBundle annotated type available via EL
>
>
> Key: DELTASPIKE-228
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-228
> Project: DeltaSpike
> Issue Type: New Feature
> Components: I18n-Module, JSF-Module
>Affects Versions: 0.2-incubating
>Reporter: Thomas Herzog
>Assignee: Rafael Benevides
>
> After you defined an MessageBundle type, you wanna use it in the views as
> well without wrapping the type into a @Named annotated cdi bean to be
> available to use it via EL.
> It would be fine if the implementation would be created and registrered as an
> cdi bean at deployment time and therefore available via EL in the views.
> I think the main usage for the messages is in the views, at least in our
> usacases.
> Therefore it would also nice to define the name of the created cdi bean via
> maybe @MessageContextConfig annotation and default should be the name of the
> type, but the name of the type could be same, just placed in different
> packages.
> If this will be done the developer only has to define his MessageBundle type
> with the getter for the messages and configuration via annotation if
> necessary, and use it in the views right away.
> Regarding to issue DELTASPIKE-223 it would be necessary to think about
> follwing possible issues.
> If there would be multiple choices for the convention of the getter methods
> for the messages defined in the MessageBundle type, there could occur
> follwing problems.
> 1. String welcomeTo(); // Key: welcome_to
> 2. String getWelcomeTo(); // Key: welcome_to with get prefix
> 3 String getWelcomeTo(); // Key: get_welcome_to
> @1
> How will EL resolve the method if called via #{type.welcomeTo} ?
> As far as i know EL would try to invoke getWelcomeTo() method which could not
> be found in this case !!
> @2 and 3
> How will it be distiguished if get prefix is part of the key or just the
> start of the getter method?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-228) Make @MessageBundle annotated type available via EL
[
https://issues.apache.org/jira/browse/DELTASPIKE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392731#comment-14392731
]
John Schneider commented on DELTASPIKE-228:
---
I got it working in 1.3.1-SNAPSHOT by changing bean discovery-mode from
"annotated" to "all". I'm not sure why this is required as I had explicitly
used "@Named" and "@MessageBundle". Is this the expected behaviour? If so,
then I request a documentation update to reflect this requirement, similar to
the "Bean-discovery-mode Annotated" subsection within the "Type-safe
View-Configs" section.
> Make @MessageBundle annotated type available via EL
>
>
> Key: DELTASPIKE-228
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-228
> Project: DeltaSpike
> Issue Type: New Feature
> Components: I18n-Module, JSF-Module
>Affects Versions: 0.2-incubating
>Reporter: Thomas Herzog
>Assignee: Rafael Benevides
>
> After you defined an MessageBundle type, you wanna use it in the views as
> well without wrapping the type into a @Named annotated cdi bean to be
> available to use it via EL.
> It would be fine if the implementation would be created and registrered as an
> cdi bean at deployment time and therefore available via EL in the views.
> I think the main usage for the messages is in the views, at least in our
> usacases.
> Therefore it would also nice to define the name of the created cdi bean via
> maybe @MessageContextConfig annotation and default should be the name of the
> type, but the name of the type could be same, just placed in different
> packages.
> If this will be done the developer only has to define his MessageBundle type
> with the getter for the messages and configuration via annotation if
> necessary, and use it in the views right away.
> Regarding to issue DELTASPIKE-223 it would be necessary to think about
> follwing possible issues.
> If there would be multiple choices for the convention of the getter methods
> for the messages defined in the MessageBundle type, there could occur
> follwing problems.
> 1. String welcomeTo(); // Key: welcome_to
> 2. String getWelcomeTo(); // Key: welcome_to with get prefix
> 3 String getWelcomeTo(); // Key: get_welcome_to
> @1
> How will EL resolve the method if called via #{type.welcomeTo} ?
> As far as i know EL would try to invoke getWelcomeTo() method which could not
> be found in this case !!
> @2 and 3
> How will it be distiguished if get prefix is part of the key or just the
> start of the getter method?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Problem with Deltaspike and Quartz integration
Hi Ron,
adding
org.apache.deltaspike.cdictrl
deltaspike-cdictrl-weld
${deltaspike.version}
compile
solved my problem.
Thank you very much.
Flo
Am 02.04.2015 um 14:34 schrieb Ron Smeral :
> Hi Florian,
>
> is your EntityManager request-scoped? If so, you need to either start the
> request scope through "startScopes", or re-scope your EM.
>
> As to the first issue, did you include an implementation of ContainerControl
> in your project? This is not yet documented, but you need to have a runtime
> dependency on e.g. org.apache.deltaspike.cdictrl: deltaspike-cdictrl-weld if
> you use Weld (and similarly for other CDI impls) anytime you use the
> Scheduler module.
>
> Also, I think this belongs to us...@deltaspike.apache.org :)
>
> Regards,
> Ron
>
> On 2.4.2015 14:09, Florian Limpöck wrote:
>> Hello Deltaspike Team,
>>
>> I try to make a scheduled send mail application, for a monthly reminder.
>>
>> My Code looks like this and it works until the point i try to use my
>> Injection.
>>
>> @Scheduled(cronExpression = "0 0/1 * * * ?")
>> public class SimpleJob implements Job {
>>
>> @Inject
>> ProjektRepository projektRepository;
>>
>> @Override
>> public void execute(JobExecutionContext context) throws
>> JobExecutionException {
>> System.out.println("Test");
>>
>> List projektList = projektRepository.getAll();
>>
>> System.out.println(projektList.get(0).getName());
>> }
>> }
>>
>>
>> I get the following Error:
>>
>> 11:14:00,008 ERROR [org.quartz.core.ErrorLogger]
>> (DefaultQuartzScheduler_Worker-1) Unable to notify JobListener(s) of Job to
>> be executed: (Job will NOT be executed!). trigger=
>> DEFAULT.6da64b5bd2ee-cac2ad65-b6c9-4cfa-8402-6b5ccc8a1467 job=
>> DEFAULT.SimpleJob: org.quartz.SchedulerException: JobListener
>> 'org.apache.deltaspike.scheduler.impl.QuartzScheduler$InjectionAwareJobListener'
>> threw exception: Could not find beans for Type=interface
>> org.apache.deltaspike.cdise.api.ContextControl and qualifiers:[] [See nested
>> exception: java.lang.IllegalStateException: Could not find beans for
>> Type=interface org.apache.deltaspike.cdise.api.ContextControl and
>> qualifiers:[]]
>> at
>> org.quartz.core.QuartzScheduler.notifyJobListenersToBeExecuted(QuartzScheduler.java:1947)
>> [quartz-2.2.1.jar:]
>> at
>> org.quartz.core.JobRunShell.notifyListenersBeginning(JobRunShell.java:324)
>> [quartz-2.2.1.jar:]
>> at org.quartz.core.JobRunShell.run(JobRunShell.java:173)
>> [quartz-2.2.1.jar:]
>> at
>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)
>> [quartz-2.2.1.jar:]
>> Caused by: java.lang.IllegalStateException: Could not find beans for
>> Type=interface org.apache.deltaspike.cdise.api.ContextControl and
>> qualifiers:[]
>> at
>> org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:150)
>> [deltaspike-core-api-1.0.1.jar:1.0.1]
>> at
>> org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:119)
>> [deltaspike-core-api-1.0.1.jar:1.0.1]
>> at
>> org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:100)
>> [deltaspike-core-api-1.0.1.jar:1.0.1]
>> at
>> org.apache.deltaspike.scheduler.impl.QuartzScheduler$JobListenerContext.startContexts(QuartzScheduler.java:427)
>> [deltaspike-scheduler-module-impl-1.0.1.jar:1.0.1]
>> at
>> org.apache.deltaspike.scheduler.impl.QuartzScheduler$InjectionAwareJobListener.jobToBeExecuted(QuartzScheduler.java:372)
>> [deltaspike-scheduler-module-impl-1.0.1.jar:1.0.1]
>> at
>> org.quartz.core.QuartzScheduler.notifyJobListenersToBeExecuted(QuartzScheduler.java:1945)
>> [quartz-2.2.1.jar:]
>> ... 3 more
>>
>>
>> I try to add startScopes={} because of this ticket
>> https://issues.apache.org/jira/browse/DELTASPIKE-656, then the job is
>> executed, but then I got this exception.
>>
>>
>> 11:10:00,001 INFO [stdout] (DefaultQuartzScheduler_Worker-6) Test
>> 11:10:00,003 ERROR [org.quartz.core.JobRunShell]
>> (DefaultQuartzScheduler_Worker-4) Job DEFAULT.SimpleJob threw an unhandled
>> Exception: : org.jboss.weld.context.ContextNotActiveException: WELD-001303:
>> No active contexts for scope type javax.enterprise.context.RequestScoped
>> at
>> org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:680)
>> [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
>> at
>> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:79)
>> [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
>> at
>> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:99)
>> [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
>> at
>> org.jboss.weld.proxies.EntityManager$1197393252$Proxy$_$$_WeldClientProxy.getCriteriaBuilder(Unknown
>> Source) [weld-core-
[jira] [Commented] (DELTASPIKE-228) Make @MessageBundle annotated type available via EL
[
https://issues.apache.org/jira/browse/DELTASPIKE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392637#comment-14392637
]
Ron Smeral commented on DELTASPIKE-228:
---
[~JohnSchneider] I tried reproducing the simple scenario, this works for me
with all DS versions from 0.6 to 1.2.1, is broken in 1.3.0 due to
DELTASPIKE-859, and works again with 1.3.1-SNAPSHOT:
{code}
@Named @MessageBundle
public interface Msg {
@MessageTemplate("{hello}")
String hello();
}
{code}
{code}
Named MessageBundle through EL:
{code}
> Make @MessageBundle annotated type available via EL
>
>
> Key: DELTASPIKE-228
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-228
> Project: DeltaSpike
> Issue Type: New Feature
> Components: I18n-Module, JSF-Module
>Affects Versions: 0.2-incubating
>Reporter: Thomas Herzog
>Assignee: Rafael Benevides
>
> After you defined an MessageBundle type, you wanna use it in the views as
> well without wrapping the type into a @Named annotated cdi bean to be
> available to use it via EL.
> It would be fine if the implementation would be created and registrered as an
> cdi bean at deployment time and therefore available via EL in the views.
> I think the main usage for the messages is in the views, at least in our
> usacases.
> Therefore it would also nice to define the name of the created cdi bean via
> maybe @MessageContextConfig annotation and default should be the name of the
> type, but the name of the type could be same, just placed in different
> packages.
> If this will be done the developer only has to define his MessageBundle type
> with the getter for the messages and configuration via annotation if
> necessary, and use it in the views right away.
> Regarding to issue DELTASPIKE-223 it would be necessary to think about
> follwing possible issues.
> If there would be multiple choices for the convention of the getter methods
> for the messages defined in the MessageBundle type, there could occur
> follwing problems.
> 1. String welcomeTo(); // Key: welcome_to
> 2. String getWelcomeTo(); // Key: welcome_to with get prefix
> 3 String getWelcomeTo(); // Key: get_welcome_to
> @1
> How will EL resolve the method if called via #{type.welcomeTo} ?
> As far as i know EL would try to invoke getWelcomeTo() method which could not
> be found in this case !!
> @2 and 3
> How will it be distiguished if get prefix is part of the key or just the
> start of the getter method?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Problem with Deltaspike and Quartz integration
Hi Florian,
is your EntityManager request-scoped? If so, you need to either start
the request scope through "startScopes", or re-scope your EM.
As to the first issue, did you include an implementation of
ContainerControl in your project? This is not yet documented, but you
need to have a runtime dependency on e.g. org.apache.deltaspike.cdictrl:
deltaspike-cdictrl-weld if you use Weld (and similarly for other CDI
impls) anytime you use the Scheduler module.
Also, I think this belongs to us...@deltaspike.apache.org :)
Regards,
Ron
On 2.4.2015 14:09, Florian Limpöck wrote:
Hello Deltaspike Team,
I try to make a scheduled send mail application, for a monthly reminder.
My Code looks like this and it works until the point i try to use my Injection.
@Scheduled(cronExpression = "0 0/1 * * * ?")
public class SimpleJob implements Job {
@Inject
ProjektRepository projektRepository;
@Override
public void execute(JobExecutionContext context) throws
JobExecutionException {
System.out.println("Test");
List projektList = projektRepository.getAll();
System.out.println(projektList.get(0).getName());
}
}
I get the following Error:
11:14:00,008 ERROR [org.quartz.core.ErrorLogger]
(DefaultQuartzScheduler_Worker-1) Unable to notify JobListener(s) of Job to be
executed: (Job will NOT be executed!). trigger=
DEFAULT.6da64b5bd2ee-cac2ad65-b6c9-4cfa-8402-6b5ccc8a1467 job=
DEFAULT.SimpleJob: org.quartz.SchedulerException: JobListener
'org.apache.deltaspike.scheduler.impl.QuartzScheduler$InjectionAwareJobListener'
threw exception: Could not find beans for Type=interface
org.apache.deltaspike.cdise.api.ContextControl and qualifiers:[] [See nested
exception: java.lang.IllegalStateException: Could not find beans for
Type=interface org.apache.deltaspike.cdise.api.ContextControl and qualifiers:[]]
at
org.quartz.core.QuartzScheduler.notifyJobListenersToBeExecuted(QuartzScheduler.java:1947)
[quartz-2.2.1.jar:]
at
org.quartz.core.JobRunShell.notifyListenersBeginning(JobRunShell.java:324)
[quartz-2.2.1.jar:]
at org.quartz.core.JobRunShell.run(JobRunShell.java:173)
[quartz-2.2.1.jar:]
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)
[quartz-2.2.1.jar:]
Caused by: java.lang.IllegalStateException: Could not find beans for
Type=interface org.apache.deltaspike.cdise.api.ContextControl and qualifiers:[]
at
org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:150)
[deltaspike-core-api-1.0.1.jar:1.0.1]
at
org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:119)
[deltaspike-core-api-1.0.1.jar:1.0.1]
at
org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:100)
[deltaspike-core-api-1.0.1.jar:1.0.1]
at
org.apache.deltaspike.scheduler.impl.QuartzScheduler$JobListenerContext.startContexts(QuartzScheduler.java:427)
[deltaspike-scheduler-module-impl-1.0.1.jar:1.0.1]
at
org.apache.deltaspike.scheduler.impl.QuartzScheduler$InjectionAwareJobListener.jobToBeExecuted(QuartzScheduler.java:372)
[deltaspike-scheduler-module-impl-1.0.1.jar:1.0.1]
at
org.quartz.core.QuartzScheduler.notifyJobListenersToBeExecuted(QuartzScheduler.java:1945)
[quartz-2.2.1.jar:]
... 3 more
I try to add startScopes={} because of this ticket
https://issues.apache.org/jira/browse/DELTASPIKE-656, then the job is executed,
but then I got this exception.
11:10:00,001 INFO [stdout] (DefaultQuartzScheduler_Worker-6) Test
11:10:00,003 ERROR [org.quartz.core.JobRunShell]
(DefaultQuartzScheduler_Worker-4) Job DEFAULT.SimpleJob threw an unhandled
Exception: : org.jboss.weld.context.ContextNotActiveException: WELD-001303: No
active contexts for scope type javax.enterprise.context.RequestScoped
at
org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:680)
[weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
at
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:79)
[weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
at
org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:99)
[weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
at
org.jboss.weld.proxies.EntityManager$1197393252$Proxy$_$$_WeldClientProxy.getCriteriaBuilder(Unknown
Source) [weld-core-impl-2.1.2.Final.jar:]
at
com.xy.repository.AbstractRepository.getAll(AbstractRepository.java:75)
[classes:]
at com.xy.quartz.SimpleJob.execute(SimpleJob.java:28) [classes:]
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
[quartz-2.2.1.jar:]
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)
[quartz-2.2.1.jar:]
11:10:00,004 ERROR [org.quartz.core.ErrorLogger]
(DefaultQuartzScheduler_Worker-4) Job (DEFAULT.SimpleJob threw an excep
Problem with Deltaspike and Quartz integration
Hello Deltaspike Team,
I try to make a scheduled send mail application, for a monthly reminder.
My Code looks like this and it works until the point i try to use my Injection.
@Scheduled(cronExpression = "0 0/1 * * * ?")
public class SimpleJob implements Job {
@Inject
ProjektRepository projektRepository;
@Override
public void execute(JobExecutionContext context) throws
JobExecutionException {
System.out.println("Test");
List projektList = projektRepository.getAll();
System.out.println(projektList.get(0).getName());
}
}
I get the following Error:
11:14:00,008 ERROR [org.quartz.core.ErrorLogger]
(DefaultQuartzScheduler_Worker-1) Unable to notify JobListener(s) of Job to be
executed: (Job will NOT be executed!). trigger=
DEFAULT.6da64b5bd2ee-cac2ad65-b6c9-4cfa-8402-6b5ccc8a1467 job=
DEFAULT.SimpleJob: org.quartz.SchedulerException: JobListener
'org.apache.deltaspike.scheduler.impl.QuartzScheduler$InjectionAwareJobListener'
threw exception: Could not find beans for Type=interface
org.apache.deltaspike.cdise.api.ContextControl and qualifiers:[] [See nested
exception: java.lang.IllegalStateException: Could not find beans for
Type=interface org.apache.deltaspike.cdise.api.ContextControl and qualifiers:[]]
at
org.quartz.core.QuartzScheduler.notifyJobListenersToBeExecuted(QuartzScheduler.java:1947)
[quartz-2.2.1.jar:]
at
org.quartz.core.JobRunShell.notifyListenersBeginning(JobRunShell.java:324)
[quartz-2.2.1.jar:]
at org.quartz.core.JobRunShell.run(JobRunShell.java:173)
[quartz-2.2.1.jar:]
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)
[quartz-2.2.1.jar:]
Caused by: java.lang.IllegalStateException: Could not find beans for
Type=interface org.apache.deltaspike.cdise.api.ContextControl and qualifiers:[]
at
org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:150)
[deltaspike-core-api-1.0.1.jar:1.0.1]
at
org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:119)
[deltaspike-core-api-1.0.1.jar:1.0.1]
at
org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:100)
[deltaspike-core-api-1.0.1.jar:1.0.1]
at
org.apache.deltaspike.scheduler.impl.QuartzScheduler$JobListenerContext.startContexts(QuartzScheduler.java:427)
[deltaspike-scheduler-module-impl-1.0.1.jar:1.0.1]
at
org.apache.deltaspike.scheduler.impl.QuartzScheduler$InjectionAwareJobListener.jobToBeExecuted(QuartzScheduler.java:372)
[deltaspike-scheduler-module-impl-1.0.1.jar:1.0.1]
at
org.quartz.core.QuartzScheduler.notifyJobListenersToBeExecuted(QuartzScheduler.java:1945)
[quartz-2.2.1.jar:]
... 3 more
I try to add startScopes={} because of this ticket
https://issues.apache.org/jira/browse/DELTASPIKE-656, then the job is executed,
but then I got this exception.
11:10:00,001 INFO [stdout] (DefaultQuartzScheduler_Worker-6) Test
11:10:00,003 ERROR [org.quartz.core.JobRunShell]
(DefaultQuartzScheduler_Worker-4) Job DEFAULT.SimpleJob threw an unhandled
Exception: : org.jboss.weld.context.ContextNotActiveException: WELD-001303: No
active contexts for scope type javax.enterprise.context.RequestScoped
at
org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:680)
[weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
at
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:79)
[weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
at
org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:99)
[weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
at
org.jboss.weld.proxies.EntityManager$1197393252$Proxy$_$$_WeldClientProxy.getCriteriaBuilder(Unknown
Source) [weld-core-impl-2.1.2.Final.jar:]
at
com.xy.repository.AbstractRepository.getAll(AbstractRepository.java:75)
[classes:]
at com.xy.quartz.SimpleJob.execute(SimpleJob.java:28) [classes:]
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
[quartz-2.2.1.jar:]
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)
[quartz-2.2.1.jar:]
11:10:00,004 ERROR [org.quartz.core.ErrorLogger]
(DefaultQuartzScheduler_Worker-4) Job (DEFAULT.SimpleJob threw an exception.:
org.quartz.SchedulerException: Job threw an unhandled exception. [See nested
exception: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No
active contexts for scope type javax.enterprise.context.RequestScoped]
at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
[quartz-2.2.1.jar:]
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)
[quartz-2.2.1.jar:]
Caused by: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No
active contexts for scope type javax.enterprise.context.RequestScoped
at
org.jbo
