Announcement Announcement Module
Collapse
No announcement yet.
Flexibilty in bundle update (as flexible as osgi console)? Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Flexibilty in bundle update (as flexible as osgi console)?

    I have the following scenario

    Bundle A - exports package p

    Bundle B - imports package p

    I deploy Bundle A ,followed by bundle B in Dm server pickup directory.

    Now when i update bundle A bundle B automiatically get updated. I prove this point by putting a sysout in the BundleActivator of B.

    Now this behavior is fine , but what if want extra flexibility like teh scenario below.

    I do this in osgi console:

    install Bundle A;
    install Bundle B;
    start Bundle A;
    start bundle B;

    now i update bundle A;
    update Bundle A

    At this point my bundle B is not refreshed , and still it uses the old classes.

    [I MISS THIS LEVEL OF CONTROL(THIS STAGE) BY DEPLOYING BUNDLE IN PICK UP OF DM SERVER]

    Only after i use
    refresh Bundle A

    Bundle B gets refreshed and its appContext is recreated.

    This is what dm server does.

    But doesn't anyone feel that this level of flexibility should be given to the user of Dm Server also ?



    Regards,
    Sudheer
Working...
X