florianz1 Absent Member.
Absent Member.
311 views

strip trigger operation only


hi,

hopefully a short to answer question 🙂

--------------
i start processing with that trigger document below


Code:
--------------------
<nds dtdversion="3.5" ndsversion="8.x">
<source>
<product version="3.6.10.4747">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<trigger event-id="trigger-job:Spray#20120105165841#0#0" source="Spray">
<operation-data source="Spray"/>
</trigger>
</input>
</nds>
--------------------


after some time i get:


Code:
--------------------
<nds dtdversion="3.5" ndsversion="8.x">
<source>
<product version="3.6.10.4747">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<trigger event-id="trigger-job:Spray#20120105165841#0#0" source="Spray">
<operation-data source="Spray"/>
</trigger>
<modify dest-dn="\test\cocoon\secoly\groups\myGroup001" event-id="trigger-job:Spray#20120105165841#0#0">
<modify-attr attr-name="Member">
<add-value>
<value>\test\cocoon\onely\r303cgrh</value>
</add-value>
</modify-attr>
</modify>
</input>
</nds>
--------------------



what i´d like to have is:


Code:
--------------------
<nds dtdversion="3.5" ndsversion="8.x">
<source>
<product version="3.6.10.4747">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<modify dest-dn="\test\cocoon\secoly\groups\myGroup001" event-id="trigger-job:Spray#20120105165841#0#0">
<modify-attr attr-name="Member">
<add-value>
<value>\test\cocoon\onely\r303cgrh</value>
</add-value>
</modify-attr>
</modify>
</input>
</nds>
--------------------



i´ve tried to strip the trigger operation with
Code:
--------------------
<do-strip-xpath expression="."/>
--------------------
from the document, but that not leaves the modify alone (as was
expected), but results in a looong

Code:
--------------------
Message: Code(-9010) An exception occurred: java.lang.NullPointerException
at com.novell.nds.dirxml.engine.rules.RuleUtil.findOrCreateModOperation(RuleUtil.java:1394)
at com.novell.nds.dirxml.engine.rules.DoAddDestAttrValue.apply(DoAddDestAttrValue.java:185)
at com.novell.nds.dirxml.engine.rules.ActionSet.apply(ActionSet.java:177)
at com.novell.nds.dirxml.engine.rules.DoIf.apply(DoIf.java:84)
at com.novell.nds.dirxml.engine.rules.ActionSet.apply(ActionSet.java:177)
at com.novell.nds.dirxml.engine.rules.DoForEach.apply(DoForEach.java:137)
at com.novell.nds.dirxml.engine.rules.ActionSet.apply(ActionSet.java:177)
at com.novell.nds.dirxml.engine.rules.DoForEach.apply(DoForEach.java:137)
at com.novell.nds.dirxml.engine.rules.ActionSet.apply(ActionSet.java:177)
at com.novell.nds.dirxml.engine.rules.DirXMLScriptProcessor.applyRules(DirXMLScriptProcessor.java:298)
at com.novell.nds.dirxml.engine.Subscriber.processEvents(Subscriber.java:854)
at com.novell.nds.dirxml.engine.Driver.submitTransaction(Driver.java:624)
at com.novell.nds.dirxml.engine.DriverEntry.submitTransaction(DriverEntry.java:1050)
at com.novell.nds.dirxml.engine.DriverEntry.processCachedTransaction(DriverEntry.java:934)
at com.novell.nds.dirxml.engine.DriverEntry.eventLoop(DriverEntry.java:756)
at com.novell.nds.dirxml.engine.DriverEntry.run(DriverEntry.java:561)
at java.lang.Thread.run(Thread.java:619)
--------------------
error and breaking the operation.
i could let the modify get done directly, and let the trigger run dead
against the filter, but i´d prefer to have it stripped out in the first
place and let the modify run through to the (successful) end.

my questions are:
1. why does that happen?
2. how could a clean document, solely containing the modify, be
achieved?

thanks in advance for your comment(s), florian


--
florianz
------------------------------------------------------------------------
florianz's Profile: http://forums.novell.com/member.php?userid=210
View this thread: http://forums.novell.com/showthread.php?t=450336


Labels (1)
0 Likes
1 Reply
Knowledge Partner
Knowledge Partner

Re: strip trigger operation only

