You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Henri van den bulk (JIRA)" <ji...@apache.org> on 2010/11/17 17:21:15 UTC

[jira] Commented: (DIRSTUDIO-710) SearchResultEntryDsml not setting attribute name correctly

    [ https://issues.apache.org/jira/browse/DIRSTUDIO-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933010#action_12933010 ] 

Henri van den bulk commented on DIRSTUDIO-710:
----------------------------------------------

This is in package org.apache.directory.shared.dsmlv2.reponse; shared-dsml-parser-0.9.19.jar


> SearchResultEntryDsml not setting attribute name correctly
> ----------------------------------------------------------
>
>                 Key: DIRSTUDIO-710
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-710
>             Project: Directory Studio
>          Issue Type: Bug
>          Components: studio-dsml-parser
>    Affects Versions: 1.5.3
>            Reporter: Henri van den bulk
>
> When the DSML repsone creation is converting the LDAP request to a DSML response the attribute names are not set correctly. Attribute name should be Camel case for the name field. Below is an example of what is being returned:
> {code:xml}
> 			<dsml:attr name="postalcode">
> 				<dsml:value>23337</dsml:value>
> 			</dsml:attr>
> {code}
> However, according to the DSML specification when I request *postalCode* it should return Camel backed result. So the valid result should be:
> {code:xml}
> 			<dsml:attr name="postalCode">
> 				<dsml:value>23337</dsml:value>
> 			</dsml:attr>
> {code}
> The issue is cause by using the getID operation instead of the getUpId in SearchResultEntryDsml.toDsml.
> the following line will need to change from
> {code:java}
>            attributeElement.addAttribute( "name", attribute.getId() );
> {code}
> to
> {code:java}
>            attributeElement.addAttribute( "name", attribute.getUpId() );
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.