topic Re: One more time ..... How to install custom component. in Installing and Upgrading

One more time ..... How to install custom component.

_AnonymousUser — Sat, 16 Nov 2024 14:08:01 GMT

I'm sorry bur I work with TOS 3.0.2, view Ecosystem doesn't works (behind proxy). I tried to install components with specifying directory for Telend componets but nothing happend ?
Does someone have the same pb ?
Is there a trace when Talend load new components ?
thanks

Re: One more time ..... How to install custom component.

Anonymous — Sat, 06 Dec 2008 05:55:30 GMT

Hello
Copy your new component folder and go to plugins\org.talend.designer.components.localprovider_3.0.0.r18993\components under install folder, paste your new folder, then restart your TOS.
Best regards
shong

Re: One more time ..... How to install custom component.

Anonymous — Thu, 12 Mar 2009 09:44:41 GMT

Hi Shong,
For me it is not work. I'm using TOS 3.0.2.
Regards,
Okta

Copy your new component folder and go to plugins\org.talend.designer.components.localprovider_3.0.0.r18993\components under install folder, paste your new folder, then restart your TOS.

Re: One more time ..... How to install custom component.

Anonymous — Thu, 12 Mar 2009 09:57:24 GMT

Hello Okta
What's your problem? Doesn't your component appear in palette panel?
Best regards

shong

Re: One more time ..... How to install custom component.

Anonymous — Thu, 12 Mar 2009 10:34:04 GMT

Yes, the component I copied in the suggested directory is not appear in pallete.
Regards,
Okta

Re: One more time ..... How to install custom component.

Anonymous — Thu, 12 Mar 2009 20:25:14 GMT

Hi Okta,
you could find the log file in your installation directory / workspace in the .metadata folder.
Sometimes errors in the component are logged there (for example invalid xml definition).
Bye
Volker

Re: One more time ..... How to install custom component.

Anonymous — Fri, 13 Mar 2009 02:16:35 GMT

Hello Okta
Generally, it is due to your invalid xml file if your component doesn't appear in the pallete panel, so please check your xml file.
Best regards

shong

Re: One more time ..... How to install custom component.

Anonymous — Fri, 13 Mar 2009 03:01:18 GMT

Hi Volker,
I copied tEmptyToNull folder to plugins/org.talend.designer.components.localprovider_3.0.2.r20205/components. Then I restarted TOS. This is content of .metadata/.log after I restarted.
!SESSION 2009-03-13 10:53:45.406 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY org.talend.libraries 1 0 2009-03-13 10:54:07.312
!MESSAGE 2009-03-13 10:54:07,312 INFO org.talend.repository.model.ProxyRepositoryFactory - ofhadis@gmail.com logged on test
Regards,
Okta

Re: One more time ..... How to install custom component.

Anonymous — Fri, 13 Mar 2009 07:37:13 GMT

Hi Shong,
I try add another component and it works by restarting TOS. You are right there are some setting in XML that make earlier component I add can not work.
Regards,
Okta

Re: One more time ..... How to install custom component.

Anonymous — Tue, 26 Oct 2010 09:15:26 GMT

I also experienced issue with some community components, for example tFileHttpPost, etc., which has been developed in 2008. From my log file I explored that there is for example fololowing message:
!ENTRY org.talend.libraries 2 0 2010-10-25 23:51:48.482
!MESSAGE 2010-10-25 23:51:48,482 WARN org.talend.commons.exception.ExceptionHandler - Cannot load component "tLog4J": Does not match xsd (Component.xsd)
!STACK 0
org.talend.commons.exception.BusinessException: Cannot load component "tLog4J": Does not match xsd (Component.xsd)
at org.talend.designer.components.model.ComponentsFactory.loadComponentsFromFolder(Unknown Source)
at org.talend.designer.components.model.ComponentsFactory.init(Unknown Source)
at org.talend.designer.components.model.ComponentsFactory.initializeComponents(Unknown Source)
at org.talend.repository.model.ProxyRepositoryFactory.logOnProject(Unknown Source)
at org.talend.repository.ui.login.LoginDialog$1.run(Unknown Source)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: org.talend.designer.components.model.MalformedMainXMLComponentFileException: Does not match xsd (Component.xsd)
at org.talend.designer.components.model.ComponentFileChecker.checkXSD(Unknown Source)
at org.talend.designer.components.model.ComponentFileChecker.checkComponentFolder(Unknown Source)
... 6 more
Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'DOCUMENTATION'. One of '{FAMILIES}' is expected.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at org.talend.commons.xml.XSDValidator.checkXSD(Unknown Source)
... 8 more
So I opened XML editor (I use Oxygen, but it can be done also by others.) and make changes to component XML specification file, which is part of component's folder, to meet Component.xsd requirements. The Component.xsd file could be found in my case under TIS_TE-All-r47759-V4.0.3\configuration\org.eclipse.osgi\bundles\193\1\.cp\model\, but this could differ based on which version and myabe also edition of Talend you currently use.
Hope it will help.
archenroot

Re: One more time ..... How to install custom component.

Anonymous — Tue, 26 Oct 2010 11:09:28 GMT

Hello
The XML specification file is different since version3.0, you have to define the family parameter in the xml file, not the .properties file since version3.0.
You can download this component which have been updated for the versions since 3.0.
Best regards
Shong

Re: One more time ..... How to install custom component.

_AnonymousUser — Thu, 04 Nov 2010 00:07:28 GMT

Where is the log folder for the component load?
I have a workspace/.metadata/.log but the file is not updated (last update 10/30). I have a new component that does not show in the palette and I can not find what is wrong with it.
Thanks!
Marc

Re: One more time ..... How to install custom component.

Anonymous — Thu, 04 Nov 2010 02:29:43 GMT

Hello Marc
If there don't throw any exception in the generation engine initializaition progress, there are no log written in the .log file. Normally, the problem comes from the xml file of component If it does not show in the palette. You can send it to me if you can't still find the cause.
Best regards
Shong