You are not logged in.
If I attempt to add a namespace to a tAdvancedFileOutputXML component (i.e. select a node in the talend gui from the xml tree interface, right click, then select the popup menu option "Add Name Space"), it shows the namespace in the GUI designer, but the namespace does not exist upon creation of the file.
I did a search on this issue and found some stuff about attributes with values that include "xml" in them being a bug - and I also found in the bugtracker that this was fixed in 2.2.2 or some such.
I really need to know if this is fixed or if there's a workaround - I could've sworn this worked once...
This is a serious flaw in this component if not - almost a show-stopper for us - if you can't validate an namespace, it's a real problem with security.
I understand your problem : You have to map one of your input column to the NameSpace "Related Column".
In your xmlns, you have a key and a value. The value comes from the input schema.
It's a strange behavior. It might be an interesting feature to allow a fixed value in this field rather than a value from the current row.
Last edited by mhirt (2009-01-27 21:36:53)
Thanks for the tip.
So - what you're saying is that I have to add some bogus column to the schema (maybe a context variable?) and use it as the basis for the namespace addition?
If that's the case, fairly simple to do - but really odd - I guess I need to volunteer some time to help with the documentation before i bitch too much.
Has this been fixed yet?
Yes, I test this problem on TOS3.0.0 and it works fine.