I’m getting this error when I first open a Window up in the Designer. It happens to Windows that have particular templates contained in them, and the errors only show on the very first open of the Windows; if I close the window and open it again, there’re no errors. Wondering what would cause this?
Any chance of a full stack trace there?
Whoops, should have done that originally!
java.lang.ClassCastException: Unable to create new interface java.awt.Paint. java.awt.Paint
at com.inductiveautomation.ignition.common.TypeUtilities$DefaultClassInitializer.createNew(TypeUtilities.java:1642)
at com.inductiveautomation.ignition.common.TypeUtilities.getInitValueForClass(TypeUtilities.java:1593)
at com.inductiveautomation.factorypmi.application.binding.AbstractPropertyAdapter.setQValue(AbstractPropertyAdapter.java:212)
at com.inductiveautomation.factorypmi.application.binding.AbstractPropertyAdapter.updateValue(AbstractPropertyAdapter.java:259)
at com.inductiveautomation.factorypmi.application.binding.ExpressionPropertyAdapter.runExpression(ExpressionPropertyAdapter.java:89)
at com.inductiveautomation.factorypmi.application.binding.ExpressionPropertyAdapter.startup(ExpressionPropertyAdapter.java:113)
at com.inductiveautomation.factorypmi.application.binding.DefaultInteractionController.startupBindings(DefaultInteractionController.java:355)
at com.inductiveautomation.factorypmi.application.binding.DefaultInteractionController.startupAdapters(DefaultInteractionController.java:360)
at com.inductiveautomation.factorypmi.application.components.template.VisionTemplate.startup(VisionTemplate.java:189)
at com.inductiveautomation.factorypmi.application.components.template.TemplateHolder.startupTemplate(TemplateHolder.java:407)
at com.inductiveautomation.factorypmi.application.components.template.TemplateHolder.onStartup(TemplateHolder.java:517)
at com.inductiveautomation.vision.api.client.components.model.AbstractVisionPanel.startupComponent(AbstractVisionPanel.java:208)
at com.inductiveautomation.factorypmi.application.components.util.ComponentVisitor$StartupVisitor.visit(ComponentVisitor.java:322)
at com.inductiveautomation.factorypmi.application.components.util.ComponentVisitor.walk(ComponentVisitor.java:91)
at com.inductiveautomation.factorypmi.application.components.util.ComponentVisitor.walk(ComponentVisitor.java:69)
at com.inductiveautomation.factorypmi.application.FPMIWindow.startup(FPMIWindow.java:357)
at com.inductiveautomation.factorypmi.designer.workspace.WindowWorkspace$DesigntimeWindowOpener.openWindow(WindowWorkspace.java:3554)
at com.inductiveautomation.factorypmi.designer.workspace.WindowWorkspace.openWindow(WindowWorkspace.java:1322)
at com.inductiveautomation.factorypmi.designer.model.navtree.WindowNode.onDoubleClick(WindowNode.java:269)
at com.inductiveautomation.ignition.designer.navtree.NavTreePanel$MouseListener$1.run(NavTreePanel.java:719)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$500(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Ignition v7.9.10 (b2018112821)
Java: Oracle Corporation 1.8.0_221
have you solved the problem? I have the same problem.
Nope, I think I still get it on some pages. I just ignore it… 
are you using the active directory in your project?
Nope. It’s something to do with colours. Doesn’t have anything to do with user security. I’m betting that it’s due to my use of client tags to store colour hex values and using them in bindings; when the page first loads, the client tags haven’t been read and therefore they’re nulls which colours don’t like
1 Like
Yes, you’re right, I just found out. I have component templates that have colors associated with tags where I have the colors stored. but in my case they are not clients tags.
I have eliminated most of those errors.
The stacktrace you originally posted should be fixed in 8.0.14 and up - can you still reproduce?