removed irrelevant formatting changes
javadoc fix
This commit is contained in:
committed by
Rob Winch
parent
5cecd0b2f7
commit
74c77276ec
@@ -69,9 +69,8 @@ public @interface Attribute {
|
||||
* This value allows attributes to be read on read, but not persisted, there
|
||||
* are many operational and read-only ldap attributes which will throw errors
|
||||
* if they are persisted back to ldap.
|
||||
* see {@link org.springframework.ldap.odm.core.impl.AttributeMetaData}
|
||||
*
|
||||
* @return true is the attribute should not be written to ldap.
|
||||
* @return {@code true} is the attribute should not be written to ldap.
|
||||
*/
|
||||
boolean readonly() default false;
|
||||
|
||||
|
||||
@@ -19,8 +19,6 @@ package org.springframework.ldap.odm.core;
|
||||
import org.springframework.LdapDataEntry;
|
||||
import org.springframework.ldap.filter.Filter;
|
||||
|
||||
import java.util.Set;
|
||||
|
||||
import javax.naming.Name;
|
||||
|
||||
/**
|
||||
|
||||
@@ -13,6 +13,7 @@
|
||||
* See the License for the specific language governing permissions and
|
||||
* limitations under the License.
|
||||
*/
|
||||
|
||||
package org.springframework.ldap.odm.core.impl;
|
||||
|
||||
import org.springframework.ldap.UncategorizedLdapException;
|
||||
@@ -42,7 +43,6 @@ import java.util.TreeSet;
|
||||
* @author Paul Harvey <paul.at.pauls-place.me.uk>
|
||||
*/
|
||||
/* package */ final class AttributeMetaData {
|
||||
|
||||
private static final CaseIgnoreString OBJECT_CLASS_ATTRIBUTE_CI=new CaseIgnoreString("objectclass");
|
||||
|
||||
// Name of the LDAP attribute from the @Attribute annotation
|
||||
@@ -233,6 +233,7 @@ import java.util.TreeSet;
|
||||
// Reflection data
|
||||
determineFieldType(field);
|
||||
|
||||
|
||||
// Data from the @Attribute annotation
|
||||
boolean foundAttributeAnnotation=processAttributeAnnotation(field);
|
||||
|
||||
@@ -253,6 +254,7 @@ import java.util.TreeSet;
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
public String getSyntax() {
|
||||
return syntax;
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user