Hi  Somashish !

It seems that this could eb either a bug or a configuration pb. It would be kind of you to fill a JIRA issue (http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10400) with a description of your pb (just copy paste the content of your mail) with more information :
- your current configuration file
- a sample of data that fail (just give us the exact description of the attributes you are trying to modify)

This will help us gratly to track the origin of the problem, and also to have a way to follow this issue and not forget it .

Thanks a lot for the report, we will do our best to fix it quickly !

Hi,



 I recently upgraded Directory server from version 0.9 to 0.9.3.  After the
upgradation the JNDI call
javax.naming.directory.DirContext.modifyAttributes(String name,
ModificationItems[] mods)has stopped working(This call was working without
any issue in 0.9). It has started failing with
InvalidAttributeIdentifierException. The structure of my application data
present in the LDAP server is identical in 0.9.3 to what it was in 0.9, so I
am sure the call is able to resolve the name. I have also checked the
contents of mods. The attributes are also present. The only difference that
I have noticed is the properties file in the 2 cases. In 0.9.3 it is an xml
file instead of a properties file. I am using the sample server.xml file
that comes with the 0.9.3 source distribution. (In case of 0.9 I was using
the sample server.properties file coming with the distribution). Also I use
JXplorer as LDAP browser. There also I am noticing the identical behavior.
Modification of any attribute was working in case of 0.9. But now with
0.9.3, I am not able to update any attribute through the browser.

Can anybody give me any pointer as to where I should look into in order to
resolve this issue. I feel it is an issue with my server startup parameters.



Thanks
Somashish




Reply via email to