Try using NamedParameterJdbcPersonAttributeDao  instead.

On Wednesday, August 19, 2015 at 3:26:37 PM UTC-7, Manfredo Hopp wrote:
>
> See my previous mail which describes details of this issue.
>
> Same result for  version 1.7.0 (latest?)
>
> Regards Manfredo
>
> 2015-08-19 17:45 GMT-03:00 Misagh Moayyed <[email protected] 
> <javascript:>>:
>
>> This “may” be an issue with person directory. Don’t know yet, but your 
>> other option for now would be to have 2 DAOs and merge the result together 
>> finally.
>>
>>  
>>
>> What version of person directory is this by the way? Can you dulicate the 
>> problem with the latest? 
>>
>>  
>>
>> *From:* Manfredo Hopp [mailto:[email protected] <javascript:>] 
>> *Sent:* Wednesday, August 19, 2015 11:26 AM
>> *To:* [email protected] <javascript:>
>> *Subject:* [cas-user] Resolving attirbutes dao results in "no value 
>> specified for parameter 2"
>>
>>  
>>
>> Hello I am using singleRowJdbcPersonAttributeDao to resolve principal 
>> attributes defined as:
>>
>>  
>>
>> singleRowJdbcPersonAttributeDao
>>
>>                     
>> class="org.jasig.services.persondir.support.jdbc.SingleRowJdbcPersonAttributeDao">
>>
>>                       <constructor-arg index="0" ref="dataSourceA" />
>>
>>                       <constructor-arg index="1"
>>
>>                       value="(SELECT a, b,  c , d
>>
>>                                               FROM u WHERE {0} 
>>
>>                                   UNION
>>
>>                                               (SELECT a, b ,c d 
>>
>>                                               FROM r WHERE {0})" />
>>
>>                       <property name="queryAttributeMapping">
>>
>>                                   <map>
>>
>>                                               <entry key="username" 
>> value="id" />
>>
>>                                   </map>
>>
>>                       </property>
>>
>>  
>>
>> And get SQLException->No value specified for parameter 2 
>>
>>  
>>
>> NO replacement for second {0}, so I am not able to use this query.
>>
>>  
>>
>> Is there any reason for the behaviour of this implementation?
>>
>>  
>>
>> Regards Manfredo
>>
>>  
>>
>> -- 
>>
>> You are currently subscribed to [email protected] <javascript:> as: 
>> [email protected] <javascript:>
>>
>> To unsubscribe, change settings or access archives, see 
>> http://www.ja-sig.org/wiki/display/JSG/cas-user
>>
>> -- 
>> You are currently subscribed to [email protected] <javascript:> as: 
>> [email protected] <javascript:>
>> To unsubscribe, change settings or access archives, see 
>> http://www.ja-sig.org/wiki/display/JSG/cas-user
>>
>>
> -- 
> You are currently subscribed to [email protected] <javascript:> as: 
> [email protected] <javascript:>
> To unsubscribe, change settings or access archives, see 
> http://www.ja-sig.org/wiki/display/JSG/cas-user
>
>
-- 
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-user

Reply via email to