Component is available for job, but not for a Route
Hello,
I have a legacy route design with custom component (for message queue connection). Now this route can be built, but I can't access properties of the custom component - message "Component not loaded" is displayed. This component is not present in Palette for Route, but I can see it palette when I edit some job. What can be done to resolve this?
You will need to find the custom component or edit the route to not use the custom component. Components for jobs are completely different to components for routes. You will not have been using the same one.
The problem is that custom component was already present in the route and functioning well. I met this problem trying to edit existing route - then I get "Component not loaded" message.
I tried to reimport this custom component into Studio and looks like it was imported, but present only on Jobs Palette. Family of this component is Connectivity / Messaging and another items of this type are visible.
Now I'm trying to activate this component in Route, as it is legacy design which worked.
After some research it seems that import of custom component is working wrong. Is there anything in component config which manages availability for Route or Job Palette?
You need to give a bit more information. For example, what is the custom component called? At the moment all I know is that a component which works in Talend jobs does not work in routes. That is how it should be.
The component itself is custom and it is analogue of cAMQP component with some extras. So I'll try to change the description:
Custom component is loaded to Talend Studio - Preferences / Talend / Components, folder with unzipped content is selected, applied.
Component is not loaded in existing route. It used to work some time ago, not sure when and why it was broken.
If I try to search for custom component on Palette - I see it for Job, and don't see for Routes, This is opposite to how it should be. When I tried to drag the component for job and build it - it was not compiled because of "from" method call - it belongs to Camel context, so can be compiled for route only, (In my understanding, I might be wrong here).
I can't provide example project here, so if anything else would help (like some logs to search for) - I'll be happy to provide.
I have been looking into this today and have used a custom component to replicate this. I haven't found a workaround for this yet, but I have raised this as a bug and have asked R&D to get back to me.
I have had some feedback from R&D about this. Can you check your {component_name}_java.xml file and look in the header. You should see something like this .....
The suspicion is that your component is missing the TYPE="CAMEL" section in the header. If it is not there, can you add it and try and load this component again?
This XML part is missing, but not mandatory. I was able to download this component by copying folder to Talend Studio installation, plugins folder. The problem is solved for now, though it seems like documentation is deprecated.
