asked on
Remove all the occurrence of a element from xsd using java
Can I get a sample java program which scans a folder for all the xsd and then
1. Removes the <choice> </choice> element from all the xsd
2. When there is a <choice> element could we check that the immediate parent element is <sequence> or not .
If its not there then wrap it by <sequence> </sequence> element.
I have attached the sample xsd .
Please help.
CMA.xsd
1. Removes the <choice> </choice> element from all the xsd
2. When there is a <choice> element could we check that the immediate parent element is <sequence> or not .
If its not there then wrap it by <sequence> </sequence> element.
I have attached the sample xsd .
Please help.
CMA.xsd
XMLJavaJava EEWeb Development
Last Comment
awking00
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Given your sample xsd, what would you want it to look like upon completion?
hi awking, the specification is in the question
- choice to sequence unless already wrapped in sequence then remove
that is exactly what the XSLT does
- choice to sequence unless already wrapped in sequence then remove
that is exactly what the XSLT does
Geert Bormans,
>>the specification is in the question<<
It's just that the specifications weren't that clear to me. If the specifications were shown as follows:
Remove all <choice><\choice> elements with an immediate parent element of <sequence>.
Where there is no immediate parent element of <sequence>, convert any <choice> element to a <sequence> element.
I wouldn't have any issue. I just thought that seeing a final example of the output would confirm the requirements for me. I also think your xslt solution is the best way to go.
java domain,
Do you still need code which does the folder scanning to retrieve the xsds?
>>the specification is in the question<<
It's just that the specifications weren't that clear to me. If the specifications were shown as follows:
Remove all <choice><\choice> elements with an immediate parent element of <sequence>.
Where there is no immediate parent element of <sequence>, convert any <choice> element to a <sequence> element.
I wouldn't have any issue. I just thought that seeing a final example of the output would confirm the requirements for me. I also think your xslt solution is the best way to go.
java domain,
Do you still need code which does the folder scanning to retrieve the xsds?
(I think the smart way to perform such a task is using XSLT by the way)