Article

lhaeger's picture
article
Reads:

7855

Score:
0
0
 
Comments:

0

Handling Move Events and Associations with the Loopback Driver

Author Info

29 August 2007 - 2:36am
Submitted by: lhaeger

Author Blog
Author Profile

Tags

Tags Map

(View Disclaimer)

Problem

A Forum reader recently asked:

"How is it possible to handle a move event in a loopback driver when there is no association? I've read that one should not use associations with the loopback driver and just handle everything in the event transform. As I understand it, I need an association to get a move event - when I do a move, I just get a sync event."

And here's the response from Lothar Haeger ...

Solution

That's the easiest way in many cases, but it's not forbidden to use association on a loopback driver. Actually it seems to be a good idea for what you want to do. You can simply add a subscriber matching policy like this:

<rule>
  <description>Match to self</description>
  <conditions/>
  <actions>
    <do-set-op-association>
      <arg-association>
        <token-src-attr name="GUID"/>
      </arg-association>
    </do-set-op-association>
    <do-add-association>
      <arg-association>
        <token-xpath expression="association/text()"/>
      </arg-association>
    </do-add-association>
  </actions>
</rule>

The loopback driver will behave a lot like any other "ordinary" driver. Don't forget to add a rule like this as last subscriber command transform, too:

<rule>
  <description>Veto all</description>
    <conditions/>
  <actions>
    <do-veto/>
  </actions>
</rule>

Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.



Related Articles


User Comments

© 2013 Novell