You saying the call to the SP from the client must now use a ServerEntry object?
Alex On Jan 18, 2008 9:35 AM, Ersin Er <[EMAIL PROTECTED]> wrote: > Hmm.. > > This effects the client side. So SPs at the client side need to be > written SPs with ServerEntry. My intent was using JNDI as much as > possible but if this is the way we need to go then OK. (Well, we also > have LdapDN used in SPs.) > > On Jan 18, 2008 4:23 PM, Emmanuel Lecharny <[EMAIL PROTECTED]> wrote: > > Hi guys, > > > > I wanted to emphasis the fact that I have modified the StoredProcedure > > to use only ServerEntry. This has an impact on the existing SP > > (BackupUtilitiesSP) : > > > > public static void backupDeleted( LdapContext ctx, LdapDN > deletedEntryName, > > LdapDN operationPrincipal, > > ServerEntry deletedEntry ) > > > > instead of : > > > > public static void backupDeleted( LdapContext ctx, LdapDN > deletedEntryName, > > LdapDN operationPrincipal, > > Attributes deletedEntry ) > > > > If someone has defined some SP using Attributes, he will get some awfull > > exception. > > > > I'm not sure that it's the best solution ever, and that we could not > > find a better way to go (like implementing some kind of automatic > > conversion from ServerEntry to Attributes), but at least, it works ! > > > > This mail is to let you think about the consequences of my modification. > > I'm waiting for further ideas on the subject, as I don't have the best > > insight on this piece of code. > > > > So, wdyt ? > > > > -- > > -- > > cordialement, regards, > > Emmanuel Lécharny > > www.iktek.com > > directory.apache.org > > > > > > > > > > -- > Ersin Er >
