| Summary: | Can we rewrite Skynet to avoid use of timer service? | ||
|---|---|---|---|
| Product: | [Community] PressGang CCMS | Reporter: | sgilda |
| Component: | Web-UI | Assignee: | sgilda |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.x | CC: | jwulf, topic-tool-list |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-06-29 04:01:34 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Skynet should use only Web Profile of EE6 so that it can port to AS7. SkyNet itself does not call the timer service directly, so this must be seam that is making the call. Good question Sande, and no doubt one that our customers will be asking. Let us know what you find out, re: what's provided by Web Profile of EE 6, and what Skynet requires. Maybe it is possible to recode it within that subset of functionality. I spoke with Jaikiran and Stuart Douglas this morning. Jaikiran is working on a fix to get past the deployment error, however, it will not fix any runtime errors related to use of the timer service in AS7. The theory is that Seam 2.x was was one big JAR including everything, whether it was used or not. If Skynet does not issue any calls to the timer service, the hope is that the application will not experience any runtime errors related to this service. Jaikiran is going to check in a fix later today and I will pull down the change, test it, and note the results here. I modified the AS7 deploy code to report but ignore the above deployment error and was able to get a little farther. It doesn't appear that we will have to modify the application to remove any timer service calls. I will wait until Jaikiran checks in his changes to verify it. |
When I deploy TopicIndex.war to AS7, I get the following error: Encountered a DeploymentUnitProcessingException "Can't handle @Resource for ENC name" during deployment. Log trace: Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Can't handle @Resource for ENC name: org.jboss.seam.async.TimerServiceDispatcher/timerService since it's missing a "lookup" (or "mappedName") value and isn't of any known type at org.jboss.as.ee.component.ResourceInjectionAnnotationParsingProcessor.process(ResourceInjectionAnnotationParsingProcessor.java:221) According to Stuart Douglas, the timer service is out of scope for AS7.0. It is not required by the web profile so will not be implemented until 7.1 which will have the full implementation. If we want to port Skynet to AS7, we need to remove the timer service.