Xml Schema creation - enforcing one tag at root
I have a schema such as the one below but this permits any of the global element declarations to start as the root of an xml document.
I want just <table> to be at the root.
<xs:element name="table">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" ref="tr"/>
</xs:sequence>
<xs:attributeGroup ref="attrs"/>
</xs:complexType>
</xs:element>
<xs:element name="tr">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" ref="td"/>
</xs:sequence>
<xs:attributeGroup ref="attrs"/>
</xs:complexType>
</xs:element>
<xs:element name="td">
<xs:complexType mixed="true">
<xs:complexContent>
<xs:extension base="Flow">
<xs:attributeGroup ref="attrs"/>
<xs:attributeGroup ref="cellvalign"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>Must I have one global element to allow only one element as the document root?
i.e.
<xs:element name="table">
<xs:complexType>
<xs:sequence>
<xs:element name="tr">
<xs:complexType ref="tr.c">
</xs:element >
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="tr.c">
<xs:sequence>
<xs:element maxOccurs="unbounded" ref="td"/>
</xs:sequence>
<xs:attributeGroup ref="attrs"/>
</xs:complexType>
thanks
I would rather use the flatter approach, the xhtml schema does how does it do it?
http://www.w3.org/2002/08/xhtml/xhtml1-transitional.xsd
Maybe I should explain more....
I wish to validate an xml document with a schema only, I pull the xml from within a propery file (Ugly I know). And keep it in memory.
The xml has no xsi attributes such as 'schemaLocation' , I tell the paser using a property the location of the external schema.
The outcome of validation is that the paser allows any globally declared element to be a root element when I wish just to have just one.
I guess the question is, what within the xml document or the schema tells the parser what the root element is?
cheers
Similar Messages
-
hi all,
i created a XML schema but i have some confusion in :
<Processsteps>
<ProcessStep/>
<ParallelProcessStep/>
</ProcessSteps>
in this case none(child element) is manadatory, but there should be at least 1 child element of either type.
how can i implement this problen mentioned above in Schema? can anybody send code for this problem/Try the 'choice' option for a 'complexType'
I just recently learned how to write schemas. This tutorial is a little vague, but it gave me a good start
http://www.w3schools.com/schema/default.asp
Sorry, not giving you code, it's not that difficult. -
Multiple Schema Creation with One Source system Via SLT
Hi all,
we have BW on HANA environment at our company premises, with SLT server installed
So, my Question is that is it possible to create more than one schema in HANA system with one Source system
As an example, lets say, ECC (Client 601) Source System has been connected to HANA via SLT and created Schema called SCHEMA_1 and again i want to create SCHEMA_2 by connecting same ECC (Client 601) source System.
please help me to short this out?
Thanks
MiranaHi Mirana,
Yes, it is possible to create more than one schema in HANA system with one Source system.
Please go through the Official SAP LT document for more details @ page number 13
http://www.saphana.com/servlet/JiveServlet/previewBody/1811-102-5-5419/SAP_LT_Replication_Server_for_SAP_HANA_SPS05_Over… -
Unable to create xml from xml schema
JDeveloper 10.1.3 EA1
I am unable to create a new xml file from an xml schema when the starting root element is a complex type (but it works with a simple type). It does not matter if the xml schema is registered within JDeveloper.
Is this a bug or intended behaviour?
Error message:
''XML Document from XML Schema creation could not be competed succesfully. Make sure the source schema is valid and that you have write permissions to the output directory."
NB The xml schema is valid and I have write permissions on the specified directory.When I do not register this (or other) schema with JDeveloper, I can create an xml document from xml schema. However, when I register this schema and then try to generate an xml document (either from the registered xsd either from a filesystem xsd) with person as starting node it fails with the mentioned error. However, when I use city as starting node it is generated successfully.
<?xml version="1.0" encoding="windows-1252" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.amis.nl/demo/hrm"
targetNamespace="http://www.amis.nl/demo/hrm"
elementFormDefault="qualified">
<xsd:element name="person">
<xsd:annotation>
<xsd:documentation>
A sample complex element
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="length" type="xsd:int"/>
<xsd:element name="weight" type="xsd:int" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="city" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
A sample simple element.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema> -
Help me some xml scheme problem
hi, everybody
I'm have some question about xml document, that can have xml scheme more than one on a document ?. please.I want put 2 xml schemes,a.xsd and b.xsd, in a xml document.
Example:
<?xml version="1.0" encoding="UTF-8"?>
<selfTest xmlns="mySelfTestNameSpace"
xmlns:myNameSpace="myTestComplexType"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="mySelfTestNameSpace D:\My-Work\MasterDegree\Thesis-Lab\selfTest.xsd myTestComplexType
D:\My-Work\MasterDegree\Thesis-Lab\testComplexType.xsd">
<ElementA></ElementA>
<ElementB>valueEleB1</ElementB>
<myNameSpace:hMessageInfo childOfMsgAttri="xxx" domain="top" port="001">
<myNameSpace:Message></myNameSpace:Message>
</myNameSpace:hMessageInfo>
</selfTest>
// In example If removed Element:<myNameSpace:hMessageInfo> .... , It can validated, but If take with above the error message follow.
- Error Message
This file is not valid:
Unexpected child element 'myNameSpace:hMessageInfo'
File: selfTest.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSPY v5 rel. 4 U (http://www.xmlspy.com) by SE (TU) -->
<xs:schema targetNamespace="mySelfTestNameSpace" xmlns:mySelftTest="mySelfTestNameSpace" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="selfTest" type="mySelftTest:TranstionType">
<xs:annotation>
<xs:documentation>Comment describing your root element</xs:documentation>
</xs:annotation>
</xs:element>
<xs:complexType name="TranstionType">
<xs:sequence>
<xs:element name="ElementA">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="attriElementA" type="xs:string"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="ElementB">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="valueEleB1"/>
<xs:enumeration value="valueEleB2"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
<xs:attribute name="externalTranstion">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="aa"/>
<xs:enumeration value="bb"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:schema>
File:testComplexType.xsd
<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSPY v5 rel. 4 U (http://www.xmlspy.com) by SE (TU) -->
<xs:schema targetNamespace="myTestComplexType" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:testComplexType="myTestComplexType" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="test">
<xs:annotation>
<xs:documentation>Comment describing your root element</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="hMessageInfo" type="testComplexType:ChildOfMsgInfo"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="MessageInfo">
<xs:sequence>
<xs:element name="Message">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string"/>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="domain">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="top"/>
<xs:enumeration value="bottom"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="port" type="xs:string"/>
</xs:complexType>
<xs:complexType name="ChildOfMsgInfo">
<xs:complexContent>
<xs:extension base="testComplexType:MessageInfo">
<xs:attribute name="childOfMsgAttri" type="xs:string"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema> -
How to identify and delete objects after failure of registering XML schema
Hi,
I have tried to register a XML schema with many global elements but failed.
I have checked the view DBA_XML_SCHEMA and found that there is an entry for this failed XML schema and the disk spaces would not be freed after the failure of registration as well.
I have tried DBMS_XMLSCHEMA.deleteSchema() with DELETE_CASCADE_FORCE but failed with ORA-31000: Resource is not XDB document.
How can I identify and delete the objects for this failed XML schema and free up the disk space ?
I would not prefer to use 'DROP USER ... CASCADE' since there are other objects owned by this user.
Thanks in advance.you can get them from user_objects.
but you have to identify them manuallly if your schema has other objects other then created by the xml schema creation process.
Note these objects will be cases senistitive. so you should enclose them with double quotes during deletion. -
Simpletype Initial tag in a XML Schema?
Hello,
We have an Oracle 12 EBS implementation, and are using an Advanced Queue dequeue process that can handle a number of XMLType files from different sources as input. The Dequeue procedure right now extracts the value of first field of each of the XML files (which would be a FILETYPE field), and decides which procedure to call. The code used for this is:
v_filetype := message.extract('//FILETYPE/text()').getStringVal();
The procedure called by the de-queue is the one that loads into the XMLType table.
The problem is that I have set up the XML Schema to use a complextype as the first item - and so each different type of XML type would have a different initial tag. For example, suppose there are Purchase Orders and Employees coming through the queue. The Purchase Order Schema file starts like this (example):
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xdb="http://xmlns.oracle.com/xdb"
version="1.0"
xdb:storeVarrayAsTable="true">
<xs:element name="PurchaseOrder" type="PurchaseOrderType" xdb:defaultTable="PURCHASEORDER"/>
<xs:complexType name="PurchaseOrderType" xdb:SQLType="PURCHASEORDER_T">
<xs:sequence>
<xs:element name="ORG_ID" type="IdType" minOccurs="0" xdb:SQLName="ORG_ID"/>
and the xml file would be:
<PurchaseOrder xsi:noNamespaceSchemaLocation="PurchaseOrders.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ORG_ID>204</ORG_ID>
... etc.
This system works fine - but the dequeue procedure, which is called before the xml is inserted into the XMLType table does not have a way to determine what kind of XML file this is. So basically, the path will be different for each different type of file.
Is there a easy way to either:
- get the FILETYPE variable some other way using PL/SQL when the initial path would be different for each file type?
- OR define the schema in such a way that allows for that information to be in the same "path"
I was thinking of something along the lines of ...
a) using remarks (how would we be able to read it using simple PL/SQL?)
b) or maybe just defining a simple type as the initial element - kind of like this:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xdb="http://xmlns.oracle.com/xdb"
version="1.0"
xdb:storeVarrayAsTable="true">
<xs:element name="FILETYPE" type="String_240Type" xdb:SQLName="FILETYPE"/>
<xs:element name="PurchaseOrder" type="PurchaseOrderType" xdb:defaultTable="PURCHASEORDER"/>
<xs:complexType name="PurchaseOrderType" xdb:SQLType="PURCHASEORDER_T">
<xs:sequence>
<xs:element name="ORG_ID" type="IdType" minOccurs="0" xdb:SQLName="ORG_ID"/>
with a corresponding xml of:
<FILETYPE xsi:noNamespaceSchemaLocation="PurchaseOrders.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">PO</FILETYPE>
<PurchaseOrder>
<ORG_ID>204</ORG_ID>
(but XMLSpy assures me this is not valid - neither the xchema nor the xml)
Any help would be deeply appreciated!
Thanks!
Edited by: user11313400 on Aug 17, 2009 11:17 AM
Edited by: user11313400 on Aug 17, 2009 11:20 AMI don't fully understand all the issues behind your questions but I'll give some answers. What is wrong with your current code of
v_filetype := message.extract('//FILETYPE/text()').getStringVal();in retrieving the FILETYPE? While the use of // is not the best for performance, that will find FILETYPE where ever it resides in the message XML? If you know FILETYPE resides at a certain level, you could also do the following to improve performance a bit (untested theory)
v_filetype := message.extract('/*/FILETYPE/text()').getStringVal();
That sample assumes FILETYPE is a child of the root node, and doesn't care what the root node is named.
As you are going to, the best method would be to have FILETYPE is the same location for all the XML messages to make retrieval the easiest. Without a larger sample of your .xsd I won't offer a working solution, but can you just make FILETYPE part of the PurchaseOrderType definition? I know you mentioned multiple XML file types so I'm not sure what the others look like and what you can and cannot change.
Other thoughts:
- Could you pass in the file type as part of what is enqueued in AQ?
- Can you determine file type from the name of the root node in the XML? -
Hi,
I have created a local varibale and stored my xml schema (xml structure) in it. I am using a sql query to fetch the records from databae and populating it to the schema using Assignment action block. But I have a requirement that one of the tag in the xml schema should be added dynamicaly according to the result of the query. Can anyone help me on this? . In the Linktype I saw one option as Append xml. How can we use that option
Please let me know if you have any thoughts on this
Thanks in advance
ShajiHi Shaji,
Please find the below link: It explains all the XML functions in MII Workbench.
http://wbhelp.sap.com/manufacturing/xmii_120/en/44/7ca00d32406572e10000000a11466f/content.htm
"Calculated Columns" can be useful here as per your requirements.
For help on Link Types, go through the following link:
http://wbhelp.sap.com/manufacturing/xmii_120/en/44/89aa7088cc6fb5e10000000a155369/content.htm
Hope this will help you.
Best regards,
Kedar -
Puttin the name of the file in one tag of the xml message
Hi all,
does anybody kowns how to put the name of the file in one tag of the xml message in the adapter, without using a java mapping to get the file name.
Thanks.H Antonio,
You can use ASMA( Adapter Specific Message Attributes) for acccessing the file name, along with Dynamic Configuration. You can follow the following blog for that. If you do not want to use the same file name for the reciever, dont select the File Name check box.
/people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14
Thanks and Regards,
Sanjeev. -
Unable to find root element in XML Schema when Syndicating (SAP MDM)
Hi experts,
We are having a problem with our Syndication.
We have created an XML Schema using XML Spy. We need a namespace, and this is 70 characters long (in other words, far shorter than maximum at 255 characters).
<xs:schema xmlns:ns="http://schemas.xxxxx.com/ServiceManagement/ServiceMasterDataFromMDM/0.3" xmlns:xs="http://www.xxxxx.org/2001/XMLSchema" targetNamespace="http://schemas.xxxxxx.com/ServiceManagement/ServiceMasterDataFromMDM/0.3" elementFormDefault="unqualified" attributeFormDefault="unqualified">
When opening the xml schema file in Syndicator, the root field is disabled.
If we remove namespace in heading of xml schema, the root field is enabled, and the root element is correct.
How can we make use of the XML schema when we need namespace?
We have tried to add namespace annotation ns: to all type definitions:
<xs:element name="ServiceCategory" type="ns:ServiceCategoryType">
This did not help.
Please advice.
KR,
Thomas
Edited by: Thomas on Mar 2, 2011 2:12 PM>>We need a namespace, and this is 70 characters long
If you want namespace to appear in XML and your XSD has it too. please add the namespace under "URI" attribute in XML schema in Console.
You need to import the XSD in Console first, specify namespace under URI and then use this to build syndication map.
Thanks
Aamir -
How to handle include tag in xml schema
My XML schema makes reference to other schema, something like:
<xsd:include schemaLocation="../LOCCommon/LOCCommon.xsd"/>
How do I handle this when using XML DB?XDB does currently understand relative URLs. We are looking at this since thier use is becoming more common. You will need to register both schemas under absolute URLs and then adjust the URL of the include or import statement to reflect this...
The following code sample may help...
procedure fixRelativeURLs(xmlschema in out xmltype, schemaLocationHint varchar2)
as
cursor getImports is
select SCHEMA_LOCATION
from xmlTable
xmlnamespaces
default 'http://www.w3.org/2001/XMLSchema'
'/schema/import'
passing xmlSchema
columns
SCHEMA_LOCATION varchar2(700) path '@schemaLocation'
cursor getIncludes is
select SCHEMA_LOCATION
from xmlTable
xmlnamespaces
default 'http://www.w3.org/2001/XMLSchema'
'/schema/include'
passing xmlSchema
columns
SCHEMA_LOCATION varchar2(700) path '@schemaLocation'
baseURL varchar2(700);
schemaLocation varchar2(700);
targetURL varchar2(700);
begin
if instr(schemaLocationHint,'/',-1) > 0 then
baseURL := substr(schemaLocationHint,1,instr(schemaLocationHint,'/',-1)-1);
else
baseURL := '/';
end if;
for import in getImports loop
targetURL := baseURL;
schemaLocation := import.SCHEMA_LOCATION;
-- The following are treated as relative URLs
-- URLs with no '/' character
-- URLs which do not start with '/' and which do not contain '://'
if ((instr(schemaLocation,'://') = 0) and (instr(schemaLocation,'/') <> 1)) then
if (instr(schemaLocation,'..') = 1 ) then
while instr(schemaLocation,'..') = 1 loop
schemaLocation := substr(schemaLocation,4);
targetURL := substr(targetURL,1,instr(targetURL,'/',-1)-1);
end loop;
end if;
schemaLocation := targetURL || '/' || schemaLocation;
-- dbms_output.put_line('Import : re-mapping "' || import.SCHEMA_LOCATION || '" to "' || schemaLocation || '".');
select updateXML
xmlSchema,
'/xsd:schema/xsd:import[@schemaLocation="' || import.SCHEMA_LOCATION || '"]/@schemaLocation',
schemaLocation,
NAMESPACES
into xmlSchema
from dual;
else
dbms_output.put_line('Import : skipping "' || import.SCHEMA_LOCATION || '".');
end if;
end loop;
for include in getIncludes loop
targetURL := baseURL;
schemaLocation := include.SCHEMA_LOCATION;
-- The following are treated as relative URLs
-- URLs with no '/' character
-- URLs which do not start with '/' and which do not contain '://'
if ((instr(schemaLocation,'://') = 0) and (instr(schemaLocation,'/') <> 1)) then
if (instr(schemaLocation,'..') = 1 ) then
while instr(schemaLocation,'..') = 1 loop
schemaLocation := substr(schemaLocation,4);
targetURL := substr(targetURL,1,instr(targetURL,'/',-1)-1);
end loop;
end if;
schemaLocation := targetURL || '/' || schemaLocation;
-- dbms_output.put_line('Include : re-mapping "' || include.SCHEMA_LOCATION || '" to "' || schemaLocation || '".');
select updateXML
xmlSchema,
'/xsd:schema/xsd:include[@schemaLocation="' || include.SCHEMA_LOCATION || '"]/@schemaLocation',
schemaLocation,
NAMESPACES
into xmlSchema
from dual;
else
dbms_output.put_line('Inlcude : skipping "' || include.SCHEMA_LOCATION || '".');
end if;
end loop;
end;
-- -
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.<br /><br />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.<br /><br />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):<br /><br /><element complextype issue><br /> <element issueId string/><br /> ...<br /> ...<br /> <element complextype majorcomponent unbounded><br /> <element majcomponentname string/><br /> ...<br /> <element complextype subcomponent unbounded><br /> <element subcomponent string/><br /> <element quantity string/><br /> ...<br /> ...<br /> </element><br /> </element><br /></element><br /><br />My problem is as follows: <br /><br />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).<br /><br />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.<br /><br />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.<br /><br />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. -
Defining entities with XML schema
Hi,
I came across a problem with XML schema's apparent lack of support for entities. e.g. we define an entity like this:
<!ENTITY le "≤" >.
First off I was trying in my XML instance to include an external entity file like this:
<!DOCTYPE wpi [
<!ENTITY % DerwentXmlEntities PUBLIC "-//Derwent//Derwent XML General ENTITIES 20000214//EN"
"derwent-xml-entities.ent">
%DerwentXmlEntities;
]>
<WPI xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://www.derwent.co.uk/wpi.xsd">
but I am not clear on where I should place the file derwent-xml-entities.ent. Everything I tried ended up with:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00202: could not open file "derwent-xml-entities.ent"
Is it possible to include a file like this?
So I tried just defining an entity like this:
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE wpi [
<!ENTITY times "×">
<!ENTITY le "≤">
]>
The "times" seems OK, but for "le" I get:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00217: invalid character 8804 (\u2264)
What sort of encoding should I use?
Thanks
Pete<xsd:element name="PsL">
<xsd:annotation>
<xsd:documentation>
**Pseudo List, required as in D-types, the editors often used the
{H control sequence to force an indent to make lists of compounds more
legible. We can't be sure that they are always lists but there is
useful mark-up there that we wouldn't want to lose**
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="PsE" minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="PsE">
<xsd:annotation>
<xsd:documentation>
Pseudo List Entry
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence minOccurs="1" maxOccurs="1">
<xsd:element ref="PsP" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="PsS" minOccurs="1" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="PsP">
<xsd:annotation>
<xsd:documentation>
Pseudo List Prefix
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:choice minOccurs="0" maxOccurs="unbounded">
<xsd:element name="PsP" type="xsd:string"/>
<xsd:element ref="Sub" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="Sup" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="Em" minOccurs="1" maxOccurs="1"/>
</xsd:choice>
</xsd:complexType>
</xsd:element>
<xsd:element name="PsS">
<xsd:annotation>
<xsd:documentation>
Pseudo List Suffix
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:choice minOccurs="0" maxOccurs="unbounded">
<xsd:element name="PsS" type="xsd:string"/>
<xsd:element ref="Sub" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="Sup" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="Em" minOccurs="1" maxOccurs="1"/>
</xsd:choice>
</xsd:complexType>
</xsd:element>
<xsd:element name="Prt">
<xsd:annotation>
<xsd:documentation>
************************ Part Container Element **************
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence minOccurs="1" maxOccurs="1">
<xsd:element ref="PrtNo" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="PrtNm" minOccurs="1" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="PrtNo">
<xsd:annotation>
<xsd:documentation>
PartNo
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:choice minOccurs="0" maxOccurs="unbounded">
<xsd:element name="PrtNo" type="xsd:string"/>
<xsd:element ref="Sub" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="Sup" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="Em" minOccurs="1" maxOccurs="1"/>
</xsd:choice>
</xsd:complexType>
</xsd:element>
xsd:element name="PrtNm">
<xsd:annotation>
<xsd:documentation>
PartName
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:choice minOccurs="0" maxOccurs="unbounded">
<xsd:element name="PrtNm" type="xsd:string"/>
<xsd:element ref="Sub" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="Sup" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="Em" minOccurs="1" maxOccurs="1"/>
</xsd:choice>
</xsd:complexType>
</xsd:element>
<xsd:element name="L">
<xsd:annotation>
<xsd:documentation>
************************ List Container Element *************
Attribute typ=used by the composition software to decide how to prefix
the list entries, e.g. (a), (A), (i), (1), etc.
AL for AlphaLower
AU for AlphaUpper
RL for RomanLower
RU for RomanUpper
No for Number
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence minOccurs="1" maxOccurs="unbounded">
<xsd:element ref="LP" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="LS" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:attribute name="typ" use="optional">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="AL"/>
<xsd:enumeration value="AU"/>
<xsd:enumeration value="RL"/>
<xsd:enumeration value="RU"/>
<xsd:enumeration value="No"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="LP">
<xsd:annotation>
<xsd:documentation>
List Paragraph
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:choice minOccurs="0" maxOccurs="unbounded">
<xsd:element name="LP" type="xsd:string"/>
<xsd:element ref="Sub" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="Sup" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="Em" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="RefD" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="RefF" minOccurs="1" maxOccurs="1"/>
</xsd:choice>
</xsd:complexType>
</xsd:element>
<xsd:element name="LS">
<xsd:annotation>
<xsd:documentation>
1st level sublist
Attribute typ=used by the composition software to decide how to prefix
the list entries, e.g. (a), (A), (i), (1), etc.
AL for AlphaLower
AU for AlphaUpper
RL for RomanLower
RU for RomanUpper
No for Number
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence minOccurs="1" maxOccurs="unbounded">
<xsd:element ref="LP" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="LSS" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:attribute name="typ" use="optional">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="AL"/>
<xsd:enumeration value="AU"/>
<xsd:enumeration value="RL"/>
<xsd:enumeration value="RU"/>
<xsd:enumeration value="No"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="LSS">
<xsd:annotation>
<xsd:documentation>
2nd level list
Attribute typ=used by the composition software to decide how to prefix
the list entries, e.g. (a), (A), (i), (1), etc.
AL for AlphaLower
AU for AlphaUpper
RL for RomanLower
RU for RomanUpper
No for Number
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="LP" minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="typ" use="optional">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="AL"/>
<xsd:enumeration value="AU"/>
<xsd:enumeration value="RL"/>
<xsd:enumeration value="RU"/>
<xsd:enumeration value="No"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="IndexingCorePt">
<xsd:annotation>
<xsd:documentation>
******** ROOT ELEMENT for Core Patent Indexing *********
** Indexing is composed of Derwent Classification (DC),IPCs,
Fragmentation Coding (Frags), Polymer Indexing, Unlinked Registry numbers
and Keyword Indexing (KI).
Any combination is these three elements is allowed.
Attribute vs =Version number starting at 0
Attribute co =Patent country
Attribute se =Patent serial
Attribute ki =Patent Kind
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence minOccurs="1" maxOccurs="1">
<xsd:element ref="DC" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="IPCs" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="Frag" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="Polymer" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="IdxU" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="KI" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:attribute name="vs" type ="xsd:NMTOKEN" use="optional"/>
<xsd:attribute name="co" type ="xsd:NMTOKEN" use="required"/>
<xsd:attribute name="se" type ="xsd:NMTOKEN" use="required"/>
<xsd:attribute name="ki" type ="xsd:NMTOKEN" use="required"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="DC">
<xsd:annotation>
<xsd:documentation>
************* DERWENT CLASSIFICATION *******************
** Derwent Classification is divided in 3 main areas:
Chemical(CPI),General & Mechanical (EngPI),
Electronic & Electronical (EPI)
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:choice minOccurs="1" maxOccurs="1">
<xsd:sequence minOccurs="1" maxOccurs="1">
<xsd:element ref="CPIs" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="EngPIs" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="EPIs" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:sequence minOccurs="1" maxOccurs="1">
<xsd:element ref="EngPIs" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="EPIs" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:element ref="EPIs" minOccurs="1" maxOccurs="1"/>
</xsd:choice>
</xsd:complexType>
</xsd:element>
<xsd:element name="CPIs">
<xsd:annotation>
<xsd:documentation>
UNIQUE ELEMENT DC
** Container element for CPI**
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="CPI" minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="CPI">
<xsd:annotation>
<xsd:documentation>
UNIQUE ELEMENT CPIs
** CPI is composed of sections A to N (no section I)
Any combination is allowed, there has to be at least one section.
No section can appear twice. The DTD does not enforce this.
Section N can't be on his own. The DTD does not enforce this.
Each single Chemical section is composed of one main class (DCCM)
and zero to many secondary classes (DCCSs). One to many Manual
code (MCCs) has to be applied to a given chemical section.
Attribute section= an allowed Derwent CPI section **
Note that content MCCs is optional as its optional in the backfile
before 19??
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:choice minOccurs="1" maxOccurs="1">
<xsd:sequence minOccurs="1" maxOccurs="1">
<xsd:element ref="DCCM" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="DCCSs" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="MCCs" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:element ref="MCCs" minOccurs="1" maxOccurs="1"/>
</xsd:choice>
<xsd:attribute name="sct" use="required">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="A"/>
<xsd:enumeration value="B"/>
<xsd:enumeration value="C"/>
<xsd:enumeration value="D"/>
<xsd:enumeration value="E"/>
<xsd:enumeration value="F"/>
<xsd:enumeration value="G"/>
<xsd:enumeration value="H"/>
<xsd:enumeration value="J"/>
<xsd:enumeration value="K"/>
<xsd:enumeration value="L"/>
<xsd:enumeration value="M"/>
<xsd:enumeration value="N"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="DCCM" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
** Derwent Class Chemical Main element **
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="DCCSs">
<xsd:annotation>
<xsd:documentation>
** Derwent Classes Chemical Secondary Container element**
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="DCCS" minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="DCCS" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
** A Derwent Class Chemical Secondary (DCCS) **
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="MCCs">
<xsd:annotation>
<xsd:documentation>
** Manual Codes CPI Container Element **
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="MCC" minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="MCC" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
** A Manual Code CPI **
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="EngPIs">
<xsd:annotation>
<xsd:documentation>
**General & Mechanical Sections Container element**
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="EngPI" minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EngPI">
<xsd:annotation>
<xsd:documentation>
UNIQUE ELEMENT EngPIs
** General & Mechanical Sections EngPI is composed of sections
P and Q. Any combination is allowed, with at least one section.
There are no manual codes for these sections.
Each single EngPI section is composed of
one or more Derwent Class Engineering (DCEng) elements.
No section can appear twice. The DTD does not enforce this.
Attribute section= an allowed Derwent EngPI section **
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="DCEngs" minOccurs="1" maxOccurs="1"/>
</xsd:sequence>
<xsd:attribute name="sct" use="required">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="P"/>
<xsd:enumeration value="Q"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="DCEngs">
<xsd:annotation>
<xsd:documentation>
** Derwent Class Engineering Container eement **
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="DCEng" minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="DCEng" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
** Derwent Class Engineering **
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="EPIs">
<xsd:annotation>
<xsd:documentation>
** Electronic & Electrical Sections EPI **
Container element for EPI
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="EPI" minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPI">
<xsd:annotation>
<xsd:documentation>
UNIQUE ELEMENT EPIs
** EPI is composed of sections R to X. Any combination is allowed,
with at least one section.
Section R can't be on his own. The DTD does not enforce this.
Each single is composed of one or more Derwent Class Electronic
and Electrical (DCE) elements.
No section can appear twice. The DTD does not enforce this. **
Attribute sct = an allowed Derwent EPI section
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="EPIgp" minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="sct" use="required">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="R"/>
<xsd:enumeration value="S"/>
<xsd:enumeration value="T"/>
<xsd:enumeration value="U"/>
<xsd:enumeration value="V"/>
<xsd:enumeration value="W"/>
<xsd:enumeration value="X"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPIgp">
<xsd:annotation>
<xsd:documentation>
** A Container element to group the related DCE & MCEs elements **
Note that content MCEs is optional as its optional in the backfile
before 19??
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence minOccurs="1" maxOccurs="1">
<xsd:element ref="DCE" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="MCEs" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="DCE" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
** Derwent Class Electronic & Electrical (DCE) contains
Manual Codes Electronic & Electrical (MCE) **
** Derwent Class EPI **
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="MCEs">
<xsd:annotation>
<xsd:documentation>
** Manual Codes EPI container element **
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="MCE" minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="MCE" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
** A Manual Code EPI **
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="IPCs">
<xsd:annotation>
<xsd:documentation>
********************IPCs Container element *************
** The following xlink construct is a link to the IPC codes on
the WIPO site, this could be added to the DTD to provide the link
without adding any thing to the individual instances
xlink:type (locator) #FIXED "locator"
xlink:rl NMTOKEN #FIXED "IPCs"
xlink:href CDATA #FIXED "http://classifications.wipo.int/fulltext/new_ipc/"
xlink:title CDATA #FIXED "IPC Codes" **
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="IPC" minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="IPC">
<xsd:annotation>
<xsd:documentation>
UNIQUE ELEMENT IPCs
** An IPC Code **
** Attribute rnk= Derwent assigned character to indicate type
of IPC:
A= Main IPC
B= Other, unlinked IPCs
C to Y = Linked IPCs and Index Terms
Z= IPC Index Terms
-= Additional terms **
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="rnk" use="required">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="A"/>
<xsd:enumeration value="B"/>
<xsd:enumeration value="C"/>
<xsd:enumeration value="D"/>
<xsd:enumeration value="E"/>
<xsd:enumeration value="F"/>
<xsd:enumeration value="G"/>
<xsd:enumeration value="H"/>
<xsd:enumeration value="I"/>
<xsd:enumeration value="J"/>
<xsd:enumeration value="K"/>
<xsd:enumeration value="L"/>
<xsd:enumeration value="M"/>
<xsd:enumeration value="N"/>
<xsd:enumeration value="O"/>
<xsd:enumeration value="P"/>
<xsd:enumeration value="Q"/>
<xsd:enumeration value="R"/>
<xsd:enumeration value="S"/>
<xsd:enumeration value="T"/>
<xsd:enumeration value="U"/>
<xsd:enumeration value="V"/>
<xsd:enumeration value="W"/>
<xsd:enumeration value="X"/>
<xsd:enumeration value="Y"/>
<xsd:enumeration value="Z"/>
<xsd:enumeration value="-"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="Frag">
<xsd:annotation>
<xsd:documentation>
***************BCE INDEXING OR FRAGMENTATION ************
** Fragmentation Container element**
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="FragSub" minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="FragSub">
<xsd:annotation>
<xsd:documentation>
UNIQUE ELEMENT Frag
** Fragmentation Sub heading **
** Attribute sjct=The main BCE chemical subject categories
defined by Derwent as subsets. The subsets are designated by the
subheadings MO through M6:
MO Agricultural, pharmaceutical 1963-1969
M1 Agricultural, pharmaceutical natural products
and polymers 1970 to present
M2 Agricultural, pharmaceutical 1970 to present
M3 General chemicals 1970 to present
M4 Dyes 1970 to present
M5 Steroids 1963 to present
M6 Galenicals 1976 to present"**
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="CardRec" minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="sjct" use="required">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="M0"/>
<xsd:enumeration value="M1"/>
<xsd:enumeration value="M2"/>
<xsd:enumeration value="M3"/>
<xsd:enumeration value="M4"/>
<xsd:enumeration value="M5"/>
<xsd:enumeration value="M6"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="CardRec">
<xsd:annotation>
<xsd:documentation>
** Card Record **
Attribute no =Derwent assigned record number
Attribute mc = Markush DARC Control Code
Attribute trc = Fragmentaion Control Time ranging codes:
M900 Pre-1970
M901 1970-1971
M902 1972-1981 (8126)
M903 1981 (8127) onward
M905
Attribute rn = 910 Codes generated from registry numbers.
Only searchable from 1981
Attribute wd = 911 Wide Disclosure. Only searchable from 1981
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence minOccurs="1" maxOccurs="1">
<xsd:element ref="FCodes" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="RINs" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="SCNs" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="MCNs" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="DRNs" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="DCRs" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
-
Null value for int and datetime date type in xml schema
hi:
I am embarrassed by a qustion in xml schema; i defined a xml schema file like
this:
<elementFormDefault="qualified" attributeFormDefault="qualified">
<xs:element name="test">
<xs:annotation>
<xs:documentation>Comment describing your root element</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="xs:string"/>
<xs:element name="password" type="xs:string" nillable="true"/>
<xs:element name="user" type="xs:int" nillable="true"/>
<xs:element name="s_time" type="xs:dateTime"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
and I send this file to workflow clientrequest() node, I wanted to receive data
in this schema file.but when i send null value to the element "user" and "s_time"
in workshop test tool(test soap),and use function in xmlbean like isNilUser or
isNilStime, one error occur.
I don't kown why, I had to ask the engineer of bea in china, one told me a bug.
is that true?Visakh16 I cant agree more with you on it, it is good but in production u cant have them change maxrows. I think
Patrick Hurst is a better option. debug the package have it running and move up
Please mark as helpful and propose as answer if you find this as correct!!! Thanks,Dia Agha .
Hmm..Why do you need to change it in production?
What I suggested was to tweak the setting in dev machine so that it interprets the Excel file datatypes correctly when doing development. Once mapping is set correctly then it will work fine when in production or in any other environment. The tweaking is
just to make sure it interprets the datatype correctly at design time and has nothing to do with production deployment
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page -
Leading ? xml version="1.0"? tag when creating / invoking web services
Hello friends. I'm wondering if anyone has any insight as to why I cannot create
a fully formed XML document when developing a web service which includes the standard
<? xml version="1.0" ?> leading tag.
If I include the leading tag in my XML mapping for a jws method, I am unable to
compile the service into an ear, getting the following error: "An unexpected
exception occurred while attempting to process the classes and annotations for
this Web Service." If I do not include the leading tag, I can compile into an
EAR file and invoke the web service from a HTTP POST, but I cannot include the
leading <?xml...> tag in my request. Considering that I'll be asking other vendors
to submit to my web services and creation of xml documents using DOM or other
methods automatically generates the <?xml ...>, I'm hoping I'm not going to have
to tell them to parse out this piece of the files they want to send me. Can anyone
help?
Thanks so much!
CMCM,
I suppose you have set 'http-xml=true' for this to work. For http-xml
protocol, there is no way to specify the leading <?xml> tag, and hence
unfortunately the desired functionality cannot be achieved.
In case, this is very important for you, could you please log a support
case, and then we can file a bug and ask the Engineering to look into it.
Thanks,
Anurag
"Crackhead Millionaire" <[email protected]> wrote in message
news:[email protected]...
>
Hi Anurag -
Thanks for the response. My problem is that I would like to be able tosubmit
straight XML (i.e., not SOAP) to a webservice from an application outsideof Weblogic.
For example, the following code block fails on submission to BEA:
* Example Simple Integration.
import java.io.*;
import java.net.*;
public class testBEAPost {
* Null constructor.
public testBEAPost () {
super();
* This method handles creation of a PeopleSoft XML Envelope, wrapping of
* user input into the envelope, submission of the message to theintegration
broker
* and display of the response message to the screen.
* @created 3.12.2003
* @param argv java.lang.String[] Standard user entry input
public static void main(String[] argv) {
try{
URL url;
URLConnection urlConn;
DataOutputStream printout;
DataInputStream input;
// Create the internal XML document which will be to send to BEA.(hardcoded)
>
String internalXMLDoc = "<? xml version=\"1.0\"?><newlocationxmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"><setid>WMS</setid><l
ocationid>1118UG0000</locationid><description>Electric
UndergroundLocation</description><exceptionemailaddress>[email protected]<
/exceptionemailaddress></newlocation>";
>
// Define the target URL.
url = newURL("http://167.75.117.20:7001/WebServices/PeopleSoftWebServices/NewLocation
Service.jws/createLocation");
>
// Open the Conection
urlConn = url.openConnection();
// Set necessary connection variables.
urlConn.setDoInput (true);
urlConn.setDoOutput (true);
urlConn.setUseCaches (false);
// Specify the content type.
urlConn.setRequestProperty("Content-Type", "text/xml");
// Send POST output.
printout = new DataOutputStream (urlConn.getOutputStream ());
printout.writeBytes (internalXMLDoc);
printout.flush ();
printout.close ();
// Get response data.
input = new DataInputStream (urlConn.getInputStream ());
String str;
while (null != ((str = input.readLine())))
System.out.println (str);
input.close ();
} catch (Exception e)
System.out.println(e);
If I run this program, I get a java.io.IOException with the serverreturning a
500 error code. However, if I strip out the leading <? xml version="1.0"?> tag
and submit to the web service, it works fine. My program set I createdthis example
for uses DOM to create the document, so I'm actually creating thedocument, getting
the String value of it, then parsing out the leading tag beforesubmission. My
problem is that soon I'll be dealing with third parties who may havetrouble generating
SOAP requests (don't ask), so I'd like to be able to tell them to generatesimple
XML documents to send to BEA if at all possible.
Can you assist? Thanks so much.
"Anurag Pareek" <[email protected]> wrote:
CM,
A SOAP message generated by a Workshop web service, when it acts as a
client
to another service, always contains the leading <?xml> tag. Here is a
sample
of a SOAP message generated by Workshop:
POST /TestImport/TestAny/TestAny.jws HTTP/1.0
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client
Protocol 1.0.3705.0; BEA WLW 7.0)
SOAPAction: "http://www.openuri.org/hello2"
Host: localhost
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: Keep-Alive
Content-Length: 398
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>
<hello2 xmlns="http://www.openuri.org/">
<o></o>
</hello2>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
It seems to me that what you are asking for is already there. Could you
please elaborate your issue further, probably with a sample of a XML
message
which you feel is not accepted by Workshop, but should be.
Thanks,
Anurag
"Crackhead Millionaire" <[email protected]> wrote in message
news:[email protected]...
Hello friends. I'm wondering if anyone has any insight as to why Icannot
create
a fully formed XML document when developing a web service which
includes
the standard
<? xml version="1.0" ?> leading tag.
If I include the leading tag in my XML mapping for a jws method, Iam
unable to
compile the service into an ear, getting the following error: "Anunexpected
exception occurred while attempting to process the classes and
annotations
for
this Web Service." If I do not include the leading tag, I can compileinto an
EAR file and invoke the web service from a HTTP POST, but I cannotinclude
the
leading <?xml...> tag in my request. Considering that I'll be askingother vendors
to submit to my web services and creation of xml documents using DOMor
other
methods automatically generates the <?xml ...>, I'm hoping I'm notgoing
to have
to tell them to parse out this piece of the files they want to sendme.
Can anyone
help?
Thanks so much!
CM
Maybe you are looking for
-
English Version for Switzerland
Why can't I choose English for the Swiss Adobe website? It is very annoying if you're a foreigner and you're trying to purchase/find out any local information on adobe.com. Also, why isn't there a section for one to report bugs/features for the actua
-
Check for latest revision when form is opened
I'm developing a form for work that will be distributed to many people and I won't always know who has the form. My plan is to post the form to a website for users to download. Is there any way to check the website for for the latest revision when
-
hi, i have created below thread in SAP NetWeaver Administrator, but no response, thought i posted it to wrong category. https://forums.sdn.sap.com/click.jspa?searchID=15443307&messageID=6020795 i re-post the same question here, hope there is someone
-
Today my friend brought me his 160GB classic and it does the old Red X on me. So, I follow the "official" support tactic of booting into Disk Mode. Well, it just goes back the the Red X as if I haven't been pressing buttons. I check the buttons on Di
-
I create a BC4J project using the wizards, and select a few tables. I create default view objects for a couple of the entity objects, and create one view link between them. When I try to insert a record into any view object (using any client), Entity