Commiting changes from listener

Millisa_Eubanks

I'm trying to write a listener that changes a content item then commits those changes to the database.  However everything I do seems to cause the code to constatnly call the same code, thus causing a loop that only stops when it is timed-out.

The test code I am using is:

log.debug("HELLO from vcm.associatedentity.groovy");log.debug("event: " + event);changes = content.getChanges();log.debug("checking changes: ${changes}");log.debug("changes size: " + changes.size());if (changes.size() > 0) {// without this, none of our changes will take effectlog.debug("changes found: ${changes}, committing");try {content.commit();} catch (Exception e) {log.error("error during. commit, not sure if everything worked", e);}}

As you can see this block is doing nothing but logging some messeages and commiting changes, but it still loops until it times out.  Should I be doing something besides calling commit to save my changes?  When I try calling code that does make changes but don't call commit those changes are not reflected in my content instance.

Please help

Warner_Soditus

that's precisely what you should expect from what you're doing. think about it. the listener is called BECAUSE there's a commit that happened. in the middle of that, you're explicitly doing a commit, which then calls your listener, which does another commit. if you're doing this in a pre-persistence listener, just take out your commit. that's what's going to happen. that's the whole reason the pre-persistence listener is being called.

if you're doing this in a post-persistence listener... then you do have to do a commit, but you have to figure out whether or not to do it, so you don't cause an infinite loop.

~Warner