You're welcome. And maybe if we had kept our code and dependencies up-to-date, the problem would have been noted 4 years ago when the "adding generics" change was first made. ;)
Monica On Friday, January 3, 2020 at 10:50:46 AM UTC-5, Grzegorz Grzybek wrote: > > Hello > > I'm glad it worked! > > *Thank you very much. I spent many hours trying to figure out what was >> wrong with my updated POM files and Payara5 deployment before I finally >> realized that the problem was with Pax Logging, not with my own code. I am >> glad you were able to fix this and make a new official release of 1.10.x >> before we released our code for running on Payara5.* >> > > Thank *you* for such detailed and precise analysis! Who'd have thought > that "adding generics" will cause such problems ;) > > regards > Grzegorz Grzybek > > pt., 3 sty 2020 o 16:44 Monica Ron <[email protected] <javascript:>> > napisał(a): > >> I downloaded the pax-logging-api-1.10.5.jar and >> pax-logging-log4j2-1.10.5.jar from Maven Central, and deployed them in my >> Payara glassfish/modules/autostart directory. >> >> Now when I start Payara with the wars already deployed, it is properly >> connecting to the pax-logging, and is respecting my configuration in >> org.ops4j.pax.logging.cfg . If I stop the domains and restart, the >> configuration is immediately taken into account, and I don't have to >> re-deploy my wars with pax-logging already activated (as mentioned in my >> bug report above, I had to do a re-deploy with pax-logging 1.10.2 and >> 1.10.4). >> >> The stack traces also get printed correctly now with 1.10.5 (as I >> mentioned in the thread related to that). >> >> My problems seem to be solved. I'll let you know if I find anything else, >> but it seems good for now. My code uses Log4J2 API directly, and the >> third-party code I use (such as Mongo, Dozer, and Spring) use SLF4J and JCL >> Logging. >> >> Thank you very much. I spent many hours trying to figure out what was >> wrong with my updated POM files and Payara5 deployment before I finally >> realized that the problem was with Pax Logging, not with my own code. I am >> glad you were able to fix this and make a new official release of >> 1.10.x before we released our code for running on Payara5. >> >> Have a great day! >> Monica >> >> -- >> -- >> ------------------ >> OPS4J - http://www.ops4j.org - [email protected] <javascript:> >> >> --- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ops4j/9fb4447d-3a87-4215-83ac-f5cd0078744a%40googlegroups.com >> >> <https://groups.google.com/d/msgid/ops4j/9fb4447d-3a87-4215-83ac-f5cd0078744a%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- -- ------------------ 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/40b39c69-10f0-497e-9660-5a446d2cab0c%40googlegroups.com.
