You are not logged in.
Ok, cool, thats very helpful.
Also, what if the component we want to install isn't compatible with our version of the studio?
Like, I'm using TIS 2.4.1, and would like to install tFTPList (http://www.talendforge.org/ext/extensio … php?eid=54), but thats only compatible up to version 2.4.0 of TOS, so its not showing up in my list...
And, are ecosystem components ever added into releases of TOS and TIS? Because, it'd be kind of a pain to install and use a component from the ecosystem and then have it not work when you update your version of the studio.
There is some component visible in ecosystem on site and not visible in My Studio when I open the ecosystem tabs
For example TFTPList doesn't visible in my ecosystem into the studio
There is a reason for that ?
By the way I'm using Talend Enterprise edition
I have to admit that I haven't take a look at the new feature concerning the download of community components. But as you Jessica I see a major problem that Talend could neither assure that a component would behave like it's description nor would work with any further releases of TOS (unless there are no changes to the interface to the generator or the structure of the generated code).
Even if they would analyze the component code it should be problematic to change its behavior or fix bugs.
So using a community component is not free of risks. I think this is point should be in mind if you use any community component.
I don't know what Talend is thinking about this point (I'm sure they have thought much about it). Using a component which is manually downloaded is "more extraordinary" then "just use it". Independent hereof I think it is the right decision to integrate it.
And to richiesgr: If I understand it right, the component defines a compatible version ot TOS. Did you check that?
Has anyone looked at it? My 2.4.2 Item list only shows 2 items, and the 3.0 complains that "Could not create the view: org/talend/designer/components/ecosystem/ui/views/EcosystemViewComposite$BeanPropertyAccessorsAdapter"
Has anyone looked at it? My 2.4.2 Item list only shows 2 items
Yes, it's a problem, because only a few components are compatible with 2.4.2 when 2.4.2 is just available. In 3.1 we will improve the version filtering system so that when selecting "3.0", you will have all components compatible with 3.0.x Talend Open Studio releases.
and the 3.0 complains that "Could not create the view: org/talend/designer/components/ecosystem/ui/views/EcosystemViewComposite$BeanPropertyAccessorsAdapter"
Does the problem still exists with TOS 3.0.2 ?
I updated my component meta data so it is usable in 3.0.* (after doing some tests).
I think this is something what every component developer should do.
Additional I pointed out the "support-problem" for this components in my last post. To give some more transparency I created a new group in the component list ("Community") and add / moved my component there. So someone who would use this component can easily see that this is a community and not a official TOS-component.
What does the community think about this? Should we talk to define some "community-standards"?
^^ I agree somewhat. It would be a good idea until you have many "community" components. Maybe we could create the sub-directory structure like the TOS-components?