On 07/05/2020 15:07, Shawn McKinney wrote:
On May 6, 2020, at 1:47 PM, Stefan Seelmann <[email protected]> wrote:
Hi Shawn,
whoops, I hope you didn't feel offended, that wasn't my intention.
I was not offended Stefan. We’re just a couple of old timers, swapping
stories. :-)
I wasn't either reading Shawn mail as a reaction of an offended
Kansasian/Arkansasian. Rather trenches memories !
The code doesn’t lie. It is what it is.
I can absolutely feel with you. When browsing the Studio code there is
no class without warning where deprecated APIs (especially from Eclipse
framework) are used. And even if we migrated from JNDI to LDAP API,
there are still places where JNDI classes are used as it's heavy
interweaved. The worst part for me is that I think I spend 80% of the
time with changes to keep it running on new Eclipse and Java versions.
Studio’s a big program. It would be a huge effort to convert to the ldap API.
It has already been converted. There are certainly some place here and
there that use javax.naming.directory.SearchControls, but that's it.
Not sure it would be worth that effort.
The effort is past us already :-)
Working code wins. Perhaps one day, someone will volunteer. Would be a great
learning project.
Actually, it's a win, because we have had frequent issues with JNDI when
bumping up Java versions (like, the internal implementation changed,
causing some tests failure - ok, granted, it's because our tests where
wrongly written -)
On Fortress, we need to get on the LDAP API 2.x branch. Even that relatively
small task has been in the backlog for over a year.
Indeed :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
