[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakartaee-platform-dev] [External] : Re: Standardizing new TCK packages (was:package prefixes for Jakarta Batch TCK-related classes?org.eclipse.ee4j.batch ?)
|
> On Jan 10, 2022, at 11:12 AM, Lukas Jungmann <lukas.jungmann@xxxxxxxxxx> wrote:
>
> I'm sorry but I got lost in the thread at the point where it was said that _some_ implementations are having hard times optimizing themselves. If that is the problem, then, IMHO, implementations should be fixed as they are usually those the best knowing the real "why" for what are they doing. I believe that what they are doing is not correct in 100% cases and it is possibly just a matter of time till someone files an issue for some of those corner-cases for which the "optimization" is wrong.
I started a thread in the EclipseLink list so we can talk through the potential issues I see with having application developers write code in the javax or jakarta namespace.
- https://www.eclipse.org/lists/eclipselink-dev/msg08182.html
EclipseLink isn't the only impl with special handling of these namespaces. I noticed it in CXF, OpenWebBeans and a few others. The trend seems to be it's pretty common in libraries that need to generate code or do bytecode inspection.
-David
