1 2 Previous Next 16 Replies Latest reply on Dec 23, 2009 11:14 AM by alesj Go to original post
      • 15. Re: Installing a context leads to resolve of other unrelated con
        dmlloyd

        bill.burke@jboss.com wrote:

        [...]

        2.  We're going to have to start indexing dependencies.  What do I mean by that?  For example, when a bean gets deployed, it should be able to look up whatever depends on it and only try to resolve those dependencies.  You can do this incrementally for explicit dependency items.  You'd also keep track of which contexts had implicit vs. explicit dependency items and only do a resolveContext on implicit ones after the explicit ones were finished.

         

        In other words, dependencies should be organized in a flat graph.  I've tried to sell this line before, and nobody was buying.  BTW, from what I can tell, implicit dependencies are an illusion - either the dependency is explicit to begin with, or a deployer will generate explicit deps based on what it knows of the implicit deps (be they from spec details or implied from other deployment artifacts).  If a dep doesn't fall into one of these categories, it doesn't exist.  Either way, MC should be able to see things as a fixed set of dependencies.

        • 16. Re: Installing a context leads to resolve of other unrelated con
          alesj

          In other words, dependencies should be organized in a flat graph.  I've tried to sell this line before, and nobody was buying.  BTW, from what I can tell, implicit dependencies are an illusion - either the dependency is explicit to begin with, or a deployer will generate explicit deps based on what it knows of the implicit deps (be they from spec details or implied from other deployment artifacts).  If a dep doesn't fall into one of these categories, it doesn't exist.  Either way, MC should be able to see things as a fixed set of dependencies.

          To begin with, we should make dependency resolution plugable.

          We are already seeing some issues by not having this plugability in our OSGi facade.

          And if we had this, it would be easy for us to see what exactly we need,

          or better, how much do we affect anything non-explicitly declared.

           

          But I agree with you, "if a dep doesn't fall into one of these categories, it doesn't exist".

           

          With plugability we will be able to preserve previous behavior, slow or not,

          while still being able to move fwd with more indexed approach, as suggested.

           

           


          1 2 Previous Next