DT driver

I am using the DT driver on to output a file. The issue I am running into
is I have to preface each line with an action add,update,delete. 

Add,Account,Jeff@foo
Update,Account,jeff@foo
Delete,Account,jeff@foo

I did not want to have to create an aux attribute to put add,update,delete
in according to the operation, so I am trying to use the output stylesheet
to do that for me. I can get Add and Update to work by shoving this in the
template that matches on add/instance:

<xsl:choose>
<xsl:when test="not($hasAssociation) and $associationValue">
<xsl:text>Add,Account,</xsl:text>
</xsl:when>
<xsl:otherwise>
<xsl:text>Update,Account,</xsl:text>
</xsl:otherwise>
</xsl:choose>	

I was working on delete(being able to put the deleted email address is
another issue entirely but I think can build through srcdn, but I cannot
even get anything to process for a delete.) I put this small template in
after the add/instance template:
		
<xsl:template match="input/delete">
<xsl:text>XXXXXXXXXXXXXXXXX</xsl:text>
</xsl:template>

and I cannot even get that text to output. someone point me on the right

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dirty hack of the day.... somewhere (Command Transform?) add a rule that
detects the operation type and then adds an operational attribute.  You
don't need it to actually be in the schema anywhere in eDir or even in
the filter (since you're past the filter at the beginning of the
channel).  Name it optype and have a rule like:

if operation equal add then add operational attribute optype value add
if operation equal modify then add operational attribute optype value modify
over and over

Maybe that will work.  Still need your output/input transform to
understand the field... possibly the driver config as well but I'm sure
you can get that all worked out.

Good luck.





Jeff Johnson wrote:
| I am using the DT driver on to output a file. The issue I am running into
| is I have to preface each line with an action add,update,delete.
|
| Add,Account,Jeff@foo
| Update,Account,jeff@foo
| Delete,Account,jeff@foo
|
| I did not want to have to create an aux attribute to put add,update,delete
| in according to the operation, so I am trying to use the output stylesheet
| to do that for me. I can get Add and Update to work by shoving this in the
| template that matches on add/instance:
|
| <xsl:choose>
| <xsl:when test="not($hasAssociation) and $associationValue">
| <xsl:text>Add,Account,</xsl:text>
| </xsl:when>
| <xsl:otherwise>
| <xsl:text>Update,Account,</xsl:text>
| </xsl:otherwise>
| </xsl:choose>	
|
| I was working on delete(being able to put the deleted email address is
| another issue entirely but I think can build through srcdn, but I cannot
| even get anything to process for a delete.) I put this small template in
| after the add/instance template:
| 		
| <xsl:template match="input/delete">
| <xsl:text>XXXXXXXXXXXXXXXXX</xsl:text>
| </xsl:template>
|
| and I cannot even get that text to output. someone point me on the right
| track please. thanks!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIK07i3s42bA80+9kRAsf7AKCFw1xtxs65rDkQ+eymYusBv50pXACeNjY3
KeICv4kjJBMQ3UXtxQjPdt8=
=Hudj

i actually had thought of using an operation attribute, but didnt think
that would work. the issue is how do i get the operation attribute in the
output text file?

On Wed, 14 May 2008 20:43:16 +0000, ab@novell.com wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Dirty hack of the day.... somewhere (Command Transform?) add a rule that
> detects the operation type and then adds an operational attribute.  You
> don't need it to actually be in the schema anywhere in eDir or even in
> the filter (since you're past the filter at the beginning of the
> channel).  Name it optype and have a rule like:
> 
> if operation equal add then add operational attribute optype value add
> if operation equal modify then add operational attribute optype value
modify
> over and over
> 
> Maybe that will work.  Still need your output/input transform to
> understand the field... possibly the driver config as well but I'm sure
> you can get that all worked out.
> 
> Good luck.
> 
> 
> 
> 
> 
> Jeff Johnson wrote:
> | I am using the DT driver on to output a file. The issue I am running
into
> | is I have to preface each line with an action add,update,delete.
> |
> | Add,Account,Jeff@foo
> | Update,Account,jeff@foo
> | Delete,Account,jeff@foo
> |
> | I did not want to have to create an aux attribute to put
add,update,delete
> | in according to the operation, so I am trying to use the output
stylesheet
> | to do that for me. I can get Add and Update to work by shoving this in
the
> | template that matches on add/instance:
> |
> | <xsl:choose>
> | <xsl:when test="not($hasAssociation) and
$associationValue">
> | <xsl:text>Add,Account,</xsl:text>
> | </xsl:when>
> | <xsl:otherwise>
> | <xsl:text>Update,Account,</xsl:text>
> | </xsl:otherwise>
> | </xsl:choose>	
> |
> | I was working on delete(being able to put the deleted email address is
> | another issue entirely but I think can build through srcdn, but I cannot
> | even get anything to process for a delete.) I put this small template in
> | after the add/instance template:
> | 		
> | <xsl:template match="input/delete">
> | <xsl:text>XXXXXXXXXXXXXXXXX</xsl:text>
> | </xsl:template>
> |
> | and I cannot even get that text to output. someone point me on the right
> | track please. thanks!
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFIK07i3s42bA80+9kRAsf7AKCFw1xtxs65rDkQ+eymYusBv50pXACeNjY3
> KeICv4kjJBMQ3UXtxQjPdt8=
> =Hudj

