Skip to content

Instantly share code, notes, and snippets.

package utils
import play.api.libs.json._
import xml._
object JsonXmlHelper {
def jsonToXml(jsonData: JsValue): Node = {
val xmlResult = jsonData match {
case JsObject(fields) => {
@lmserrano
lmserrano / JAXBDemo.scala
Created April 6, 2018 16:56 — forked from javathought/JAXBDemo.scala
scala + jaxb
package io.github.javathought.commons.xml
import java.io.StringWriter
import javax.xml.bind.JAXBContext
import javax.xml.bind.annotation._
import javax.xml.bind.annotation.adapters.{XmlAdapter, XmlJavaTypeAdapter}
import io.github.javathought.commons.xml.XmlTypes._
import org.apache.commons.io.IOUtils
@lmserrano
lmserrano / JAXBDemo.scala
Created April 6, 2018 16:56 — forked from javathought/JAXBDemo.scala
scala + jaxb
package io.github.javathought.commons.xml
import java.io.StringWriter
import javax.xml.bind.JAXBContext
import javax.xml.bind.annotation._
import javax.xml.bind.annotation.adapters.{XmlAdapter, XmlJavaTypeAdapter}
import io.github.javathought.commons.xml.XmlTypes._
import org.apache.commons.io.IOUtils
@lmserrano
lmserrano / 0.README.md
Created August 4, 2020 22:15 — forked from ijokarumawak/0.README.md
The simplest NiFi Wait Notify example

This flow using Wait processor to wait for the all split FlowFiles to be processed. When it runs, following log messages can be seen:

2019-04-05 10:02:58,752 INFO [Timer-Driven Process Thread-7] o.a.nifi.processors.standard.LogMessage LogMessage[id=eafe4890-0169-1000-9927-a81fbbafafc6] Processing 1/5 message for 875bd765-209d-4136-a75d-5d14241384fe
2019-04-05 10:02:58,769 INFO [Timer-Driven Process Thread-3] o.a.nifi.processors.standard.LogMessage LogMessage[id=eafe4890-0169-1000-9927-a81fbbafafc6] Processing 2/5 message for 875bd765-209d-4136-a75d-5d14241384fe
2019-04-05 10:02:58,770 INFO [Timer-Driven Process Thread-3] o.a.nifi.processors.standard.LogMessage LogMessage[id=eafe4890-0169-1000-9927-a81fbbafafc6] Processing 3/5 message for 875bd765-209d-4136-a75d-5d14241384fe
2019-04-05 10:02:58,770 INFO [Timer-Driven Process Thread-3] o.a.nifi.processors.standard.LogMessage LogMessage[id=eafe4890-0169-1000-9927-a81fbbafafc6] Processing 4/5 message for 875bd765-209d-4136-a75d-5d14241384fe
2019-04-05 10:02:5
@lmserrano
lmserrano / Reset_Slack.ps1
Created June 4, 2021 16:39 — forked from bdwyertech/Reset_Slack.ps1
Reset Slack Windows App -- Typically resolves crashing issues
# Reset_Slack.ps1
# Brian Dwyer - Intelligent Digital Services
# Fixes Slack startup crashing issues on Windows
Stop-Process -Name slack -Force -EA SilentlyContinue
Remove-Item -Path (Resolve-Path "$env:APPDATA\Slack\*") -Recurse -Force -EA SilentlyContinue -Verbose
@lmserrano
lmserrano / docker-machine-insecure-registry.md
Created July 7, 2021 11:44 — forked from SalmonKing72/docker-machine-insecure-registry.md
docker-machine: adding insecure registry configuration to an existing machine/VM

The issue

  • deployed a local docker registry container to a docker-machine VM
  • cannot push to local docker registry
  • get an error including a message similar to, "http: server gave HTTP response to HTTPS client"

The solution

  • in order to push to this local registry you need to make some modifications to your docker VM
  • open c:\users\<user-name>\.docker\machine\machines\default\config.json or ~/.docker/machine/machines/default/config.json in an editor
  • find the InsecureRegistry property and append "localhost:5000" to it
  • go to your docker terminal