Thanks. I will write a bug in PAXLOGGING soon.
Version 1.11.3 doesn't run on Payara 5.192 (different OSGi version, maybe?). Version 1.10.4 runs, but has the same issue I reported. I downloaded 1.10.4 and swapped the order of the generic parameters to match the original code (i.e., I made key=Logger, value=String). When I did that, my logging worked properly when I restarted the domain. Even with all loggers being stored in a single map in the Activator in 1.11.3, I'll run into the same issue I saw with the actual 1.10.4. When a second logger is registered in that global map with a name that already exists, the first logger will be lost, and won't get the TrackingLogger when the Activator starts up. I am still trying to run the tests for 1.11.3. I need to configure a few things in my system for that. When I write a bug, I will attach a modified unit test that exhibits the behavior that I am seeing. -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ops4j/9108d4a5-43cf-45da-ac17-feefe3b56ccc%40googlegroups.com.
