# DeveloperModuleLoadingServlet under Ignition 8.3? **URL:** \ **Category:** Module Development\ **Tags:** ignition83\ **Created:** [January 4, 2026, 4:45pm UTC](https://forum.inductiveautomation.com/t/developermoduleloadingservlet-under-ignition-8-3/113062 "2026-01-04T16:45:25Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![mpderbec](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@mpderbec](https://forum.inductiveautomation.com/u/mpderbec)\ **Post date:** [January 4, 2026, 4:45pm UTC](https://forum.inductiveautomation.com/t/developermoduleloadingservlet-under-ignition-8-3/113062/1 "2026-01-04T16:45:25Z")
Does this deployment facility still work in Ignition 8.3? The Gradle code I have (which replicates the Gradle code from [https://github.com/inductiveautomation/ignition-module-tools](https://github.com/inductiveautomation/ignition-module-tools/blob/4fd236ab99605f165c610000eae27b3d13e60f92/gradle-module-plugin/src/main/kotlin/io/ia/sdk/gradle/modl/task/Deploy.kt)) works under Ignition 8.0/8.1 but not under 8.3. ---
**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:** [January 4, 2026, 4:58pm UTC](https://forum.inductiveautomation.com/t/developermoduleloadingservlet-under-ignition-8-3/113062/2 "2026-01-04T16:58:35Z")
No, it’s gone. Similar functionality that uses the API could be added to the plugins or written as custom Gradle build script. > [@Issue Upgrading Third Party Modules](https://forum.inductiveautomation.com/t/issue-upgrading-third-party-modules/111257/4): > > I don't think anything is currently planned but it doesn't hurt to ask. We don't use the Maven or Gradle plugins so the incentives aren't exactly aligned when it comes to improving the dev experience using them. ---
**Author:** ![mpderbec](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@mpderbec](https://forum.inductiveautomation.com/u/mpderbec)\ **Post date:** [January 4, 2026, 5:07pm UTC](https://forum.inductiveautomation.com/t/developermoduleloadingservlet-under-ignition-8-3/113062/3 "2026-01-04T17:07:31Z")
Thanks, I’ve added a comment to [this open issue](https://github.com/inductiveautomation/ignition-module-tools/issues/69#issuecomment-3708254897) expressing support for bringing it back. ---
**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:** [January 4, 2026, 5:10pm UTC](https://forum.inductiveautomation.com/t/developermoduleloadingservlet-under-ignition-8-3/113062/4 "2026-01-04T17:10:51Z")
It’s probably going to happen when somebody from the community PRs it. ---
**Author:** ![mpderbec](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@mpderbec](https://forum.inductiveautomation.com/u/mpderbec)\ **Post date:** [January 4, 2026, 5:16pm UTC](https://forum.inductiveautomation.com/t/developermoduleloadingservlet-under-ignition-8-3/113062/5 "2026-01-04T17:16:16Z")
My hope would be to bring back the servlet (which would require IA personnel), disable it by default, enable it via ignition.conf. Then no one in the community needs to figure it out and it’s officially supported. It was mentioned in the GitHub issue that this was “discussed endlessly in the forums and at ICC” – I’m not finding much in the forums, maybe someone could provide a link. I’m thinking maybe security is not the only issue that caused it to be removed. ---
**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:** [January 4, 2026, 5:19pm UTC](https://forum.inductiveautomation.com/t/developermoduleloadingservlet-under-ignition-8-3/113062/6 "2026-01-04T17:19:03Z")
We're not bringing back the servlet because there should be equivalent functionality in the Open API. The thing discussed "endlessly" was the removal of module hot loading. The servlet removal was just a consequence of that + the new API being available. ---
**Author:** ![mpderbec](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@mpderbec](https://forum.inductiveautomation.com/u/mpderbec)\ **Post date:** [January 4, 2026, 5:24pm UTC](https://forum.inductiveautomation.com/t/developermoduleloadingservlet-under-ignition-8-3/113062/7 "2026-01-04T17:24:46Z")
OK thanks. ---
**Author:** ![mpderbec](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@mpderbec](https://forum.inductiveautomation.com/u/mpderbec)\ **Post date:** [January 4, 2026, 5:29pm UTC](https://forum.inductiveautomation.com/t/developermoduleloadingservlet-under-ignition-8-3/113062/8 "2026-01-04T17:29:08Z")
Am I correct in assuming that using the API to load a new version of your module will require a subsequent gateway restart? (If so then there’s nothing to be gained in writing a new Deploy script.) ---
**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:** [January 4, 2026, 5:31pm UTC](https://forum.inductiveautomation.com/t/developermoduleloadingservlet-under-ignition-8-3/113062/9 "2026-01-04T17:31:59Z")
Yes, that's the removal of module hot loading. There is no solution that won't involve a gateway restart, even if we brought back the servlet. The servlet only did what those replacement APIs can do - install the module. ---
**Author:** ![mpderbec](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@mpderbec](https://forum.inductiveautomation.com/u/mpderbec)\ **Post date:** [January 4, 2026, 6:05pm UTC](https://forum.inductiveautomation.com/t/developermoduleloadingservlet-under-ignition-8-3/113062/10 "2026-01-04T18:05:05Z")
OK thanks– then yes I don’t think there’s any point (at least in my case) to using the APIs. I can just as easily restart the agent with the scripts I have. Thanks for all the info. ---
**Author:** ![bmusson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmusson/32/87530_2.png) [@bmusson](https://forum.inductiveautomation.com/u/bmusson)\ **Post date:** [January 4, 2026, 8:15pm UTC](https://forum.inductiveautomation.com/t/developermoduleloadingservlet-under-ignition-8-3/113062/11 "2026-01-04T20:15:14Z")
> [@Kevin.Herron](#): > > It’s probably going to happen when somebody from the community PRs it. Boo, but understandable. I think it might be better as a separate Gradle plugin. Building a module (i.e. the existing plugin) is a separate concern from deployment, which is what the new API is all about. ---
**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:** [January 4, 2026, 10:08pm UTC](https://forum.inductiveautomation.com/t/developermoduleloadingservlet-under-ignition-8-3/113062/12 "2026-01-04T22:08:04Z")
Does Claude count as part of the community? This Gradle task seemed to work with the Perspective component example from the SDK: [deployModuleTask.kts · GitHub](https://gist.github.com/kevinherron/d795b72fbfdf9121705d8e9c6e7bbc41) ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [January 4, 2026, 11:30pm UTC](https://forum.inductiveautomation.com/t/developermoduleloadingservlet-under-ignition-8-3/113062/13 "2026-01-04T23:30:19Z")
Depends if Claude can attain Level 4 in the forums?