LogFilter | Simple Android library which filters Logs

See here :

setUrlPatterns

public void setUrlPatterns(Collection urlPatterns)

Set the URL patterns that the filter will be registered against. This will replace any previously specified URL patterns. ...

a variant of this method (with more precise documentation):

addUrlPatterns

public void addUrlPatterns(String... urlPatterns)

Add URL patterns, as defined in the Servlet specification, that the filter will be registered against.

...(searching;) :

• => Servlet Spec
  • => (Latest) 3.1.final:

12.2 Specification of Mappings

In the Web application deployment descriptor, the following syntax is used to define mappings:

• A string beginning with a / character and ending with a /* suffix is used for path mapping.
• A string beginning with a *. prefix is used as an extension mapping.
• The empty string ("") is a special URL pattern that exactly maps to the application's context root, i.e., requests of the form http://host:port//. In this case the path info is / and the servlet path and context path is empty string ("").
• A string containing only the / character indicates the "default" servlet of the application. In this case the servlet path is the request URI minus the context path and the path info is null.
• All other strings are used for exact matches only.

If the effective web.xml (after merging information from fragments and annotations) contains any url-patterns that are mapped to multiple servlets then the deployment must fail.

So to your core question:

Is there a better way to do this instead write List.of("/hello", "/hello/")?

Nope(, sorry), not with Servlet <=3.1. "hello", "hello/" would be two exact matches according to this specification. (And List.of(few, ..., items) is "quite cool"/up-to-date/immutable!;))

Use ${data.name} for the command step or @data.name@ for script step. I made a basic example that gets the value from a JSON file.

Rundeck job definition:

This error should go away in the future after https://github.com/web3j/web3j/pull/1495 solving https://github.com/web3j/web3j/issues/1486 (should be next version after 4.8.7)

In short: JSON RPC error was no visible on web3j level.

To analyze issue like that run program with log level debug to see JSON RPC messages.

I think logging the response should be done in debugging mode only and really can be done at your service API (by using DI interception). That way you don't need to use IActionFilter which actually can provide you only a wrapper IActionResult which wraps the raw value from the action method (which is usually the result returned from your service API). Note that at the phase of action execution (starting & ending can be intercepted by using IActionFilter or IAsyncActionFilter), the HttpContext.Response may have not been fully written (because there are next phases that may write more data to it). So you cannot read the full response there. But here I suppose you mean reading the action result (later I'll show you how to read the actual full response body in a correct phase). When it comes to IActionResult, you have various kinds of IActionResult including custom ones. So it's hard to have a general solution to read the raw wrapped data (which may not even be exposed in some custom implementations). That means you need to target some specific well-known action results to handle it correctly. Here I introduce code to read JsonResult as an example:

queryString = queryString.equals(null) ? "" : "?" + queryString; is incorrect.

SUGGESTED ALTERNATIVE:

Yes, exactly, if all your log lines look exactly the same, I would leverage the dissect filter. A pattern like this one should do:

a setup that might work better is that you have a solution with two projects. Project1 is the webapp BUT PROJECT2 is a library.

Now when you get an exception on project1 you can call the class/function what you might need in project2 and log the information.

future projects (3,4,...etc) can still reference project2 for logging purposes.

Request Body is consumed and not available in the OnActionExecuted, I do it like this,

Read The Request Body and Store it HTTPContext

Next time, when you want to know the JDBC version, just do "java -jar ojdbc8.jar". Also, as suggested, it is better to use the latest driver. If you have atleast JDK8 then you can use 19.7 even when your database is 12c. You can get JDBC drivers from [Central Maven] or can download them from here.