[ https://issues.jboss.org/browse/AS7-735?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler commented on AS7-735: ------------------------------------ A bundle marked as .deployed reaches Bundle.INSTALLED state -- 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-735?page=com.atlassian.jira.plugin.sy... ] David Bosschaert commented on AS7-735: -------------------------------------- I think this is not intuitive, because you only really get to know whether there are any issues once the bundle is resolved. Just to compare with EE deployments. If there are any jboss-modules dependencies listed in an EJB-Jar these and these are missing in the deployment of that EJB-Jar is marked as failed - this is much more useful IMHO. -- 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-735?page=com.atlassian.jira.plugin.sy... ] David Bosschaert commented on AS7-735: -------------------------------------- I think that BundleA should fail its hot-deployment (which also includes starting), unless BundleB is also present. I do understand that EJB doesn't have the same states as OSGi, but from a user's perspective I think if a bundle fails to resolve the deployment should be marked as failed. This might be hard to do, but from a user's perspective it's consistent with the behaviour of JavaEE deployments. -- 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-735?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler edited comment on AS7-735 at 5/12/11 3:54 AM: ------------------------------------------------------------- This would create a notion of correct bundle install order, which the client would have to resolve. For trivial cases like B before A this would be doable. However, we generally want to avoid that sort of ordering requirement. For a complex dependency graph it is nearly certain to fail. Have a look at AS7-378 and its associated forum entries. What you are probably looking for is a set of one deployment, with a requirement that all deployments in the set (i.e. just the one) can be started after all deployments in the set have been installed. was (Author: thomas.diesler): This would create a notion of correct bundle install order, which the client would have to resolve. For trivial cases like B before A this would be doable. However, we generally want to avoid that sort of ordering requirement. Have a look at AS7-378 and its associated forum entries. What you are probably looking for is a set of one deployment, with a requirement that all deployments in the set (i.e. just the one) can be started after all deployments in the set have been installed. -- 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-735?page=com.atlassian.jira.plugin.sy... ] Jason Greene updated AS7-735: ----------------------------- Assignee: (was: Jason Greene) -- 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-735?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler updated AS7-735: ------------------------------- Fix Version/s: (was: 7.1.0.Alpha1) -- 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-735?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler updated AS7-735: ------------------------------- Fix Version/s: 7.2.0.Alpha1 Please revisit and take an action. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-735?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler resolved AS7-735. -------------------------------- Fix Version/s: (was: 7.2.0.CR1) Resolution: Out of Date Out of Date -- 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