[resolved] nullpointerexception in TSO-BD 6.1 after update to context repository

[_AnonymousUser]

I upgraded a project from Talend Platform for MDM 5.6 that had no Platform-specific components to TOS-BD 6.1 (6.0.1 has the same error).  The project jobs build and work fine with no problems.  However, after changing the name and value of a variable in the Context group in the repository and propagating the change, I get a nullpointerexception opening any job in the designer.  See the log entry below.

!ENTRY org.eclipse.ui.workbench 4 2 2015-11-16 13:21:00.127
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
!STACK 0
java.lang.NullPointerException
	at org.talend.core.model.context.ContextUtils.samePropertiesForContextParameter(ContextUtils.java:501)
	at org.talend.designer.core.ui.editor.process.ProcessUpdateManager.checkContext(ProcessUpdateManager.java:342)
	at org.talend.designer.core.ui.editor.process.ProcessUpdateManager.getUpdatesNeeded(ProcessUpdateManager.java:2407)
	at org.t

To see the whole post, download it here

[Anonymous]

Hello I have the same problem with Talend 6.1.0. I've put a description for all my context variables but I still have the NPE error.
java.lang.NullPointerException
at org.talend.core.model.context.ContextUtils.samePropertiesForContextParameter(ContextUtils.java:501)
at org.talend.designer.runprocess.ui.ProcessContextComposite.checkIsSameContextParameter(ProcessContextComposite.java:282)
at org.talend.designer.runprocess.ui.ProcessContextComposite.setProcess(ProcessContextComposite.java:178)
at org.talend.designer.runprocess.ui.views.ProcessView.refresh(ProcessView.java:603)
at org.talend.designer.runprocess.DefaultRunProcessService.refreshView(DefaultRunProcessService.java:229)
at org.talend.designer.runprocess.RunProcessService.refreshView(RunProcessService.java:187)
at org.talend.designer.core.ui.views.contexts.ContextViewComposite.refreshRelationship(ContextViewComposite.java:61) at org.talend.designer.core.ui.vi

To see the whole post, download it here
OriginalPost.pdf

[peeterm · Accepted solution]

Hi,
seems like the bug is still not fixed (TOS version 6.1.0.20151029_1337).
after adding dummy strings to all comment fields in context all works fine.