[ https://issues.jboss.org/browse/AS7-796?page=com.atlassian.jira.plugin.sy... ] Jason Greene updated AS7-796: ----------------------------- Description: If an EE deployment, or JDBC driver happens to include osgi metadata, it will no longer deploy. This is because the OSGi subsystem bypasses other deployers, and treats it as just a bundle. Both Mysql and Hypersonic can not be deployed due to this problem. Ideally the OSGi subsystem would just add services and augment the module configs so that other deployers can function. Alternatively we can explore the possibility of deploying bundles differently than regular deployments, perhaps requiring special packaging, or extra deployment data. If we can't come up with a solution by CR1, I think we need to disable the OSGi subsystem by default. was: If an EE deployment, or JDBC driver happens to include osgi metadata, it will no longer deploy. This is because the OSGi subsystem bypasses other deployers, and treats it as just a bundle. Both Mysql and Hypersonic can not be deployed due to this problem. Ideally the OSGi subsystem would just add services and augment the model configs so that other deployers can function. Alternatively we can explore the possibility of deploying bundles differently than regular deployments, perhaps requiring special packaging, or extra deployment data. If we can't come up with a solution by CR1, I think we need to disable the OSGi subsystem by default. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-796?page=com.atlassian.jira.plugin.sy... ] Jason Greene updated AS7-796: ----------------------------- Description: If an EE deployment, or JDBC driver happens to include osgi metadata, it will no longer deploy. This is because the OSGi subsystem bypasses other deployers, and treats it as just a bundle. Both Mysql and Hypersonic can not be deployed due to this problem. Ideally the OSGi subsystem would just add services and augment the model configs so that other deployers can function. Alternatively we can explore the possibility of deploying bundles differently than regular deployments, perhaps requiring special packaging, or extra deployment data. If we can't come up with a solution by CR1, I think we need to disable the OSGi subsystem by default. was: If an EE, or JDBC driver happens to include osgi metadata, it will no longer deploy. This is because the OSGi subsystem bypasses other deployers, and treats it as just a bundle. Both Mysql and Hypersonic can not be deployed due to this problem. Ideally the OSGi subsystem would just add services and augment the model configs so that other deployers can function. Alternatively we can explore the possibility of deploying bundles differently than regular deployments, perhaps requiring special packaging, or extra deployment data. If we can't come up with a solution by CR1, I think we need to disable the OSGi subsystem by default. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-796?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler commented on AS7-796: ------------------------------------ If a deployment contains OSGi metadata it is a Bundle and should be treated as such. We generally have the ability to create a dependency on a Bundle from an EE deployment. Of course, both MySQL and Hypersonic should deploy and be usable. What is the specific issue? I can check if it is still there in https://github.com/tdiesler/jboss-as/tree/as722. That branch is the one that should go into CR1. The module dependencies are generated from the resolution result that the OSGi resolver comes up with. The packaging of OSGi bundles is well defined. I don't think we need to come up with anything extra here. Instead, other deployments should be aware that they have a dependency on an OSGi bundle e.g. {code} Dependency: deployment.some-symbolic-name:1.0.0 {code} For EJB3 I show this here (https://github.com/tdiesler/jboss-as/commit/e462a4d85043) and for WebApps here (https://github.com/tdiesler/jboss-as/commit/e3cb658a0a9e56) Please show me how to reproduce this and what error I should expect. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-796?page=com.atlassian.jira.plugin.sy... ] Jason Greene closed AS7-796. ---------------------------- Resolution: Done -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira