XML Schema Element any

Is there any workaround or planned support for the XML any tag in future for PI 7.1?

We have a situation where a sending system is sending a message which conforms to a schema which includes an <xs:any minOccurs="0"/> element. I have access this XSD so could (in theory) create a PI message type. However, the message type can't handle the <any> element - when designing the mapping you don't have access to the elements which could be replaced into the <any> element.
Does any one have ideas, work arounds, to handle source messages whose XSD contains an <any> element?

Similar Messages

How to bind data from script created variable to embed element of XML schema (xsd) in "Data View"

Hi, i have got another problem with livecycle designer scripting.
I have got script line which is defining of string variable:
var aaa = "this is my string";
and i have got embed XML schema like this (it`s only short part of whole file):
... xs:element name="bbb" type="xs:string"/ ...
After saving data to XML i would like to get "this is my string" as a value of my "bbb" XML element.
To save this data i`m using submit button which is connect with submit.php file on my server.
How to connect script created variable and embed XML schema element which is present on my "Data View" tab.
Please help me a bit becouse i don`t know even where to search answer of it...
Of course i know possibilities to create fake unvisible text field object and bind it with 'bbb' and than put "this.rawValue = aaa" to connect those two variables but i think that is not a good idea to solve it in that way. It`s too primitive

i solve it, i should write this:
xfa.datasets.data.bbb.value = aaa;

XML Schema binding - dynamic form

I am new to Designer and XML. I have been given a basic interactive form and have persevered for a couple of (often frustrating) weeks to extend its functionality to link to an xml schema and provide for dynamic record creation. Unfortunately I am still having problems when adding new instances of subforms. I have a main form for reporting issues. Underneath it there are major components on a subform (can be multiple major components for each issue) and under major components are sub-components (can be multiple sub-components for each major component) on a child subform of major. I can add and delete instances of the subforms for both levels of records. I have created an xml schema based on the form since it already existed, and so the form fields have not inherited properties from the schema. However, I have bound the fields in the form to the xml fields through a data connection. The schema basically looks as follows (bot not literally the same as you will see from the tags): <element complextype issue> <element issueId string/> ... ... <element complextype majorcomponent unbounded> <element majcomponentname string/> ... <element complextype subcomponent unbounded> <element subcomponent string/> <element quantity string/> ... ... </element> </element> </element> My problem is as follows: When I add an instance of a sub-component or major component subform, the first new instance appears to work correctly. However, every subsequent one inherits the values of the previous record and when it is changed, it changes the values of existing fields of the same name but of a different node. When I change each element in the xml schema to "unbounded", the forms appear to work properly but the values are then not nested correctly in the outputted xml data file (many records will appear under one sub-component, for example, when a new sub-component should be added for each). I suspected my problem might be that the "unbounded" property in the schema of the major component and sub-component elements are not linked to the Designer form because the major component and sub-component subforms are not bound to the xml schema. The reason they are not bound is because if I bind the subform, the first element, major/sub component name as applicable, loses its binding. I am sorry if this doesn't make any sense but I am hoping that someone might recognise the problem I am talking about as it is really creating much bother. Thanks.

Thanks Justin for the reply. Unfortunately I can't explain exactly what was happening because I didn't keep sufficient notes and now the form is behaving differently. You are right in that when I bind the subform to the xml schema element, child fields do change their bindings from a full to a relative path. I had seen this before on all except the first field on a subform, which had losts any binding reference at all.
I finally gave up on the schema and bound the forms to sample xml data. This fixed my problem. Now (several days later), I have revisited the problem and deleted my data connection to the xml file to connect to the schema once again. I am quite sure I have not changed the schema at all, nor the form, but for some reason it now appears to work correctly.
I will continue to work with it, once again but thanks very much for your interest.

Using xml schema problem (SAP MDM 7.1 Syndicator)

Good day !
I try to syndicate directory which correspond to some xml-schema and I have a problem.
I want to syndicate data from hierarchy table which have one field which have a type like lookup <Flat> (multivalued).
In XML-schema element "DEF_PRODUCT" and "DEF_PRODUCT_CODE" - attribute presents hierarchy table.
"CREDIT_PRODUCT" and childs presents linked flat table.
According idea and business rules I must get the result like this: each "DEF_PRODUCT" have N-"CREDIT_PRODUCT". One - to- many.
But when I set up all map completely and look to xml result file I start to be disappointed.
XML result file approximately must be like this:
<DEF_PRODUCT>
 <CREDIT_PRODUCT/>
 <CREDIT_PRODUCT/>
 <CREDIT_PRODUCT/>
</DEF_PRODUCT>
but in result I have all <CREDIT_PRODUCT> in one node and child attributes.
I attach 3 pics which explain my situation.
xml-schema :[http://xmages.net/storage/10/1/0/6/3/upload/42ca6ca8.jpg]
field mapping: [http://xmages.net/storage/10/1/0/6/a/upload/bbbc09f2.jpg]
example: [http://xmages.net/storage/10/1/0/c/c/upload/817b0e23.jpg]
Anybody can help me?
About software : SAP MDM 7.1 (7.1.04.139)
P.S: My problem can be resolved succesfully if I will use 1 <main> table and 1 <qualified flat> table.
 But in my case I must use hierarchy - structure because it most usable for business - users

>
Christian Heuer wrote:
> Hi,
>
> now I understood and you really have got a point here. But the question is whether you need key mapping then on the remote key level with a tuple anymore. If yes, you won
>
> Best regards
> Christian
If SAP MDM will present many opportunities to me I will be very glad.
I repeat I must get output xml which have the pair like "RemoteKey"="RemoteSystem" in tuple subnode.
In tuple, after your advices.
Ideally, Syndicator must present to each user ability to choose pair "RemoteKey" = "RemoteSystem" in each subnode like <LookUp> table in root (look at my example pic).
Imagine you have one root table and N-linked <lookup> tables.
Tree like this :
<main tbl>
<subtbl1/>
<subtbl2/>
<subtbl3>
 <childtbl1/>
 <childtbl2/>
</subtbl3>
</main tbl>
It's dangerous to deprive SAP MDM user to select pair "RemoteKey" = "RemoteSystem" from ROOT to ALL and LAST LEAF in abstract hierarchy. How do you think ?
Now, I haven't abilities to solve my problem using standard resources. Really ?

Using XSDBuilder to build XML Schema objects

I want to parse an XML document using an XML Schema Definition that I provide explicitly to the parser, rather than one identified in the document being validated. It appears that I can create an XML Schema object using XSDBuilder, and give it to the XML parser using XMLParser.setXMLSchema(). The problem is that XSDBuilder.build() wants an XSD system ID that is a file, and I want to retrieve XSD documents from non-file-based stores. Ideally, I'd like to give the builder a stream containing the XSD, or barring that, provide a custom entity resolver that it can use. Any ideas how to go about doing that? Or am I going about this the wrong way?
Thanks for any advice,
markl
null

Hi,
I didn't test it wit XML Schema, but any parser that finds a system ID should call an implementation of EntityResolver that returns an InputSource for the system ID.
An InputSource is a wrapper around an InputStream and its url and it ssystemID.
An example for sun's parser is on http://www.s-line.de/homepages/gerd_castan/java/resolve.html
(I "tested" this code also with oracles DTD and Schema parser. This means that I used this code for oracle, too, but I didn't go through the debugger to see what it does.)
Cheers,
Gerd

Logical DS using RDF/XML schema?

Hi,
Does ALDSP 2.5 support creation of a logical data source using an RDF/XML schema?
Any pointers to this would be really helpful.
Thanks,
Vidya

Hi,
Firstly a briefing on what I am trying to accomplish:
1.In my experiment, I have a XML schema called CurDataModel, with which I have created a logical DS CurDataModel.ds
I have created an RDF equivalent of the XML schema and want to create another logical DS.
2.I did refer the SampleTutorial1.pdf Section 3.1 which describes how to create logical DS.
3.However when i try to import a pre-defined RDF/XML schema (CUR.rdf) as attached, I am unable to do it.
Regards
Vidya

XML Schema any element

I have a list of schema files and they a number of elements in them. But for my data extraction i use only close to 300 tags. When i register the schema I get an error that a table cannot of have more than 1000 columns. My work mate is working on Annotations and I am planning to build a new schema to make extract only these 300 tag names and also make sure the XML file can be validated like it did earlier. Explaining this i came across a complex type element called *<any>* which can be used to allow elements to be available which are not declared within the schema file.
My Original schema file looks something like below,
<xsd:complexType name="WfInformation">
<xsd:all minOccurs="0">
<xsd:element name="Company" type="WfCompany" minOccurs="0" />
<xsd:element name="HeadOffice" type="WfOffice" minOccurs="0" />
<xsd:element name="IndependentOffice" type="WfIOffice" minOccurs="0" />
<xsd:element name="AffiliateCompany" type ="WfIAOffice" minOccurs="0" />
<xsd:element name="Number" type="xsd:string" minOccurs="0" />
<xsd:element name="ReferenceID" type="xsd:string" minOccurs="0" />
</xsd:all>
</xsd:complexType>
of the above list of items i use only elements Company, HeadOffice, Number. After reading through some documentation I wanted to <any> tag like below,
<xsd:complexType name="WfInformation">
*<xsd:sequence>*
<xsd:element name="Company" type="WfCompany" minOccurs="0" />
<xsd:element name="HeadOffice" type="WfOffice" minOccurs="0" />
*<xsd:any processContents="lax"/>*
*<xsd:any processContents="lax"/>*
<xsd:element name="Number" type="xsd:string" minOccurs="0" />
*<xsd:any processContents="lax"/>*
*</xsd:sequence>*
</xsd:complexType>
My question is if I am correcting the lines as i mentioned above will be Register schema again fail with same reason that i have 1000 columns. As i understand every element inside an Complex element is stored as a column value. In that case will this redesign work. Or is there any other way to approach re-desgin the XML Schema.

Thanks. I think that leaves out my option to create a totally new Schema to suit my XML files.
Only other option we have is to use Annotations.
I think my colleague - eoin62 would have shared the XML Schema files earlier through your oracle email address.
Please refer thread - How to register multiple XSD files
But we received a reply and we knew very little on how to make changes to Admin.xsd and how would that solve our problem. Please correct me if i am incorrect. Because the biggest Schema was estimate.xsd that has close to 800+ elements. I am not sure if my colleague sent you the necessary tag names we use within the Schema. We have close to around 300 tags we use. But our combined XML Schema has close to 1600+ If we have to annotate, i thought it would be better we tell Oracle which tagswe need, which inturn should should help better create XMLtype table against a Schema and work on performance.
Your earlier reply was,
Basically in XML Schema Admin.xsd element AdminCompin WorkfileTypeneeds to be stored Out of line..
Add the annotations xdb:SQLInline=”false” and xdb:defaultTable=”ADMIN_COMP_XML”. to the element..
if you can share with our XML Schema on how to annotate or if you can share a location that shows how an annotated or non-annotated Schema works that would help us correcting our Schema files.
Thanks for all your support. We have gone a long way in XML Parsing in the last 6 weeks.
Edited by: beta32c on Feb 19, 2013 12:09 AM

How to create a new aspx page in Pages library using Elements.xml without including any aspx page layout in my feature?

Is it possible to have the elements.xml file create a page in the Pages (or SitePages) library without actually including any sort of page layout or aspx artifact in the feature?
I see no reason to add a mywebpartlayout.aspx to my feature just so I can deploy a Home.aspx based on the BlankWebPart.aspx page layout.
I'm sure there is something obvious I am missing with regards to the Elements schema (which is why I've almost given up on using it completely and just gone to pure C#) but
I would really like to do this kind of simple stuff with declarations if at all possible. Must less code to write, debug, test and maintain.

I don't see how my question keeps getting misunderstood. This seems to be very clear and clearly not answered: "Is it possible to have the Elements.xml file
create a page in the Pages (or SitePages) library without actually including any sort of page layout or aspx artifact in the feature?"
I can't be more clear than "without including ANY sort of page layout or aspx artifact (meaning anything ending in aspx) IN THE FEATURE". I am not capitalizing to yell,
only to emphasize. Your disagreement is based on a link that shows ADDING AN ARTIFACT (the dummy MyPage.aspx) to a feature. I am asking if it
is possible (again, I cannot be more clear) to just use an Elements.xml file to instruct SharePoint to make a new item in a Pages or SitePages library.
Your definition of page includes Page Layouts and what you call Web Part Pages (again, a type of page layout + data in a site pages list that says what webparts
to display). Page Layouts are clearly NOT items stored inside of a SitePages or Publishing Pages library. Those libraries are just lists whose records
define the parts to show inside a specific layout.
When I refer to a Page I mean an entry into a pages (site pages/publishing pages) list. If I wanted to deploy a page layout then, quite obviously, I would need
to include it into my solution. I think maybe you are assuming that I do not know the difference. I do. The question is, can an Elements file alone be enough to instruct SharePoint to make a new entry into a Pages or SitePages library.
Now, your second link does show how to reference an existing Page Layout. Thank you for that. It is excellent. But this still leaves the problem of having to
add some sort of aspx page into the solution. Let me try to explain why I feel this SHOULD BE unnecessary: The aspx file will not have anything on it if I am referring to the ~sitecollections/.../BlankWebPartPage.aspx layout.
All web parts and content that should appear on the new page can be described IN the Elements.xml file. Any sort of aspx file is unnecessary, it seems to me.
So, if I am referencing a ~sitecollections/.../BlankWebPartPage.aspx page layout and specifying the web parts to add to the page, why should there be a
requirement to have some aspx file within the feature? That's what I am trying to figure out.
I am not asking for source code as proof. I am asking for an Elements file that does NOT reference anything AT ALL inside the Visual Studio solution for reasons I just described.
If you do not know how to do it then perhaps it cannot be done but I would like the question to stay unanswered for a little while until someone can demonstrate either a) it CAN
be done or b) a link to some Microsoft document stating that it is MANDATORY to have a physical element within the feature that gets copied to the environment.
I think it is important to understand what is being asked before insisting you have answered. It is clear from your posts that you have not fully understood the question yet but
I am hoping this posts makes it clear. I really appreciate you taking the time to respond, though. You seem to be the only one up for the challenge! :)

Read any XML File Elements using SAX Parser in J2se

Hi All
I can able to parsed one structured XML file using SAX
Sample code :
// ===========================================================
 // SAX DocumentHandler methods
 // ===========================================================
 public void startDocument() throws SAXException {
 logger.info("Start of document");
 public void endDocument() throws SAXException {
 logger.info("End of document");
 public void startElement(String namespaceURI, String localName, // local
 // name
 String qualName, // qualified name
 Attributes attrs) throws SAXException {
 elemName = new String(localName); // element name
 if (elemName.equals(""))
 elemName = new String(qualName); // namespaceAware = false
 tagPosition = TAG_START;
 // Set the string for accumulating the text in a tag to empty
 elemChars = "";
 // If the element name is "row", create a new row instance
 // If the element is "indexxid", "ModelPrice", or "ModelSpread",
 // the value will be read in the method "characters" and stored.
 if (elemName.equals("row")) {
 row = new IndexRow();
 numRows++;
 // logger.info("Number of numRow:"+numRows);
 } // end method startElement
 public void endElement(String namespaceURI, String simpleName, // simple
 // name
 String qualName // qualified name
 ) throws SAXException {
 elemName = new String(simpleName);
 if (elemName.equals(""))
 elemName = new String(qualName); // namespaceAware = false
 tagPosition = TAG_END;
 String indexId = new String();
 Double dblVal = new Double(0);
 // If element name is "row", put the current row in the map for row
 // instances
 if (elemName.equals("row")) {
 if (numRows <= 5) { logger.info("Row is: " + row.toString()); }
 //ABX
 //indexRows.put(row.getIndexxId(), row);
 if (family.equals("ABX.HE")){
 indexRows.put(row.getIndexREDId(), row);
 else {
 //CDX ITRXX
 indexRows.put(row.getIndexxId(), row);
 } else if (elemName.equals("IndexID")) {
 row.setIndexxId(elemChars);
 // Leave double value at default of zero if there are no chars
 if (elemChars.trim().length() != 0) {
 dblVal = new Double(elemChars);
 row.setCompositeSpread(dblVal);
 indexId = row.getIndexxId();
 } else if (elemName.equals("REDCode")) {
 row.setRedCode(elemChars);
 else if (elemName.equals("Name")) {
 row.setRowName(elemChars);
 } else if (elemName.equals("Series")) {
 row.setSeries(elemChars);
 } else if (elemName.equals("Version")) {
 row.setVersion(elemChars);
 } else if (elemName.equals("Term")) {
 row.setTerm(elemChars);
 } else if (elemName.equals("Maturity")) {
 row.setMaturity(elemChars);
 } else if (elemName.equals("OnTheRun")) {
 row.setOnTheRun(elemChars);
 } else if (elemName.equals("Date")) {
 row.setRowDate(elemChars);
 } else if (elemName.equals("Depth")) {
 row.setDepth(elemChars);
 else if (elemName.equals("Heat")) {
 // logger.info("Chars for element " + elemName + " are '" +
 // elemChars + "'");
 // Leave double value at default of zero if there are no chars
 if (elemChars.trim().length() != 0) {
 dblVal = new Double(elemChars);
 row.setHeat(dblVal);
 indexId = row.getIndexxId();
// ABX.HE
 else if (elemName.equals("IndexREDId")){
 row.setIndexREDId(elemChars);
 else if (elemName.equals("Coupon")){
 row.setCoupon(elemChars);
 if (elemName.equals("Ontherun")) {
 row.setOnTheRun(elemChars);
 } // end method endElement
 public void characters(char buf[], int offset, int len) throws SAXException {
 // If at end of element, there will be no characters
 if (tagPosition == TAG_END) {
 return;
 // The characteres method may be called more than once
 // for an element if the internal buffer fills up.
 // Append the characters until the end of the element.
 String strVal = new String(buf, offset, len);
 elemChars = elemChars + strVal;
 } // end method characters
} // end class MarkItIndexLoader
but the problem is i want to read (parse) any XML file means any Elemets would be change any time using SAX .In the above example
else if (elemName.equals("Heat")) {
else if (elemName.equals("IndexREDId")){
} else if (elemName.equals("Maturity")) {
like above I am doing hard code Elements names and reading the values so i don't want hard coding the elements names I want to read any element name and value dynamically.
If i give any one below XML file i want to read the Elements and displaying to console without changing any code i want to read the XML document.
EX:
Student.XML: <root>..</StName>..</StAge>...</root>
Employee.XML: <root>..</EmpName>..</EmpAge>...</root>
CdCatalog.XML: <root>..</Cdtitle>...</CdNumber>...</root>
I need one java program can ready any type of XML file elements and send to the Database table.
Please any one done like this task please suggest some reference links or books or sample snippet which can help me to develop program in my requirement.
Thanks in advance
Regards
satish

You should ask in the Java forum.
Regards
Stefan

Specifying Case-Insensitive Element Names in XML Schema

Hope someone knows this!
Is it possible to define an an XML Schema Definition so that Element names in the target XML File can be case insensitive.
At the moment my Parser throws an error if the element names in the XML file do not have the exact same case as the definition in the XML schema.
E.g
In Schema i have:
<xsd:element name="HOSTINVENTORYLINE" type="HostInventoryLineType" maxOccurs="unbounded" minOccurs="0"/>
but in xml file i have
<HostInventoryLine field=""/>
or
<hostinventoryline field=""/>
Does anyone know anyway to get around this, so that the parser accepts the HostInventoryLine element in the xml as an instance of the HOSTINVENTORYLINE element defined in the schema.
Thanks in Advance
JJ
Message was edited by:
[email protected]

You could use substitution groups to handle this. You would need an entry in the schema for each valid capitalization. This won't scale well if you want to be completely case insensitive, but if you only support lower case, upper case, and camel case it should do the trick.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
 <xs:complexType name="HostInventoryLineType">
 <xs:sequence>
 <xs:element name="an-element" type="xs:string"/>
 </xs:sequence>
 </xs:complexType>
 <xs:element name="HostInventoryLine" type="HostInventoryLineType"/>
 <xs:element name="HOSTINVENTORYLINE" type="HostInventoryLineType" substitutionGroup="HostInventoryLine"/>
 <xs:element name="hostinventoryline" type="HostInventoryLineType" substitutionGroup="HostInventoryLine"/>
</xs:schema>-Blaise

Specifying nested element with two different XML Schema

Hello,
I am trying to convert one xml file to another file. I figure data services would be great for this.
My problem relates to how to have a source xml file with a certain xml schema be transformed to one of a different xml schema. I cannot build the nested elements of the target schema.
From the source xml I only need four fields. But they need to be nested three levels in the target xml.
Source
<DRUG_PRODUCT_LST xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <DRUG_ITEM>
 <DRUG_PRODUCT_ID>113083</DRUG_PRODUCT_ID>
 <DIN_PDIN>2317559</DIN_PDIN>
 <HC_BRAND_NAME>PMS-SILDENAFIL</HC_BRAND_NAME>
 <HC_ATC_CODE>G04BE03</HC_ATC_CODE>
 </DRUG_ITEM>
<DRUG_PRODUCT_LST
Target
<?xml version="1.0" encoding="ISO-8859-1"?>
<CODES>
 <CODE_TYPES>
 <CODE_TYPE>
 <COD_CODE>113083</COD_CODE>
 <COD_DESCR>PMS-SILDENAFIL</COD_DESCR>
 <COD_SOURCE>G04BE03</COD_SOURCE>
 <COD_NPSA>2317559</COD_NPSA>
 </CODE_TYPE>
 </CODE_TYPES>
</CODES>
I have tried using an xml pipline to unnest the source, then use a query transform to re-nest for the target. But I do not know how to specify the input schemas.

Hello,
I am trying to convert one xml file to another file. I figure data services would be great for this.
My problem relates to how to have a source xml file with a certain xml schema be transformed to one of a different xml schema. I cannot build the nested elements of the target schema.
From the source xml I only need four fields. But they need to be nested three levels in the target xml.
Source
<DRUG_PRODUCT_LST xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <DRUG_ITEM>
 <DRUG_PRODUCT_ID>113083</DRUG_PRODUCT_ID>
 <DIN_PDIN>2317559</DIN_PDIN>
 <HC_BRAND_NAME>PMS-SILDENAFIL</HC_BRAND_NAME>
 <HC_ATC_CODE>G04BE03</HC_ATC_CODE>
 </DRUG_ITEM>
<DRUG_PRODUCT_LST
Target
<?xml version="1.0" encoding="ISO-8859-1"?>
<CODES>
 <CODE_TYPES>
 <CODE_TYPE>
 <COD_CODE>113083</COD_CODE>
 <COD_DESCR>PMS-SILDENAFIL</COD_DESCR>
 <COD_SOURCE>G04BE03</COD_SOURCE>
 <COD_NPSA>2317559</COD_NPSA>
 </CODE_TYPE>
 </CODE_TYPES>
</CODES>
I have tried using an xml pipline to unnest the source, then use a query transform to re-nest for the target. But I do not know how to specify the input schemas.

Xml Schema xs:choice element in dynamic forms

Hi all,
I'm developing an xml schema for creating the data model of a form. I connect LC Designer-8.2ES to this schema.
In the schema I do have mutually exclusive elements implemented with a <xs:choice> element. A very comparable situation was described in this thread : http://www.acrobatusers.com/forums/aucbb/viewtopic.php?id=123 in 2007.
The problem, as related in this thread, is that only the very first element of the choice is displayed in the generated pdf and I don't know how to display all parts as a real choice. So what's the best way to let user fill in one part or the other of the choice?
Does it need to be implemented with scripting (xfa...myform.presence = visible | hidden)?
I want that only the filled element of the choice be exported from the form, the resulting xml being valid according the schema. I seems to work, but as of now, only for the first element...
BTW, what's the best document describing what parts of xml schema are usable in dynamic XFA forms? Is it 100% compatible? I've observed that the constraints in my schema are not validated in the forms. Shouldn't xml schema generate validating script in LCD? Does it apply for a subset of xml schema?
Thanks in advance,
jgrd

Hi all,
finally, I understand that we cannot use "anonymous" sequences neither in LiveCycle (like this following example where person might have many email)
 <xs:element name="person">
 <xs:complexType>
 <xs:sequence maxOccurs="unbounded">
 <xs:element name="email" type="xs:string"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
valid instance with 3 emails :
<person xsi:noNamespaceSchemaLocation="Untitled39.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <email>String</email>
 <email>String</email>
 <email>String</email>
</person>
In LC Designer, element with same name (<email>) are not used AFAK. Maybe I'm wrong?
The same hands with <xs:choice> where only first choice appears in pdf although being present in LC Designer.
As for sequences, my idea is to produce <email1>, <email2>, etc. in a static schema, before connecting schema's data to LCD.
Hope someone can show up and tell it's the right way or not.
Regards
jgrd

Data Insertion, XML Schema Specifying Element minOccurs="1

An XML schema having an element with attribute minOccurs="1" has been successfully registered. A table was created based on that schema. Inserting data both with and without that element works successfully. Why is this?

The only thing right now, I can think of, is that the database doesn't recognize it as being controlled via / depends on a registered XML Schema. See the FAQ on this forum for examples (See here: How does XML DB handle XML Schema Validation ?

Any function module/program to write-xml schema of a idoctype

Hi experts,
I need to write the xml format into an internal table.
input---idoc type.
output--xml schema file in an internal table/or in some file.
Through we60 we can get the xml schema.but through some program i want to get it .how to go for it.
Any function module do you suggest which fits to this requirement and do the work for me.
For ex: idoc type--orders05
Message was edited by:
dasr r

Hello Dasr
There are several function modules available. Please check yourself if any of them matches your demands.
EDIN                           IDoc: Eingangsverarbeitung
IDOC_INBOUND_XML_VIA_HTTP      eingang über http
IDOC_XML_FROM_FILE             IDoc: Eingangsverarbeitung vom XML über Dateischnittstelle
IDOC_ADAPTER_MB                Message Broker IDoc Adapter
IDX_IDOC_TO_XML                Konvertierung IDoc nach IDoc XML im XMB
IDOC_XML1                      erweiterte Tabellenpflege (generiert)
IDOC_XML_DISPLAY               Anzeigen eines IDocs in XML-Format mit XSL
IDOC_XML_TRANSFORM             Anzeigen eines IDocs in XML-Format mit XSL
Regards
Uwe

Any workarounds for not supported features of XML Schema

Hi,
We are trying to generate JAVA source code by providing a xsd.
This XML Schema file has all sorts of Identity constraints & attribute wildcards.
Due to the above reasons I am unable to generate the code.
Are there any workarounds? If so Please share those.
Thanks & Regards,
Priti Ranka

I am sorry I did not mention the tech. being used.
I am using JAXB for the above task.

XML Schema Element any

Similar Messages

Maybe you are looking for