Hi, Sonic wrote: > I just wanted to let you know that I now updated to beta-2 and tried again. > Replication for style elements still doesn't work, but Parameters, > Attachments and deletes seem to be replicated, if I understand the logfile > correctly.
OK, thanks for following through and reporting your progress. > Every time exorcist sees a style element or something similar, it > produces something like this in the logfile: > > 26.11.2005 18:54:51 net.sf.exorcist.midgard.MidgardImporter importObject > INFO: Importing midgard_style 8303fb7318dcbf61de37d670f113a3fb > 26.11.2005 18:54:51 net.sf.exorcist.midgard.MidgardImporter importObject > INFO: Local object is more recent! > > 26.11.2005 18:54:51 net.sf.exorcist.midgard.MidgardImporter importObject > INFO: Importing element_i 43ab3e0ce051aa9be905dcbd1d7855a4 > 26.11.2005 18:54:51 net.sf.exorcist.midgard.MidgardImporter importObject > INFO: Local object is more recent! > > Of course, all style elements are unmodified, except for one, so I guess > that's ok, and for the modifed object, the log entries looks like this: This seems correct. The "Local object is more recent!" message is printed whenever an object is not updated because no new changes are included in the replication dump. A more accurate message would be "Local object is up to date or more recent". > INFO: Importing midgard_element 019318338034deaaf407c7842777541a > 26.11.2005 18:54:51 net.sf.exorcist.midgard.MidgardImporter importObject > (...) > INFO: Importing element_i f956a9c80dd90e144b8ad08037cce706 > 26.11.2005 18:54:51 net.sf.exorcist.midgard.MidgardImporter importObject This suggests that Exorcist is at least correctly trying to update the modified element in question. And if you do not get any WARNING or ERROR messages in the log, then there shouldn't be any problems doing that... > But still, replication simply does not happen. The element_i's content in the > target database is still the same. What am I missing? Could you please try removing or commenting out (<!-- .... -->) the "importer" bean definition in your staging2live.xml configuration file. The result is that the staging2live script will print the entire exported site XML file to standard output for reviewing. You'll probably want to redirect sandard output to a file (staging2live.sh > content.xml) for easier access. Then open the file and search for the element GUID (019318338034deaaf407c7842777541a). Please check that the XML serialization really does contain the updated field values. BR, Jukka Zitting -- Yukatan - http://yukatan.fi/ - [EMAIL PROTECTED] Software craftmanship, JCR consulting, and Java development --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
