# JSON Patch in Ignition

**URL:** <https://forum.inductiveautomation.com/t/json-patch-in-ignition/115580>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [May 18, 2026, 1:41pm UTC](https://forum.inductiveautomation.com/t/json-patch-in-ignition/115580 "2026-05-18T13:41:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hkewalramani](https://avatars.discourse-cdn.com/v4/letter/h/e47774/32.png) [@hkewalramani](https://forum.inductiveautomation.com/u/hkewalramani)\
**Post date:** [May 18, 2026, 1:41pm UTC](https://forum.inductiveautomation.com/t/json-patch-in-ignition/115580/1 "2026-05-18T13:41:19Z")

</div>

I’m looking at adding JSON Patch support into Ignition using existing Java libraries instead of writing patch logic manually.

From what I can tell, libraries like:

- `com.github.fge:json-patch`

- `java-json-tools:json-patch`

- Jackson dependencies

could potentially work inside Ignition scripting/modules.

What’s the recommended way to import and use external JARs in Ignition for something like this?

Questions:

1. Should the JARs go into `user-lib/jars` on the Gateway?

2. Has anyone successfully used a JSON Patch library inside Perspective or Gateway scripts?

3. Is there a preferred modern library compatible with Ignition’s Java version?

Example goal would be something like:

```python
from com.github.fge.jsonpatch import JsonPatch

```

and then applying RFC 6902 patches directly in scripting.

Would appreciate any guidance or best practices from others who’ve integrated third-party Java libraries into Ignition.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [May 18, 2026, 4:38pm UTC](https://forum.inductiveautomation.com/t/json-patch-in-ignition/115580/2 "2026-05-18T16:38:37Z")

</div>

> [@How to import Java Libraries (.jar files)](https://forum.inductiveautomation.com/t/how-to-import-java-libraries-jar-files/115190/2):
>
> lib/core/{scope} is generally the quick and dirty place to do it. If you only tried lib/core/gateway, then assuming you restarted the Gateway, it would only be available in the Gateway scope (tag scripts, project scripts, etc...), so if you tried something in e.g. the Designer Script Console it wouldn't and shouldn't work. SAP JCo has its own extra issues that you can search the forum to find out about. At least in old versions, it had certain expectations about the name of the JAR file itself…

What's the actual thing you're trying to do, though?