on 05-03-2010 1:38 PM
Hi
Please see my screendump here <a href="http://www.sendspace.com/file/4cvsq2">http://www.sendspace.com/file/4cvsq2</a>.
I got this weird problem.
Our customer delivers and XSD that uses a GROUP as a "header" SectionH for two "subsections" Section001 and Section002.
Okay that is all good. SectionH (GROUP) is marked as 1-unbounded, so it means that SectionH can occur many times with section001 and section002.
The problem is that when importing this as an External Definition the messages created does not show up with SectionH as a header. It is as if the GROUP definition from the xsd is totally neglected?!?
BUT when looking in the generated WSDL the SectionH appears fine!!!!
Please see my screendump here <a href="http://www.sendspace.com/file/4cvsq2">http://www.sendspace.com/file/4cvsq2</a>.
The above is an example of a live problem we are having. According to the SAP docu I can find, GROUPs in XSD are supported in PI 7.11!
Our problem is that we can not change the customers XSD, it is a standard we MUST use and it is also VERY big. Since SAp claims to support GROUPS we are reluctant to change anything. Can anyone help with a sensible "SAP-explanation".
For me it looks like a SAP bug?!
Cheers
> The problem is that when importing this as an External Definition the messages created does not show up with SectionH as a header.
It is correct that the SectionH itself does not show up as element, as this is only the name of the group definition.
http://w3schools.com/schema/el_group.asp
Or is it something else, what you are missing here?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.