RxJava's Observable class has plenty of methods that can be used to transform the stream of emitted items to the kind of data that you need. Those methods are at the very core of RxJava and form a big part of it's attraction. But there are other methods, that do not change the stream of items in any way - I call those methods side effect methods.
As a brief note to self, when you need to debug a chain of RxJava Observable method calls, you can use the
doOnNext method to log the current values or print them to STDOUT or STDERR with
println. Here’s an example from RxJava For Android Developers, where the debug output is logged with the Android
As a brief note to self, when you need to change Play Framework logging, such as to change it to more of a debug mode, edit the logback.xml file and add/change entries like these:
This is an excerpt from the Scala Cookbook (partially modified for the internet). This is Recipe 18.12, “Resolving Problems by Getting an SBT Stack Trace.”
This is an excerpt from the Scala Cookbook (partially modified for the internet). This is Recipe 18.13, “Setting the SBT Log Level.”
You’re having a problem compiling, running, or packaging your project with SBT, and need to adjust the SBT logging level to debug the problem. (Or, you’re interested in learning about how SBT works.)
Set the SBT logging level in your build.sbt file with this setting:
Using Akka logging is a great thing, until you need to turn it off. In short, to disable Akka logging, you need to create a file named application.conf in your SBT src/main/resources folder, and set the
loglevel to “OFF” in that file, like this:
UPDATE: These days you should put your server configurations in files in the /etc/nginx/sites-enabled directory.
As a short note, if you need to configure Nginx to serve multiple static websites out of one nginx.conf file, I have been using this approach, and it seems to work well:
If you need to turn off (disable) java.util.logging logging, adding this line of code to your
main method seems to work: