Java dev troubleshooting tale 🧑💻
My manager asked for help (albeit using the wrong terminology) to view the SQL generated by a #Java application he was running locally on a #JBoss AS instance via #Eclipse IDE. I explained that JBoss has a file where logging granularity for specific classes or packages can be defined, but its location depends on the version. After I inquired further, he managed to tell me the JBoss version, which was progress. I looked it up and quickly found a web page citing the specific configuration file for that version. I mentioned I wasn't sure if he'd checked already, but the page X says it's the file Y. Then I had to make guesses: if the app he's testing uses #Hibernate, he could set logging for certain two classes to
🤔 ...Did I just tell my manager to #RTFM??? 🙀
#office #dev
TRACE in that file. If it's actually Hibernate under JPA, I commented that he might tweak certain properties in persistence.xml; otherwise, it would be another file. I emphasized that this is how it works at least in the Hibernate version I know. If it does not work this way, I concluded, he (or someone else—definitely not me!) would have to search the documentation for their specific Hibernate version.🤔 ...Did I just tell my manager to #RTFM??? 🙀
#office #dev