I'm trying to configure a loopback driver so it picks up objectClass A
(objSource), transforms it and writes it as an objectClass B (objObject)
in another container.

I've set objSource to sync in the subscriber and objObject to sync in
the publisher, including all its attributes.
In the mapping policy, I set the operation class to objObject when
'fromNds' is True and the class-name equals objSource . The driver is as
simple as that, apart from some transformations being done.

When I create an objSource, it goes through the subscriber and publisher
without any problems. objObject is written as it should.
When I modify an attribute on objSource, the publisher filter filters
out the objSource, which is fine. But somehow the engine sees the
<modify> document with an object-class of objSource. The result is that
the operation is vetoed by the filter. But the <modify> is an objObject,
which should not get filtered out.

I've attached a level 3 trace from where the modify is send through the
subscriber filter until the publisher filter vetoes the operation.

Does anyone recognize this behavior or have an explanation as to why the
engine would do this? And how to prevent this? Any hint is greatly



|Filename: resolve.log |
|Download: https://forums.netiq.com/attachment....tachmentid=404 |

turgon2007's Profile: https://forums.netiq.com/member.php?userid=9632
View this thread: https://forums.netiq.com/showthread.php?t=55178