Hi All

We're in the process of moving from IDM 2 to IDM 3.5.1 and i'm just
reviewing the XML code in some of our drivers, and I've noticed some
code in the EventTransform Policy on the Subscriber channel that looks
redundant.

For example, our SAP driver has:


Code:
--------------------
<?xml version="1.0" encoding="UTF-8"?>

<xsl:stylesheet exclude-result-prefixes="query cmd jdbc" extension-element-prefixes="query" version="1.0" xmlns:cmd="http://www.novell.com/nxsl/java/com.novell.nds.dirxml.driver.XdsCommandProcessor" xmlns:jdbc="urn:dirxml:jdbc" xmlns:query="http://www.novell.com/nxsl/java/com.novell.nds.dirxml.driver.XdsQueryProcessor" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

<!--
Match MODIFY of user and copy through
-->
<xsl:template match="modify[@class-name='User']">
<xsl:copy>
<xsl:apply-templates select="@*|node()"/>
</xsl:copy>
</xsl:template>

<!--
MATCH syncs and drop
-->
<xsl:template match="sync[@class-name='User']"/>
</xsl:stylesheet>
--------------------


I'm unsure if this is needed, or if it's a throwback to the old DirXML
1.1a days when the driver was originally created.

Do we really need to xsl:copy the node, or is this done automatically
now ?

Is dropping resyncs generally a bad idea ? I'm guessing this was to
allow us to disable the driver under DirXML 1.1a without the impact of
the resync on re-enable, but is it possible there is another reason ?

Thx


--
TS_MS
------------------------------------------------------------------------
TS_MS's Profile: http://forums.novell.com/member.php?userid=19762
View this thread: http://forums.novell.com/showthread.php?t=339631