[
https://issues.jboss.org/browse/JBOSGI-590?page=com.atlassian.jira.plugin...
]
Thomas Diesler moved AS7-5454 to JBOSGI-590:
--------------------------------------------
Project: JBoss OSGi (was: Application Server 7)
Key: JBOSGI-590 (was: AS7-5454)
Workflow: jira (was: GIT Pull Request workflow )
Component/s: (was: OSGi)
Security: Public
Fix Version/s: JBossOSGi 1.2.0
(was: 7.2.0.CR1)
Allow EE deployments as OSGi bundles
------------------------------------
Key: JBOSGI-590
URL:
https://issues.jboss.org/browse/JBOSGI-590
Project: JBoss OSGi
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Fix For: JBossOSGi 1.2.0
This essentially means that you can put OSGi metadata into an EE deployment manifest,
which essentially makes it an OSGi bundle.
Deployment unit processing should be such that the EE bundle gets resolved according to
it's defined capabilities/requirements. Subsystem processors should not need to care
whether the Module was created as a result of OSGi resolution or by the
ModuleSpecProcessor.
This task is complete when we can do this with the EE core technologies (i.e. webapp,
ejb3, cdi)
--
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