# Ignition changes JAR file names artificially

**URL:** <https://forum.inductiveautomation.com/t/ignition-changes-jar-file-names-artificially/17241>\
**Category:** Module Development\
**Created:** [March 5, 2018, 11:24pm UTC](https://forum.inductiveautomation.com/t/ignition-changes-jar-file-names-artificially/17241 "2018-03-05T23:24:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![byounghyun.an](https://avatars.discourse-cdn.com/v4/letter/b/9de053/32.png) [@byounghyun.an](https://forum.inductiveautomation.com/u/byounghyun.an)\
**Post date:** [March 5, 2018, 11:24pm UTC](https://forum.inductiveautomation.com/t/ignition-changes-jar-file-names-artificially/17241/1 "2018-03-05T23:24:05Z")

</div>

I made my module with a 3rd-party JAR file. The 3rd-party JAR file name is **_sapjco3.jar_** , and the JAR file is not supposed to change its name. If this JAR file name is modified, then an exception will be occurred.

But, when I install my module on Ignition, Ignition changes this jar file name **_sapjco3_** artificially like that:

_…\Inductive Automation\Ignition\temp\ **sapjco3340385287549517404.jar** _  
_…\Inductive Automation\Ignition\data\jar-cache\sapconnectorgateway\ \_\_ **2224554137** \_\_ **sapjco3.jar** _

When I run my module, Ignition loads _ **sapjco3340385287549517404.jar** _. And the exception is occurred because JAR file name is not **_sapjco3.jar_**.

How can I solve this issue?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 5, 2018, 11:43pm UTC](https://forum.inductiveautomation.com/t/ignition-changes-jar-file-names-artificially/17241/2 "2018-03-05T23:43:27Z")

</div>

I’ve seen this same issue, with this same jar, once before. You won’t be able to load it from a module.

A workaround might be to just drop the jar file into the `lib/core/gateway` folder of your Ignition install.

Relying on your own JAR file being any certain name is pretty absurd practice.

---

<div class="post-metadata">

**Author:** ![byounghyun.an](https://avatars.discourse-cdn.com/v4/letter/b/9de053/32.png) [@byounghyun.an](https://forum.inductiveautomation.com/u/byounghyun.an)\
**Post date:** [March 5, 2018, 11:59pm UTC](https://forum.inductiveautomation.com/t/ignition-changes-jar-file-names-artificially/17241/3 "2018-03-05T23:59:57Z")

</div>

I already tried the method that you mentioned. But, Ignition still loads **_sapjco38096529840247398430.jar_** of the `Ignition\temp` folder even though I drop the JAR file **_sapjco3.jar_** into the `Ignition/lib/core/gateway` folder.

Any idea?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 6, 2018, 12:06am UTC](https://forum.inductiveautomation.com/t/ignition-changes-jar-file-names-artificially/17241/5 "2018-03-06T00:06:51Z")

</div>

Right, looks like we do the same thing with the platform JARs.

Unfortunately I don’t think there’s anything else you can do here.