The drawback is a necessity to loop through all SeverPlatformDetectors (and we don't know how expensive their checkPlatform calls might be).
Alternatively "websphere" word in a package name is a good reason to call WebSpherePlatformDetector right away.
If it's a standard JSE classloader -> NoPlatform right away.
Thanks,
Andrei
----- Original Message -----
From: curtisr7@xxxxxxxxx
To: eclipselink-dev@xxxxxxxxxxx
Sent: Wednesday, December 17, 2014 2:54:19 PM GMT -05:00 US/Canada Eastern
Subject: Re: [eclipselink-dev] Adding extension points to EclipseLink
That is the beauty of the last patch I posted. For each app server we cam do what makes the most sense.
From a WebSphere point of view, I wouldn't look at the classloader class name as those classes are internals and are subject to change at any time. Using some sort of a defined API/SPI/something is the ideal solution. The two WebSphere mechanisms (system prop and a static class) I used in the patch are documented and can't go away / change.
Thanks,
Rick