[
https://issues.jboss.org/browse/JBSEAM-5072?page=com.atlassian.jira.plugi...
]
RH Bugzilla Integration commented on JBSEAM-5072:
-------------------------------------------------
Luan Cestari <lcestari(a)redhat.com> made a comment on [bug
904174|https://bugzilla.redhat.com/show_bug.cgi?id=904174]
Hi Marek,
In InitilizeTimers class he used Seam API to find or create the timers (
Component.getInstance(nme, true, true)). About using the JNDI, I remember that we tried
but it didn`t work as well. I Also talked with a guy from SEG that confirmed about TCCL.
Regards,
Luan
Issue with TCCL which is causing the Quartz thread to not have access
to the application's "java:app" context
--------------------------------------------------------------------------------------------------------------
Key: JBSEAM-5072
URL:
https://issues.jboss.org/browse/JBSEAM-5072
Project: Seam 2
Issue Type: Bug
Components: Core
Affects Versions: 2.2.0.GA, 2.2.1.Final, 2.2.2.Final
Reporter: Luan Cestari
Description of problem:
Issue with TCCL which is causing the Quartz thread to not have access to the
application's "java:app" context. In other words, Seam can`t find the beans
in context, even that they are there (due the annotations and logs that confirm that).
EAP 6`s documentation that gives the steps to migrate Seam 2 applications:
https://access.redhat.com/knowledge/docs/en-US/JBoss_Enterprise_Applicati...
Version-Release number of selected component (if applicable):
Seam 2.2 in EAP 6
How reproducible:
Just create a Seam and Quartz bean and another Seam and EJB bean that on Startup will
lookup for Seam/Quartz bean, but can`t find it.
Actual results:
Can`t find the bean
Expected results:
Find the bean
Additional info:
salesforce link:
https://c.na7.visual.force.com/apex/Case_View?id=500A000000CQzrg&sfdc...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira