attribute resolver issues after upgrade to v3

Daniel Fisher dfisher at
Mon Aug 17 23:51:01 EDT 2015

On Fri, Aug 14, 2015 at 8:01 PM, Robert A Basch <rbasch at> wrote:

> In our version 2 attribute-resolver.xml, we have been using the
> template language to effect a conditional query in an additional LDAP
> data connector, based on the value (if any) of a dependency attribute:
>     <FilterTemplate>
>         <![CDATA[
>             #if (${attribute.isEmpty()} || ! ${attribute.get(0)})
>               <dummy filter guaranteed to return no results>
>             #else
>               <"real" LDAP search filter>
>             #end
>         ]]>
>     </FilterTemplate>

I believe JNDI strips spaces internally from the beginning and end of a
filter, but it doesn't strip other forms of whitespace. So the following
template would works as well:

             #if (${attribute.isEmpty()} || ! ${attribute.get(0)})
               <dummy filter guaranteed to return no results>#else
               <"real" LDAP search filter>#end

--Daniel Fisher
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the users mailing list