How Java Generics Affect PeopleCode

Does the Java "Object" return type force us into #PeopleCode/Java reflection misery? Can you "cast" Java Objects in PeopleCode? #PeopleSoft has fantastic built-in support for Java. Sometimes, figuring out how to translate between the two languages can be challenging. In this episode, we use CreateJavaObject and GetJavaClass to extend the PeopleCode API with Java and discuss how modern Java Generics affect our PeopleCode.

Sample PeopleCode:

/*
*/

[GaryFurash]

I really wish they would come up with better support for generics though.

[AlexeiTetenov]

Any chance you can update the LOG4J framework that you created for Log4J version 2? There is an overloaded method that I can't seem to get the correct syntax to reference it via reflection.

[AlexeiTetenov]

Any chance you can update the LOG4J framework that you created for Log4J version 2? There is an overloaded method that I can't seem to get the correct syntax to reference it via reflection.
This is the problematic section:
Local JavaObject &logManagerJO =
results in a "Matching constructor for class is not public."
This is correct. The LogManager is a static class where the constructor is not public.

However, when trying to instantiate the static class with
Local JavaObject &logger =
I get the following error message:
ErrorReturn-> 742 - Calling Java more than one overload matches.
I'm not sure how to create a reference to this java class when the class is static and has a private constructor.
Thanks,
-Alexei