[
https://issues.jboss.org/browse/AS7-4324?page=com.atlassian.jira.plugin.s...
]
Aaron Whiteside commented on AS7-4324:
--------------------------------------
I think I am still seeing this issue because I am deploying a large amount of bundles and
the deployment scanner is executing halfway through my # cp *.jar deployments/ command so
it only sees half the bundles, then it executes again and sees the other half but nothing
resolves correctly... because that is treated as two different deployment batches?
Apache Felix provides an auto-deploy feature where it monitors a directory for changes and
enacts these changes. If there are unresolved bundles present and a new bundle is
installed that provides the necessary packages it will automatically refresh those
dependent bundles.
It may not be required by the specification, but it's actually really handy for
development. If JBoss won't support this feature how am I to successfully deploy large
batches of bundles?
Batch deployment of bundles
---------------------------
Key: AS7-4324
URL:
https://issues.jboss.org/browse/AS7-4324
Project: Application Server 7
Issue Type: Feature Request
Components: OSGi
Affects Versions: 7.1.1.Final
Environment: Mac OS X 10.7.3
Reporter: Tim Diekmann
Assignee: Thomas Diesler
Fix For: 7.1.2.Final (EAP)
It has to be possible to deploy a large set of bundles at the same time without
triggering the resolution of each bundle individually.
Currently, if you deploy multiple bundles either through CLI or via the hot deployment
folder the deployer processes each bundle individually. If you try to deploy 287 bundles
with interdependencies, this would mean you have to install them in the absolute correct
order or else the deployer finds missing dependencies and undeploys the bundle again.
The OSGi framework API allows for installation of multiple bundles before calling a
single refresh call to trigger the re-wiring. The deployer needs to support a mechanism
similar to this as well.
--
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