# Information object modeling - inheritance

**URL:** <https://forum.inductiveautomation.com/t/information-object-modeling-inheritance/106381>\
**Category:** Ignition\
**Created:** [May 17, 2025, 2:19pm UTC](https://forum.inductiveautomation.com/t/information-object-modeling-inheritance/106381 "2025-05-17T14:19:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tp\_gates\_mypapa](https://avatars.discourse-cdn.com/v4/letter/t/c2a13f/32.png) [@tp\_gates\_mypapa](https://forum.inductiveautomation.com/u/tp_gates_mypapa)\
**Post date:** [May 17, 2025, 2:19pm UTC](https://forum.inductiveautomation.com/t/information-object-modeling-inheritance/106381/1 "2025-05-17T14:19:24Z")

</div>

I searched on inheritance before I posted. Do the components in the palette have full inheritance like the classes of objects in RSLogix/Studio5000, the Logix engine? If I can create components, is there a framework to do so to allow full inheritance?

---

<div class="post-metadata">

**Author:** ![ryan.white](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan.white/32/73193_2.png) [@ryan.white](https://forum.inductiveautomation.com/u/ryan.white)\
**Post date:** [May 17, 2025, 4:57pm UTC](https://forum.inductiveautomation.com/t/information-object-modeling-inheritance/106381/2 "2025-05-17T16:57:16Z")

</div>

> **[Project Inheritance | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/platform/projects/project-inheritance)**
>
> Project Inheritance allows one project to inherit resources from another project. If you have project resources that you want other projects to use such as views, windows, scripts, templates, or pipelines, you can create an inheritable project...

Untouched inherited items use the base resource, as soon as you override the inherited resource, it becomes its own resource and will not be updated if you change the base(source) item.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 17, 2025, 5:15pm UTC](https://forum.inductiveautomation.com/t/information-object-modeling-inheritance/106381/3 "2025-05-17T17:15:41Z")

</div>

> [@tp\_gates\_mypapa](#):
>
> Do the components in the palette

In Vision, you can subclass components in the Java SDK. Not all components expose methods that make them easy to subclass.

Such a subclassed component would coexist with its parent in the palette--you cannot replace.

There is no component subclassing within Ignition's project hierarchy.

---

<div class="post-metadata">

**Author:** ![tp\_gates\_mypapa](https://avatars.discourse-cdn.com/v4/letter/t/c2a13f/32.png) [@tp\_gates\_mypapa](https://forum.inductiveautomation.com/u/tp_gates_mypapa)\
**Post date:** [May 17, 2025, 9:12pm UTC](https://forum.inductiveautomation.com/t/information-object-modeling-inheritance/106381/4 "2025-05-17T21:12:17Z")

</div>

Thank you for the response. It is more about explaining to learners the functionality than anything that I wanted to do. I am comparing the components to class of objects in RSLogix/Studio5000 with inheritance. I will just not breach that subject.