# 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:** 1\
**Showing post:** 2

<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?

---

_[View the full topic](https://forum.inductiveautomation.com/t/json-patch-in-ignition/115580)._
