At least one item must exist on Schema

[Anonymous]

When I try to create Metadata File xml using the wizard, I often get the following error:
"At least one item must exist on Schema"
I must have done something wrong. Could someone help me?
Also, It takes quite long time to complete the third step of the wizard(over 10 minutes for a file of few hundred lines). Any idea why? I am doing this on a laptop with 1.8Ghz CPU and 1.5GB RAM. I am running Talend 2.2.2 on Windows XP.
Thanks in advance.

[Anonymous]

Hi
Can you show your xml file?

It takes quite long time to complete the third step of the wizard(over 10 minutes for a file of few hundred lines). Any idea why? I am doing this on a laptop with 1.8Ghz CPU and 1.5GB RAM.

You can allocate more memory to TOS by modifying the TalendOpenStudio.ini in <TOS_installation>
by default:

-vmargs
-Xms40m
-Xmx500m
-XX:MaxPermSize=128m

with 1.5GRAM, you can try

-vmargs 
-Xms512m 
-Xmx512m 
-XX:PermSize=128m 
-XX:MaxPermSize=128m

Best regards
shong

[Anonymous]

Here is the XML file. Thanks for your help.

<?xml version="1.0" ?>
- <PC-Compounds xmlns=" http://www.ncbi.nlm.nih.gov" xmlns:xs=" http://www.w3.org/2001/XMLSchema-instance" xs:schemaLocation=" http://www.ncbi.nlm.nih.gov ftp://ftp.ncbi.nlm.nih.gov/pubchem/specifications/pubchem.xsd">
- <PC-Compound>
- <PC-Compound_id>
- <PC-CompoundType>
- <PC-CompoundType_id>
<PC-CompoundType_id_cid>5353536</PC-CompoundType_id_cid>
</PC-CompoundType_id>
</PC-CompoundType>
</PC-Compound_id>
- <PC-Compound_atoms>
- <PC-Atoms> - <PC-Atoms_aid> <PC-Atoms_aid_E>1</PC-Atoms_aid_E>

To see the whole post, download it here
OriginalPost.pdf

[Anonymous]

Hi,
I use Talend open Studio 2.3.0 but I have the same problem!!
Thanks

[Anonymous]

hello,
i also have the same problem. it seems that that feature only works with highly simplified XML. if a schema is referenced (with a NS identifier) and that schema is not accessible by talend, will that cause the xml metadata function to stop working? this is a HUGE probem and is holding us up from using TOS to progress our workflows (
-c