Hi team,
I am facing an error in tMSSqlRow using Talend 6.1.1. The job executes successfully by performing the query using database selected whereas i see a error in the Talend studio.
Error is: Parameter (Component List) has a value (XXXX) that doesnt exist anymore
Details about implementation: I have created a custom defined talend component which uses tMSsqlConnection component internally to create a MSSQL connection. I have checked Use a shared connection. The shared connection name is tClientAdminDBConn_1. Query is executed successfully.
Can you please tell me how to resolve this error?
Hi,
Please find attached screenshots of my job. I have created a custom component called tClientAdminDBConnection which uses tMSSqlConnection of talend. MSSql connection is successful and even query is performed successfully. Only pending issue is that Error is displayed in the Talend studio desiger view and also same error is shown in pop up message when building the job
Below is the code snippet of custom component
<%@ jet
imports="
org.talend.core.model.process.INode
org.talend.core.model.process.ElementParameterParser
org.talend.core.model.metadata.IMetadataTable
org.talend.core.model.metadata.IMetadataColumn
org.talend.core.model.process.IConnection
org.talend.core.model.process.IConnectionCategory
org.talend.designer.codegen.config.CodeGeneratorArgument
org.talend.core.model.metadata.types.JavaTypesManager
org.talend.core.model.metadata.types.JavaType
java.util.List
java.util.Map
"
%>
<%
CodeGeneratorArgument codeGenArgument1 = (CodeGeneratorArgument) argument;
INode node1 = (INode)codeGenArgument1.getArgument();
String cid1 = node1.getUniqueName();
String client_id = (String)ElementParameterParser.getObjectValue(node1, "__CLIENT_ID__");
String shared_connection_name = (String)ElementParameterParser.getObjectValue(node1, "__SHARED_CONNECTION_NAME__");
Hi
It sounds just be a display issue rather than a compilation error. It is a custom component, so I don't have a clue about the display error, I would suggest you to open a jira issue on our
bugtracker.
Regards
Shong