RefEngine persistance bug?

Raphael Ritz <[email protected]>
Newsgroups gmane.comp.web.zope.plone.archetypes.devel
Organization Humboldt-University Berlin
Message-ID <[email protected]>
Hi,

I'm currently stumbling over the following weird behavior
that I don't understand:

Use-case: I want to create a reference from code, like in

    ref = self.addReference(target, ref_name)

(which works fine) with the only difference that I want
it the other way around, i.e,

    ref = target.addReference(self, ref_name)

i.e., in a method of 'self' I have a handle on an object
'target' for which I want to set the reference.
But at first glance it looks like the reference isn't set.

Debuging this, I figured out that initially, the reference
is created (by calling 'print ref' right after adding it
shows up corectly in the log) but when browsing to the affected
objects later, the reference is gone :-(

Anybody a clue why?

Any idea how to get it persistent?
(all I tried so far was to set 'target._p_changed=1' but this didn't
change things in any way)

Raphael



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.