A Nimble approact to dependency management
•
1 like•990 views
An overview of the Nimble dependecy resolver and provisioner from an OSGi point of view
Recommended
More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
A Nimble approact to dependency management
- 1. A Nimble approach to dependency management robert.dunne@paremus.com http://nimble.codecauldron.org/download A Nimble approach to dependency management www.paremus.com June 2009 Copyright © 2009 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved. Tuesday, 23 June 2009
- 2. Managing Dependency Compexity • Modularity is good ... • ... But often undermined by complexity ‣ wire-up ‣ configuration • How can we manage this? ‣ automate where possible ‣ preserve and reuse design decisions ‣ we’ve been here before A Nimble approach to dependency management www.paremus.com June 2009 Copyright © 2009 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved. Tuesday, 23 June 2009
- 3. Nimble • Full lifecycle dependency resolver ‣ resolve, install, uninstall and clean-up - rich diagnostics ‣ multiple deployable units - easily extended - Bundles, WARs, POJOs, Config files ‣ OSGi specific features - fragment attachment policy - optional import policy - import narrowing - resolves dependencies on extender bundles (DS, SpringDM, iPOJO) A Nimble approach to dependency management www.paremus.com June 2009 Copyright © 2009 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved. Tuesday, 23 June 2009
- 4. Parts ‣ Nimble manages a Part Graph - parts have capabilities and requirements - resolved bundles - requirements -> exports, capabilities -> imports - POJOs - requirements -> constructor args, capabilities -> interfaces - Add & Remove Root Parts - Control Resolution with policy A Nimble approach to dependency management www.paremus.com June 2009 Copyright © 2009 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved. Tuesday, 23 June 2009
- 5. Builders • Parts have a builder requirement ‣ no need for pre-installed builders ‣ builder turns the part into a runtime entity using: - artifacts for the part - capabilities wired to parts other requirements • Builders for ‣ resolved, active and fragment bundles ‣ WARs, Config files ‣ easily extensible A Nimble approach to dependency management www.paremus.com June 2009 Copyright © 2009 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved. Tuesday, 23 June 2009
- 6. Rules and Extensions • Rules are Templates for Parts ‣ Rule + configured Extensions -> Part ‣ target - rules to which extensions can apply ‣ policy - choice of extensions to apply A Nimble approach to dependency management www.paremus.com June 2009 Copyright © 2009 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved. Tuesday, 23 June 2009
- 7. Repositories and Policies • Repository ‣ Index of available rules and extensions ‣ OBR or richer Nimble metadata • Policies ‣ configure selected extensions ‣ constrain requirement -> capability matching ‣ configure option resolution A Nimble approach to dependency management www.paremus.com June 2009 Copyright © 2009 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved. Tuesday, 23 June 2009
- 8. Modelling Fragments Fragment Rules Fragment Parts A Nimble approach to dependency management www.paremus.com June 2009 Copyright © 2009 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved. Tuesday, 23 June 2009
- 9. Thanks for coming http://nimble.codecauldron.org/download http://www.paremus.com robert.dunne@paremus.com A Nimble approach to dependency management www.paremus.com June 2009 Copyright © 2009 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved. Tuesday, 23 June 2009