[Checkins] SVN: five.localsitemanager/branches/icemac-absolute-path-components/src/five/localsitemanager/registry.py traverse to component instead of traversing to its parent and wrapping the stored component into parent's path as it makes more sense

[Michael Howitz]

Log message for revision 90333:
  traverse to component instead of traversing to its parent and wrapping the stored component into parent's path as it makes more sense

Changed:
  U   five.localsitemanager/branches/icemac-absolute-path-components/src/five/localsitemanager/registry.py

-=-
Modified: five.localsitemanager/branches/icemac-absolute-path-components/src/five/localsitemanager/registry.py
===================================================================
--- five.localsitemanager/branches/icemac-absolute-path-components/src/five/localsitemanager/registry.py	2008-08-26 14:11:43 UTC (rev 90332)
+++ five.localsitemanager/branches/icemac-absolute-path-components/src/five/localsitemanager/registry.py	2008-08-26 14:32:59 UTC (rev 90333)
@@ -105,10 +105,8 @@
     # If component is stored as a ComponentPathWrapper, we traverse to
     # the component using the stored path:
     if isinstance(comp, ComponentPathWrapper):
-        return comp.component.__of__(
-            getSite().unrestrictedTraverse(comp.path[:-1]))
+        return getSite().unrestrictedTraverse(comp.path)
 
-
     # BBB: The primary reason for doing this sort of wrapping of
     # returned utilities is to support CMF tool-like functionality where
     # a tool expects its aq_parent to be the portal object. New code