# Custom method on container does not set custom component property **URL:** \ **Category:** Ignition\ **Tags:** vision, scripting\ **Created:** [June 9, 2026, 8:47pm UTC](https://forum.inductiveautomation.com/t/custom-method-on-container-does-not-set-custom-component-property/115915 "2026-06-09T20:47:07Z")\ **Posts on this page:** 1\ **Showing post:** 3
**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:** [June 10, 2026, 12:25am UTC](https://forum.inductiveautomation.com/t/custom-method-on-container-does-not-set-custom-component-property/115915/3 "2026-06-10T00:25:57Z")
Long-standing gap in the application of Ignition's `PyComponentWrapper` everywhere it might be needed. When jython applies default wrapping to a `VisionComponent`, it doesn't end up with the attributes for custom properties and custom methods. Details here: > [@Transaction groups triggered expression item updating when trigger is false](https://forum.inductiveautomation.com/t/transaction-groups-triggered-expression-item-updating-when-trigger-is-false/17196/14): > > Ok, so I’ve been down the rabbit hole and found Ignition’s (undocumented) PyComponentWrapper. I haven’t deciphered it enough to be sure, but it seems to be invoked only for particular situations, based on the string constants in the class file (like “getComponent” and “getComponents”). To play with this, I constructed a conversion adapter like so: public class PyComponentAdapter implements PyObjectAdapter { public PyComponentAdapter() {} @Override public boolean canAdapt(Object jObj) { … TL/DR: Install my Integration Toolkit to get fully automatic wrapping. If you cannot do that, use the `PyComponentWrapper` manually. --- _[View the full topic](https://forum.inductiveautomation.com/t/custom-method-on-container-does-not-set-custom-component-property/115915)._