[resolved] nullpointerexception in TSO-BD 6.1 after update to context repository
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
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.
Hi, Is it working when you create a new job on your TOS-BD 6.1 without using Context group? Is there any good news after re-starting your studio? Starting from version 6.0, Talend Studio requires a JDK installation instead of JRE. Have you already checked KB article about: TalendHelpCenter:Requiring a JDK installation to build jobs starting from version 6.0? Best regards Sabrina
Yes, I was aware of the JDK requirement and it is installed (jdk 1.7). I can create new jobs with context, modify the context and have no problems. I can, starting with a clean workspace, import the 5.6 project, make modifications to jobs, build the job, execute the job all with no problem. However, when I make a change to the imported context in the repository and then propagate the changes, from that point on, every time I open one of the jobs in the designer, I get the same nullpointerexception at ContextUtils:501.
The context group in the repository has 3 environments (Development, Stage, Production) and 100 variables. Previously, in 5.6, I had added placeholder variables (new1, new2, new3...new10). After migrating to 6.1, I tested the application and it worked fine. I made a few changes for the 6.1 environment and then built the app as a standalone job. Once again, everything was fine and the standalone job executed correctly. No problems. I then decided that I needed a new variable for a new function. I changed one of the placeholder variables. I changed the name from "new10" to "VariableX" and put a default value for each of the 3 environments of "X". I propagated the change to all jobs. From that point on, every time I open a job in the designer, I get the nullpointerexception and the log entry I posted above.
OK, to test one more thing I changed the environment so that TOS-BD 6.1 would execute with Java 1.8. Started from scratch importing the project from 5.6, etc. Made the edits to the context in the repository and propagated the change. Now, the jobs open OK with no nullpointerexception. SO... perhaps the issue is related to Java 1.7 and how TOS 6.x propagates context changes.
The problem reappeared when I made a change to the context group in the repository while using Java 1.8. So, after digging a little more, it appears that Talend doesn't always update the context xml properly when there is no comment. After changing the name of a variable and propagating the change to all affected jobs, all of the jobname.item files are incorrect which causes the nullpointerexception. The attribute comment="" is missing from the line where the variable name was changed. When the comment="" is put back in, the nullpointerexception goes away.
