[
https://issues.jboss.org/browse/AS7-5951?page=com.atlassian.jira.plugin.s...
]
Paul Illingworth edited comment on AS7-5951 at 11/20/12 10:09 AM:
------------------------------------------------------------------
"this_one_failed.txt" attachment is a trace of the startup when the fragments do
not attach (according to the felix web console). There is also a JBAS011910: Cannot
resolve requirements WARN at the end.
"this_one_worked.txt" attachment is a trace of the startup when the fragments
did attach.
was (Author: pillingworth):
"this_one_failed.txt" attachment is a trace of the startup when the
fragments do not attach (according to the felix web console). There is also a JBAS011910:
Cannot resolve requirements WARN at the end.
Cannot reliably deploy OSGi host and fragment bundles on server
restart
-----------------------------------------------------------------------
Key: AS7-5951
URL:
https://issues.jboss.org/browse/AS7-5951
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.2.0.Alpha1
Environment: Windows XP SP3
Reporter: Paul Illingworth
Assignee: Thomas Diesler
Labels: OSGI
Fix For: 7.2.0.Alpha1
Attachments: this_one_failed.txt, this_one_worked.txt
If I deploy guice-3.0.0 (host bundle), guice-servlet (fragment) and guice-persist
(fragment) into the "deployments" folder then the there is no guarantee the
fragments will be installed before the host and so they may not be attached to the host
when it resolves.
This happens on starting the application server. Sometimes the fragments are attached,
sometimes they aren't.
If I install the bundles into the "bundles" folder structure and add capability
entries to the standalone.xml file then it works as expected.
I am using 7.2.0-Alpha1 built from cb72a7cd1669131b28a552f1dbf3c2582ad19813.
--
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