lita | chat bot written in Ruby with persistent storage | Bot library

Credit for this answer goes to Jimmy Cuadra

The Lita handler you showed defines a route that will invoke an instance method called greeting_response when an incoming message matches. There is no instance method with that name defined, hence the "undefined method" exception. You have a method with this name defined in the other file, but a method defined at the top-level scope is not the same thing as an instance method in a class. If you want that method to be included in the Lita handler class, you should define it in a module that you include in the handler.

Difference in value displayed by excel and read by Apache POI comes from date formats that react to user language settings. From Excel:

Date formats that begin with an asterisk (*) responds to changes in regional date and time settings that are specified for the operating system.

Apache POI DataFormatter ignores these locale specific formats and returns default US format date. From Apache POI DataFormatter documentation:

Some formats are automatically "localized" by Excel, eg show as mm/dd/yyyy when loaded in Excel in some Locales but as dd/mm/yyyy in others. These are always returned in the "default" (US) format, as stored in the file.

To work around this behavior see answer to Java: excel to csv date conversion issue with Apache Poi

TL,DR;

Currently, there's no way to do that.

Reasons

• xadesj4j is based on the XAdES 1.4.1 standard. On that standard, the SigningCertificate property requires that the signing certificate is identified within the property, but doesn't state which item corresponds to the signing certificate if there is more than one certificate reference in the property. xades4j tries to use the data on KeyInfo to figure it out.
• xades4j starts by doing the core XML-DSIG/cryptographic validation (which requires the singing certificate) and only after checks each qualifying property. This means that the SigningCertificate property isn't considered when trying to identify the certificate. Maybe this could be different, specially if there's only one certificate reference in the property (the problem mentioned in the previous item wouldn't be applicable).

Ideas

1. The goal of identifying the signing certificate is to supply a X509CertSelector to CertificateValidationProvider.validate(). Without other changes, if an "empty" cert selector was supplied when KeyInfo is not present, it would mean that the CertificateValidationProvider would need to know how to identify the signing certificate. The builtin PKIXCertificateValidationProvider would fail, which is not cool. However, since this scenario currently fails, it means that the change wouldn't breaking existing apps.
2. When there is no KeyInfo, try to lookup the SigningCertificate property and if it contains a single certificate reference, use the issuer/serial in there to configure the X509CertSelector. Given the current architecture, this has the downside of accessing property data prior to the core signature verification.

I'm not a fan of any of the options. I've added a reference to this question in an existing issue also about the creation of theX509CertSelector. I'll think a bit more about this. Feel free to throw in more ideas or experiment with implementation.

XadesSigner.sign will add the signature as a child of the supplied element. Since you say you're passing ... in the string parameter, the output is as it should be.

To reproduce the output you intended, you should probably pass ... and pass the document node to the sign method (), so that the signature is appended to it. If you need more control, you can use the sign overload that allows to specify a different way of attaching the signature to the document (e.g. SignatureAppendingStrategies.lastChild)

Side note: you probably want to make the document builder factory namespace aware.

You can do this using Robot#send_messages. For example:

rows is a reserved keyword as of MySQL 8.0.2. Reserved words must be surrounded in backticks, though single quotes can work as column aliases:

The best way to go about this is to install a web server (nginx, caddy, etc.) to handle SSL termination. It should then proxy requests to the Docker instance. You can use nginx-proxy with the LetsEncrypt companion as the basic setup, although you'll need to alter the Lita systemd script to include config and environment variables (e.g., VIRTUAL_HOST, expose).

nginx-proxy listens for container changes to dynamically update its proxying, but I created systemd services for both nginx-proxy and the LetsEncrypt companion so that they would start on boot.

You can access using bracket notation