Hi Marc,
I just committed the hierarchy change.
Now, for any extRequest you can grap the value as a byte[], you just
need to cast the instance to OpaqueExtendedRequest.
On 06/01/2022 23:09, Marc Boorshtein wrote:
the PasswordModify extended request is natively supported by the LDAP
API, there is no need to cast it. The class hierarchy is the following:
[[AbstractRequest]]
^
|
+-- [[AbstractExtendedReques]]
| ^
| |
| +-- [PasswordModifyRequestImpl]
|
+-- [OpaqueExtendedRequest]
It's a bbit a pity we havn't made the OpaqueExtendedRequest class
extending the AbstractExtendedReques class, but anyway.
Right, I never want to cast an extended request to an existing class.
We're a virtual directory so we'll pass it through directly downstream
unless operated on by the user. Is there a way to disable casting to a
specific implementation? Would excluding the existing implementations
listed below force everything to OpaqueExtendedRequest?
Thanks
Marc
--
*Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE
T. +33 (0)4 89 97 36 50
P. +33 (0)6 08 33 32 61
[email protected] https://www.busit.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
