For the fun of it
$ cat input.xml
<it is="not(there)" you="not(can_see_it)"/>
$ xpath++ "string(//it[@is = document('input.xml')/it/@is]/and[@you = document('input.xml')/it/@you]/it/@is)" gone.xml
For the fun of it
In my January posting on TOhtml tool for creating the nicely syntax-highlighted source code listings I use in my blog
(based on vi's (my favorite editor) TOhtml command), I showed the "answer" to Shakespeare's question from a
C- or Java-programmer's perspective:
Today I thought again on Shakespeare's question, and think the answer is more likely to be "true"
because the question term is a (logic) tautology.
And XPath seems to agree with that view ;-)
(this posting was triggered by my today's application or not application, that is the question Twitter posting)
"Epoch time" or "Unix time" is the number of seconds since 1970-01-01T00:00:00Z (universal time, UTC).
For getting timestamps inside a stylesheet the number of seconds is fine, but getting the same value with millisecond resolution is better.
These are the four options to determine "now" in a DataPower stylesheet (<foobar/> because the xpath++ tool expressions do not need input here):
And to answer that question here now, we do not have Java on the box.
java.util.date.new() is just a convenience function mentioned back in 2008 in this developerWorks DataPower forum thread.
A colleague made me aware, that java.util.Date.new() is used in <func:function name="dpfunc:zulu-time">
from shipped stylesheet store:///utilities.xsl as well.
HermannSW 2700006U54 Identificações:  xpath++ webservice repair datapower mime tool broken coproc2 xslt 1.942 Visitas
Please have a look at some interesting/useful postings from today:
Find new piggyback technique for a stylesheet executed by coproc2 service.
It allows to "call" coproc2 service from a stylesheet just being executed by coproc2 service(!):
Posting "xpath++.xsl" allows xpath++ tool to be executed on all (Java) platforms by coproc2.java client:
See sample execution here:
Finally posting "Re: MIME response with no end tag through MPGW"
provides a workaround for dealing with broken webservice MIME responses missng the closing MIME boundary.
HermannSW 2700006U54 Identificações:  datapower soma xml xpath++ dosoma interface management xslt 2 Comentários 3.837 Visitas
My corrupted posting from June 12 does not only affect the display of all postings
(they are still accessible by google search as well as monthly Archive links on the right).
It seems that this now also broke the nice display of code sections, for new as well as for all my old postings ...
I really need to get the posting fixed but cannot do that myself and do not know whom to ask for ... :-(
This is the response to developerWorks DataPower Forum posting "Count number of requests coming into the processing policy":
> How can i count number of requests passing through the processing policy.
for those policies which are tied to specific stylesheets you may look up "Status-->XML Processing-->Stylesheet Executions" in WebGUI.
You get the exact counts of stylesheet executions for 10 sec, 1 min, 10 min, 1 hour and 1 day.
You may reset the counters to 0 by flushing the corresponding XML manager's stylesheet cache.
> is there any Dp:element , XSL element or function available.
This seems to indicate that you want to access these counts from within a stylesheet?
You can access above mentioned counters via XML management interface:
This is the XML management request:
See posting "Accessing XML Management interface from within a stylesheet" on how to use that:
HermannSW 2700006U54 Identificações:  soma xpath++ datapower management tool xml dosoma 3.057 Visitas
This developerWorks DataPower forum posting gives the complete details:
The problem statement was:
Can some one help with sample soma file to get list of MQFSH object names and its op state and Administrative State properties alone.
In the thread it turned out that the ObjectStatus of all objects could be selected only.
And it was proposed that an XPath expression needs to be applied to the SOMA response from DataPower to restrict the output to what is needed.
See here how doSoma and xpath++ tools play well together: