Hi Martin, the good news: to fix your inital problem with the search dialog is very easy to fix, I'll do it immediately :-)
The other problem that Oracle OID is not standard conform is another story. In fact Studio fails to read the schema from OID. To fix this would take much more time, we would need to write a separate schema parser just for OID. Kind regards, Stefan Martynas Brijunas wrote: > Hi Alex, > > The fact that the DS is used in various environments is a testament to > the versatility and quality of the code. Take any OS, plug DS into > Eclipse and you have a first class LDAP browser. I would hate to give > up DS just because I have to deal with OID. I simply have not found a > better LDAP tool. > > The open source is famous for circumventing various obstacles imposed > by commercial vendors - Oracle including. > > Best regards, > Martin > > 2008/8/27 Alex Karasulu <[EMAIL PROTECTED]>: >> On Wed, Aug 27, 2008 at 8:20 AM, Emmanuel Lecharny <[EMAIL PROTECTED]>wrote: >> >>> Martynas Brijunas wrote: >>> >>>> Hi, >>>> >>>> I came across a proble today and not sure if this is a feature, or a bug. >>>> >>>> I am using DS to connect to our Oracle OID server. Running a search, >>>> getting the results I expect to get. The problem starts when I want to >>>> select which attributes to display. If I want to display "user_id", >>>> >>>> >>> Underscores are not valid in an attributeType : >>> >>> attributetype = oid >>> oid = descr / numericoid >>> descr = keystring >>> numericoid = number 1*( '.' number ) >>> keystring = leadkeychar *keychar >>> leadkeychar = ALPHA >>> keychar = ALPHA / DIGIT / '-' >>> ALPHA = %x41-5A / %x61-7A ; "A"-"Z" / "a"-"z" >>> DIGIT = %x30 / LDIGIT ; "0"-"9" >>> >>> >>> (RFC 4512) >>> >>> I'm sorry that Oracle is not LDAP compliant... >>> >>> >> That's hilarious. My recommendation to the user is to get the hell off of >> OID fast instead of expecting the tooling to support it's flaws. My >> experiences with OID have been utterly disastrous. >> >> Alex >>
