| Summary: | Allow multiple Actions to share a single Spring Context | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | csams |
| Component: | Deployment | Assignee: | Ken Johnson <kejohnso> |
| Status: | NEW --- | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.1.0 GA | CC: | csams |
| Target Milestone: | --- | ||
| Target Release: | FUTURE | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-3151 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Feature Request | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
csams
2011-07-05 20:06:10 UTC
The idea here I think would be to create the spring application context(s) and bind them to JNDI so the action instances can look them up on initialization. This can be done with the spring deployer from WFK/Snowdrop, but it should be a straightforward alternative to write an MBean to fulfill the requirement without bringing that in. |