# Adding java custom classes to Ignition

**URL:** <https://forum.inductiveautomation.com/t/adding-java-custom-classes-to-ignition/15202>\
**Category:** General Discussion\
**Tags:** ignition79, sdk, scripting\
**Created:** [August 30, 2017, 3:06pm UTC](https://forum.inductiveautomation.com/t/adding-java-custom-classes-to-ignition/15202 "2017-08-30T15:06:37Z")\
**Posts on this page:** 1\
**Showing post:** 18

<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:** [April 4, 2018, 7:47pm UTC](https://forum.inductiveautomation.com/t/adding-java-custom-classes-to-ignition/15202/18 "2018-04-04T19:47:31Z")

</div>

I just unzipped the jar file for that version and looked.

> [@brandon1](#):
>
> Also, If I imported the classes I wanted in a scripting module, would they be available to the client and designer then?

You're going to run into the same potential conflict as long as the Reporting module is installed. You've hit a weird corner case in the architecture of the Client and Designer and its flat class path.

If you loaded POI in the Gateway scope and all your interactions with the library took place there you'd be okay.

---

_[View the full topic](https://forum.inductiveautomation.com/t/adding-java-custom-classes-to-ignition/15202)._