Unable to import components.xml

CloverDX Platform
1

I can’t import a custom component under Eclipse with the last release of cloverGUI (1.4):

I’ve got this error message :

“Resource Loading Error:
File does not exist.: null type”

I don’t understand because I wrote the type parameter in my xml file.

below is my xml file :

<?xml version="1.0" encoding="UTF-8"?> Finds intersection of data flows (sets) A (in-port0) and B (in-port1) based on specified key. Both inputs must be sorted according to specified key. DataRecords only in flow A are sent out through out-port\[0\]. DataRecords in both A&B are sent to specified transformation function and the result is sent through out-port\[1\]. DataRecords present only in flow B are sent through out-port\[2\].

Can someone help me please ?

Thanks.

2

Thanks for your time and good analyze of our DTD. We must update this part of ducumentation.

OtaSanek

3

Thanks for the tip. It turns out it wasn’t the “category” attribute on the “ETLComponent” tag, it was the “category” attribute on the “property” tag.

In order to determine this, I copied your DTD and my XML validator agains my copy of “components.xml” that contained my new components. I had to change both the component description and the DTD in order to parse it. The components.sml changes where mostly in the attributes classified as NMTOKEN - blanks and special characters are not permitted. In the DTD, some of the explicit lists for attributes were missing values and several of the elements that were defined as alternatives really should be optional elements. The important result of all this is I found the error that cause the component loading failure.

Mike

4

Thanks !

It works great. I also changed for the “slaveOverrideKey” property and now it works.

Thanks again.

5

Hello,
a mistake is in the “Join key” property definition. The error message is little bit misleading, but right form of this property is for now:

Look forward to new updated clover.GUI documentation.

OtaSanek

6

Hello Mike.

Error mesasge is little bit misleading, but last part says “null category”. I think, that your custom component description has not defined category.

Try something like -

<ETLComponent category=“others” …

OtaSanek