Hi,

I have a custom component using an external library.

This component was developped with TOS 3.2.2 and worked smoothly on this version.

I upgraded to TOS 4.00 and now I cannot use a job using this component without pushing the component to palette beforehand.

Indeed, if I try to use the component directly after startup, I get compilation errors on "invalid" or "non recognized" types on all the external library references. This is as the external jar was not in the classpath at compilation time.

Pushing the component to palette from Component designer seems to solve the problem but only if I put a new instance of the custom component in the job.

I guess the classpath is not correct at startup and the action of pushing to palette and putting the component in a job force it to be refreshed.

I would really like to get rid of this problem as pushing component and playing with a job to update the classpahth takes quite a long time specially if you change projects several times a day...

I miss some information on the classpath generation and the management of external librairies when component is "pushed" to palette. Is there any doc (outside TOs sources) on these points ?

Could anyone give me sone hints on how to investigate further on this problem?

Any suggestion is welcome.

Thanks,
Xavier

Last edited by xavier335659 (2010-05-13 16:26:55)