sorry for some reason i thought you said operation-property :) this should
be an easy fix now hopefully. thanks!

On Wed, 14 May 2008 20:43:16 +0000, ab@novell.com wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Dirty hack of the day.... somewhere (Command Transform?) add a rule that
> detects the operation type and then adds an operational attribute.  You
> don't need it to actually be in the schema anywhere in eDir or even in
> the filter (since you're past the filter at the beginning of the
> channel).  Name it optype and have a rule like:
> 
> if operation equal add then add operational attribute optype value add
> if operation equal modify then add operational attribute optype value
modify
> over and over
> 
> Maybe that will work.  Still need your output/input transform to
> understand the field... possibly the driver config as well but I'm sure
> you can get that all worked out.
> 
> Good luck.
> 
> 
> 
> 
> 
> Jeff Johnson wrote:
> | I am using the DT driver on to output a file. The issue I am running
into
> | is I have to preface each line with an action add,update,delete.
> |
> | Add,Account,Jeff@foo
> | Update,Account,jeff@foo
> | Delete,Account,jeff@foo
> |
> | I did not want to have to create an aux attribute to put
add,update,delete
> | in according to the operation, so I am trying to use the output
stylesheet
> | to do that for me. I can get Add and Update to work by shoving this in
the
> | template that matches on add/instance:
> |
> | <xsl:choose>
> | <xsl:when test="not($hasAssociation) and
$associationValue">
> | <xsl:text>Add,Account,</xsl:text>
> | </xsl:when>
> | <xsl:otherwise>
> | <xsl:text>Update,Account,</xsl:text>
> | </xsl:otherwise>
> | </xsl:choose>	
> |
> | I was working on delete(being able to put the deleted email address is
> | another issue entirely but I think can build through srcdn, but I cannot
> | even get anything to process for a delete.) I put this small template in
> | after the add/instance template:
> | 		
> | <xsl:template match="input/delete">
> | <xsl:text>XXXXXXXXXXXXXXXXX</xsl:text>
> | </xsl:template>
> |
> | and I cannot even get that text to output. someone point me on the right
> | track please. thanks!
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFIK07i3s42bA80+9kRAsf7AKCFw1xtxs65rDkQ+eymYusBv50pXACeNjY3
> KeICv4kjJBMQ3UXtxQjPdt8=
> =Hudj

i actually got my delete working,,,i was an idiot and forgot to modify the
output transform to process it. so hopefully i can get this working
now,,we see :)

On Wed, 14 May 2008 20:43:16 +0000, ab@novell.com wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Dirty hack of the day.... somewhere (Command Transform?) add a rule that
> detects the operation type and then adds an operational attribute.  You
> don't need it to actually be in the schema anywhere in eDir or even in
> the filter (since you're past the filter at the beginning of the
> channel).  Name it optype and have a rule like:
> 
> if operation equal add then add operational attribute optype value add
> if operation equal modify then add operational attribute optype value
modify
> over and over
> 
> Maybe that will work.  Still need your output/input transform to
> understand the field... possibly the driver config as well but I'm sure
> you can get that all worked out.
> 
> Good luck.
> 
> 
> 
> 
> 
> Jeff Johnson wrote:
> | I am using the DT driver on to output a file. The issue I am running
into
> | is I have to preface each line with an action add,update,delete.
> |
> | Add,Account,Jeff@foo
> | Update,Account,jeff@foo
> | Delete,Account,jeff@foo
> |
> | I did not want to have to create an aux attribute to put
add,update,delete
> | in according to the operation, so I am trying to use the output
stylesheet
> | to do that for me. I can get Add and Update to work by shoving this in
the
> | template that matches on add/instance:
> |
> | <xsl:choose>
> | <xsl:when test="not($hasAssociation) and
$associationValue">
> | <xsl:text>Add,Account,</xsl:text>
> | </xsl:when>
> | <xsl:otherwise>
> | <xsl:text>Update,Account,</xsl:text>
> | </xsl:otherwise>
> | </xsl:choose>	
> |
> | I was working on delete(being able to put the deleted email address is
> | another issue entirely but I think can build through srcdn, but I cannot
> | even get anything to process for a delete.) I put this small template in
> | after the add/instance template:
> | 		
> | <xsl:template match="input/delete">
> | <xsl:text>XXXXXXXXXXXXXXXXX</xsl:text>
> | </xsl:template>
> |
> | and I cannot even get that text to output. someone point me on the right
> | track please. thanks!
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFIK07i3s42bA80+9kRAsf7AKCFw1xtxs65rDkQ+eymYusBv50pXACeNjY3
> KeICv4kjJBMQ3UXtxQjPdt8=
> =Hudj