Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.0.GA
    • Fix Version/s: 1.1.0.M2
    • Component/s: IoC
    • Labels:
      None

      Description

      ApplicationContext imports PyroProxyFactory so that it can tag it as a type to avoid. This is requiring users to install Pyro in order to use the IoC container. Replacing it with some alternative strategy would remove this dependency.

      ==From an posting on the mailing list ==
      Some problems here:

      • springpython.context depends on pyro just because it imports
        PyroProxyFactory to add it in types_to_avoid, but this seems a bit of
        overkill.

        Activity

        Hide
        alanfranz Alan Franzoni added a comment -

        this is a patch proposal, against trunk rev. 622.

        Show
        alanfranz Alan Franzoni added a comment - this is a patch proposal, against trunk rev. 622.
        Hide
        gregturn Greg Turnquist added a comment -

        Took Alan's patch, and applied it to a copy of the trunk. Had a small glitch with jython, which was resolved by initializing self._dict_["service_url"] to None, just like client_proxy. Verified against python2.4, 2.5, 2.6, and jython2.5. Thanks Alan!

        Show
        gregturn Greg Turnquist added a comment - Took Alan's patch, and applied it to a copy of the trunk. Had a small glitch with jython, which was resolved by initializing self._ dict _ ["service_url"] to None, just like client_proxy. Verified against python2.4, 2.5, 2.6, and jython2.5. Thanks Alan!
        Hide
        gregturn Greg Turnquist added a comment -

        While reviewing SESPRINGPYTHONPY-12, spotted old comment in front of PyroServiceExporter involving this circular dependency and its workaround. Realizing it had been fixed I patched PyroServiceExporter to properly use InitializingObject.

        Show
        gregturn Greg Turnquist added a comment - While reviewing SESPRINGPYTHONPY-12 , spotted old comment in front of PyroServiceExporter involving this circular dependency and its workaround. Realizing it had been fixed I patched PyroServiceExporter to properly use InitializingObject.

          People

          • Assignee:
            gregturn Greg Turnquist
            Reporter:
            gregturn Greg Turnquist
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: