2 Replies Latest reply on Sep 1, 2006 6:23 AM by adrian.brock

    Using preinstantiated collections, maps (JBMICROCONT-35)

    alesj
    alesj Aug 31, 2006 3:31 PM

       


      Reopened since this isn't working.

      The only reason the test passed is because the default constructor
      was changed to set preinstantiated to true.

      If it uses the default constructor then it is not using preinstantiated object.


      Will look into this one.


      I've also uncommented the equivalent tests for sets and list.
      We could also do with array and map tests.


      I already added tests for arrays and maps, but forgot about lists and sets.

      • 4500 Views
      • Tags:
        • 1. Re: Using preinstantiated collections, maps (JBMICROCONT-35)
          alesj
          alesj Aug 31, 2006 5:33 PM (in response to alesj)

           

          "alesj" wrote:

          Reopened since this isn't working.

          The only reason the test passed is because the default constructor
          was changed to set preinstantiated to true.

          If it uses the default constructor then it is not using preinstantiated object.


          Will look into this one.


          The problem is that preinstantiated lookup needs to pass MetaDataVisitor.initialVisit() for meta data node stack lookup and controller set up.
          And test case simply uses plain meta data - no controller.

            • Actions
          • 2. Re: Using preinstantiated collections, maps (JBMICROCONT-35)
            adrian.brock Sep 1, 2006 6:23 AM (in response to alesj)

            That is correct. The tests have two versions, a plain
            version that constructs the BeanMetaData in line and an xml version.

            The xml version does use the controller, but the inline version
            only uses the configurator.

            You can change the inline version to use a full controller.
            See AbstractKernelConfigTest.

              • Actions