Re: [solved] mysterious LDAP problem and "why doesn't EOAdaptorDebugEnabled log LDAP too?"
Re: [solved] mysterious LDAP problem and "why doesn't EOAdaptorDebugEnabled log LDAP too?"
- Subject: Re: [solved] mysterious LDAP problem and "why doesn't EOAdaptorDebugEnabled log LDAP too?"
- From: Benjamin J Doherty <email@hidden>
- Date: Sat, 15 Oct 2005 21:46:17 -0500
On Oct 14, 2005, I wrote:
I've done some more experimentation and figured out this. If an
entry which does not already have that attribute
(homePostalAddress) defined is loaded by EOF, that attribute can be
created and saved. No error. However, if I work with an entry
that has that attribute, I cannot save it. It doesn't matter
whether I change that attribute or not, because EOF wants to use
that attribute for locking. However, even if I chose not to use
that attribute for locking, I still need to have the power to edit
that attribute.
It's the locking that is causing my problem. I was too distracted by
the newness of EOF and LDAP to realize that some value types are
difficult to compare for locking purposes. So the new rule is that I
can't lock on "postal address" syntax attributes. I probably can
only lock on directory strings.
Cheers,
Benjamin in chicago.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden