I actually ran into this issue yesterday.  No it does not throw an 'error' per se that gets 'caught' by the error rule.

I am still looking into a solution.  Let me know if you find one, and I will do the same. 

I suggest using Firefox.  WebGUI works MUCH better with Firefox IMO. 

This may not fix your issue though, but worth a try

I have used dp:variable extensions in XSLT in the past.

Your syntax looks good to me.

Have you included xmlns:dp="http://www.datapower.com/extensions" in your XSL? 

Try this :

<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tns="http://www.example.org/tns" xmlns:dp="http://www.datapower.com/extensions" extension-element-prefixes="dp" exclude-result-prefixes="dp">
   <xsl:output method="xml"/>
   <xsl:template match="/">
      <someRootElement>
         <responseheader:DestinationSystem>
            <xsl:value-of select="dp:variable('var://context/tempvar1/request/OriginationSystem')"/>
         </responseheader:DestinationSystem>
         <responseheader:OriginationSystem>
            <xsl:value-of select="dp:variable('var://context/tempvar1/request/DestinationSystem')"/>
         </responseheader:OriginationSystem>
         <responseheader:CorrelationID>
            <xsl:value-of select="dp:variable('var://context/tempvar1/request/MessageID')"/>
         </responseheader:CorrelationID>
      </someRootElement>
   </xsl:template>
</xsl:stylesheet>

(I haven't had a chance to test this yet)

We are restricting operations based on access using LDAP Authorization.

Here is a portion of the XSL that is using the result set from the LDAP query.

<xsl:variable name="authorizeServices">
         <xsl:copy-of select="$result/LDAP-search-results/result/attribute-value/text()"/>
      </xsl:variable>
      <!--     Authorize service    -->
      <xsl:variable name="serviceMatch">
         <xsl:for-each select="$result/LDAP-search-results/result/attribute-value">
            <xsl:variable name="authorizeServices">
               <xsl:value-of select="text()"/>
            </xsl:variable>
            <xsl:choose>
               <xsl:when test="$authorizeServices=$msgAuthorize">
                  <xsl:value-of select="true()"/>
               </xsl:when>
               <xsl:otherwise>
                  <!-- do what you like here -->
               </xsl:otherwise>
            </xsl:choose>
         </xsl:for-each>
      </xsl:variable>
      <xsl:choose>

As you can see we use the LDAP 'attribute-value' result, and match that to the operation name.  We use a 'for-each' as a user may have access to multiple operations.

If there is a match the user is authorized to utilize that service and operation, otherwise they will be denied access. 

Not sure your comfort level with DataPower, but some other users might not know how to implement the custom XSL.  To do so in the AAA policy go to the Authorize tab, for 'Method' select 'custom' from the drop down list.  Then in the 'Custom URL' box you would put the value of your XSL. e.g. 'local:///myAAA.xsl'.

I have omitted some details, but I think this should get you going in the right direction.  If you need more help let me know. 

I hope this helps.

I would suggest using soapUI instead of cURL.  soapUI is easier to use than cURL for https IMO.

I prefer it over cURL, it might make your life easier.

soapUI can be found here for free :

http://sourceforge.net/project/showfiles.php?group_id=136013&package_id=163662&release_id=542387

Home site is :

http://www.soapui.org/

(I am not affiliated with them at all)

I agree, I think AZ is the correct answer. 

From the documentation:
"After authorizing the client, an Access Control Policy may perform optional post-processing activities...."

Although this might be a 'trick' question as Authentication is performed before Authorization (in the out of the box 'AAA' policy).  So the key phrase in the question is "...previous AAA step."

I think if you want to set multiple target URL's in the 'Result Action' you would need to use an XSL (or 'setvar action') to specify the target URL's. 

e.g.

<xsl:variable name="URLs">
   <url>http://10.69.69.69:2222</url>
   <url>http://10.69.69.69:2223</url>
</xsl:variable>
<dp:set-variable name="'var://context/PUBSUB/endpoints'" value="$URLs/*"/>

Then in the Destination field on the 'Result Action' you would put 'var://context/PUBSUB/endpoints'. as your destination.

Now getting back to your question, it appears like you are hoping to aggregate the responses from multiple providers?  Is that the case?  I would be interested to see your use case as well.

Been waiting for this for some time. 

Great idea, I was just talking to co-workers yesterday about a need for a DataPower Forum. 

Kudos.