On 1/5/2012 12:36 PM, florianz wrote:
>
> hi,
>
> hopefully a short to answer question 🙂
>
> --------------
> i start processing with that trigger document below
>
>
> Code:
> --------------------
> <nds dtdversion="3.5" ndsversion="8.x">
> <source>
> <product version="3.6.10.4747">DirXML</product>
> <contact>Novell, Inc.</contact>
> </source>
> <input>
> <trigger event-id="trigger-job:Spray#20120105165841#0#0" source="Spray">
> <operation-data source="Spray"/>
> </trigger>
> </input>
> </nds>
> --------------------
>
>
> after some time i get:
>
>
> Code:
> --------------------
> <nds dtdversion="3.5" ndsversion="8.x">
> <source>
> <product version="3.6.10.4747">DirXML</product>
> <contact>Novell, Inc.</contact>
> </source>
> <input>
> <trigger event-id="trigger-job:Spray#20120105165841#0#0" source="Spray">
> <operation-data source="Spray"/>
> </trigger>
> <modify dest-dn="\test\cocoon\secoly\groups\myGroup001" event-id="trigger-job:Spray#20120105165841#0#0">
> <modify-attr attr-name="Member">
> <add-value>
> <value>\test\cocoon\onely\r303cgrh</value>
> </add-value>
> </modify-attr>
> </modify>
> </input>
> </nds>
> --------------------
>
>
>
> what i�d like to have is:
>
>
> Code:
> --------------------
> <nds dtdversion="3.5" ndsversion="8.x">
> <source>
> <product version="3.6.10.4747">DirXML</product>
> <contact>Novell, Inc.</contact>
> </source>
> <input>
> <modify dest-dn="\test\cocoon\secoly\groups\myGroup001" event-id="trigger-job:Spray#20120105165841#0#0">
> <modify-attr attr-name="Member">
> <add-value>
> <value>\test\cocoon\onely\r303cgrh</value>
> </add-value>
> </modify-attr>
> </modify>
> </input>
> </nds>
> --------------------
>
>
>
> i�ve tried to strip the trigger operation with
> Code:
> --------------------
> <do-strip-xpath expression="."/>
> --------------------
> from the document, but that not leaves the modify alone (as was
> expected), but results in a looong
>
> Code:
> --------------------
> Message: Code(-9010) An exception occurred: java.lang.NullPointerException
> at com.novell.nds.dirxml.engine.rules.RuleUtil.findOrCreateModOperation(RuleUtil.java:1394)
> at com.novell.nds.dirxml.engine.rules.DoAddDestAttrValue.apply(DoAddDestAttrValue.java:185)
> at com.novell.nds.dirxml.engine.rules.ActionSet.apply(ActionSet.java:177)
> at com.novell.nds.dirxml.engine.rules.DoIf.apply(DoIf.java:84)
> at com.novell.nds.dirxml.engine.rules.ActionSet.apply(ActionSet.java:177)
> at com.novell.nds.dirxml.engine.rules.DoForEach.apply(DoForEach.java:137)
> at com.novell.nds.dirxml.engine.rules.ActionSet.apply(ActionSet.java:177)
> at com.novell.nds.dirxml.engine.rules.DoForEach.apply(DoForEach.java:137)
> at com.novell.nds.dirxml.engine.rules.ActionSet.apply(ActionSet.java:177)
> at com.novell.nds.dirxml.engine.rules.DirXMLScriptProcessor.applyRules(DirXMLScriptProcessor.java:298)
> at com.novell.nds.dirxml.engine.Subscriber.processEvents(Subscriber.java:854)
> at com.novell.nds.dirxml.engine.Driver.submitTransaction(Driver.java:624)
> at com.novell.nds.dirxml.engine.DriverEntry.submitTransaction(DriverEntry.java:1050)
> at com.novell.nds.dirxml.engine.DriverEntry.processCachedTransaction(DriverEntry.java:934)
> at com.novell.nds.dirxml.engine.DriverEntry.eventLoop(DriverEntry.java:756)
> at com.novell.nds.dirxml.engine.DriverEntry.run(DriverEntry.java:561)
> at java.lang.Thread.run(Thread.java:619)
> --------------------
> error and breaking the operation.
> i could let the modify get done directly, and let the trigger run dead
> against the filter, but i�d prefer to have it stripped out in the first
> place and let the modify run through to the (successful) end.
>
> my questions are:
> 1. why does that happen?
> 2. how could a clean document, solely containing the modify, be
> achieved?
>
> thanks in advance for your comment(s), florian


IF operation = trigger
do-veto.

Should do it. The modify will get processed see the if op trigger and
not fire the rule.


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.