XML Document not Valid

Hi Techies,
I m making a xml document and that is validated on xml schema. But it is giving error that document is not valid because it is not deg\fining DOCTYPE element. Is it necessary to define it

It is not nesessary, but you have probably made your parser validating. In Java validating parsers use DTD to validate, and while schema validation is possibly those parsers are non-validating.

Similar Messages

Supplied XML is not valid

Hi All,
While refreshing a Webi report, I am getting following error:
"A database error occured. The database error text is: The supplied XML is not valid. [Measures].[0701FBYSYG9KJQ47GRMMAVZ89]. (WIS 10901) ".
Could you please let me know how to resolve it?
Regards,

definition of one of your measure objects selected in the webi query is not correct in the universe. Parse the objects in the universe and find the objects with incorrect definition. This may be due to deletion of a key figure from BEx query. You can refresh the universe structure for updating it.

DPM 2012 R2 install fail - Reporting services "definition contains XML that is not well-formed or the XML is not valid"

Hi Everyone,
I've been battling with this for a while and I'm getting nowhere. I'm attempting to install DPM 2012R2 onto a fresh VM with a local SQL installation. The setup is as follows:
Server OS: 2008R2 SP1
SQL: 2008 R2 standard with SP3(tried SP2 before this)
Collation: SQL_Latin1_General_CP1_CI_AS
Reporting services installed: Yes(ticked do not configure during the installation)
Enabled reporting servics on port 80 with the default URL
DPM Installation does not throw any errors during the preinstall stage(The server passes all the checks)
Basically, when Installing. I get this error(extract):
at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.DeployFileInServer(Boolean recreate, ReportDBInfo rptInfo)
at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.DeployReports(String sourceFolderPath, Boolean recreate, Boolean calledFromSetup)
at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.InstallReports(Boolean calledFromSetup, String sourceFolderPath, String sqlServerName, String sqlInstanceName, String dbConnectionString)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.DeployReports(Boolean isRemoteReporting, String sqlMachineName, String sqlInstanceName, String rsMachineName, String rsInstanceName, String installerPath)
[10/12/2014 2:35:25 p.m.] * Exception : => Report configuration failed.Verify that SQL Server Reporting Services is installed properly and that it is running.Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.BackEndErrorException: exception
---> Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.ReportDeploymentException: exception ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException:
exception ---> System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: The report definition is not valid or supported by this version of Reporting Services. This could be the result of publishing a report definition of
a later version of Reporting Services, or that the report definition contains XML that is not well-formed or the XML is not valid based on the Report Definition schema. Details: Root element is missing.
at Microsoft.ReportingServices.WebServer.ReportingService2005Impl.CreateReport(String Report, String Parent, Boolean Overwrite, Byte[] Definition, Property[] Properties, Warning[]& Warnings)
at Microsoft.ReportingServices.WebServer.ReportingService2005.CreateReport(String Report, String Parent, Boolean Overwrite, Byte[] Definition, Property[] Properties, Warning[]& Warnings)
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.Internal.EnterpriseStorage.Dls.UI.Reporting.ReportingService2005.CreateReport(String Report, String Parent, Boolean Overwrite, Byte[] Definition, Property[] Properties)
at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.CreateReport(String pathOfReport, ReportDBInfo rptInfo)
--- End of inner exception stack trace ---
at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.CreateReport(String pathOfReport, ReportDBInfo rptInfo)
at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.DeployFileInServer(Boolean recreate, ReportDBInfo rptInfo)
at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.DeployReports(String sourceFolderPath, Boolean recreate, Boolean calledFromSetup)
at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.InstallReports(Boolean calledFromSetup, String sourceFolderPath, String sqlServerName, String sqlInstanceName, String dbConnectionString)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.DeployReports(Boolean isRemoteReporting, String sqlMachineName, String sqlInstanceName, String rsMachineName, String rsInstanceName, String installerPath)
--- End of inner exception stack trace ---
at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.DeployReports(Boolean isRemoteReporting, String sqlMachineName, String sqlInstanceName, String rsMachineName, String rsInstanceName, String installerPath)
at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.DeployReports(String reportserverConfigFilePath, Boolean isOemSetup, String sqlMachineName, String sqlInstanceName, Boolean isRemoteReporting, String reportingServerMachineName, String
reportingInstanceName)
--- End of inner exception stack trace ---
at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.DeployReports(String reportserverConfigFilePath, Boolean isOemSetup, String sqlMachineName, String sqlInstanceName, Boolean isRemoteReporting, String reportingServerMachineName, String
reportingInstanceName)
at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.DpmInstaller.DeployReports(Boolean isRemoteReporting, Boolean isUpgrade)
at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ProgressPage.InstallerThreadEntry()
*** Mojito error was: ReportDeploymentFailed; 0; None
[10/12/2014 2:35:25 p.m.] *** Error : Report configuration failed.
Verify that SQL Server Reporting Services is installed properly and that it is running.
ID: 812
[10/12/2014 2:35:25 p.m.] Information : Data Protection Manager installation has failed. All the items that were copied during the installation process have been removed.
For details, click the Error tab.
Any ideas?
I've managed to get it to this stage. Originally I didn't have encryption keys or a listening port(which I fixed).

Can you try following steps:
If there are SSL certificates on your computer, by default SQL 2008
installation configures HTTPS for reporting websites. When DPM tries to
deploy reports on these websites it may fail if the reporting websites
are not accessible (might be due to invalid/expired certificates). To
workaround this, provided you do not require HTTPS for reporting websites do
the following:
1. Edit C:\Program Files\Microsoft DPM\SQL\MSRS10.MSDPMV3BETA1EVAL\Reporting
Services\ReportServer\rsreportserver.config
2. Set the SecureConnectionLevel to 0 if the current value is 2 (A value to
2 means secure connection is required)
3. Connect to SQL reporting service configuration manager and connect to the
instance MSDPMV3BETA1EVAL
4. Click on Web Service URL, click advanced and remove SSL identities
5. Repeat the above for Report Manager URL
6. Make sure report manager URL and web service URL are accessible with out
any errors.
6. Restart report server
If that doesn't solve the problem, please try following steps:
1. Open Start-> All programs->SQL server 2008->Configuration Tools->Report
Server Configuration Manager
2. Connect to the instance which the DPM is using to install.
3. Browse Report Manager URL and web service url
4. If report manager URL or web service url throws any error say 500 or 404
fix the error. (Try also replacing machine name with localhost in url)
5. Otherwise delete DPMReports folder (if present) using below instructions
6. Restart reporting services
7. Try DPM setup again.
Deleting DPM reports:
1. Open report manager URL in IE
2. Click show details on right hand side
3. Put a tick against DPMReports folder
4. Click Delete button.
Regards, Trinadh [MSFT] This posting is provided AS IS with no warranties, and confers no rights. If you found the reply helpful, please MARK IT AS ANSWER. Looking for source of information for DPM? http://blogs.technet.com/b/dpm/ http://technet.microsoft.com/en-in/library/hh758173.aspx

Parse failed: Exception DBD, The supplied XML is not valid[Measures].[SAP_OBJECT_NAME] State:N/A error for hidden KFs when migrated to HANA

Hi All
Please help me with the following query. We are migrating SAP BW 7.4 on Oracle to HANA. We have few WEBI report's universes built on BEx queries. In one of those reports there are some hidden RKFs, these works perfectly fine in reports based on oracle. Now we migrated to HANA in development system and when i refresh the universe structure they started giving errors like "Parse failed: Exception DBD, The supplied XML is not valid[Measures].[SAP_OBJECT_NAME] State:N/A". The object giving this error is in hidden state. I tried to unhide it and run the report then it runs fine but that not the client want as there might be so many hidden KFs in other reports also. BO version is 4.1 SP 2. We are on SAPKW74006 support package on BW side. Is there any notes to correct this error. Please pass me the relevant links. Highly appreciate your help.
Thanks
Dwaraka

DCA-40012: The Web Service call failed. A connection to the target Web Service could not be created.
First of all test the web service you have created in model project. Right click the web service name and select "Test WebService". If you see any issue(s) while testing fix it first before you run the jspx page.
Check the port number in the URL and connections.xml, it have to be same.

SAP BW query to BOBJ Universe: The supplied XML is not valid.

Help!
The Business Objects Sever XI is giving us messages like the below, on some but not all BOBJ Universes based on SAP BW queries.
A database error occurred. The database error text is: The supplied XML is not valid. [various InfoObjects] [LEVEL01] (WIS 10901)
These queries were executing 1 working day, 3 calendar days ago. No transports to SAP BW or promotions to BOBJ were made.
Any ideas?
Thanks,
John Hawk
When we refresh the Universe, we get this mesdage
Error getting hierarchies for dimension 0INFOPROV (Cube FIGL_M10/FIGL_M10_Q001): Exception condition "HIERARCHY_NOT_FOUND" raised
Edited by: John Hawk on Jun 1, 2010 9:15 PM

Hi John,
I'm also getting same error 'Error getting hierarchies for dimension 0INFOPROV (Cube ZLE_M10/YBO_FREIGHT_ZLE_M10_UNIV_MPT1): Unknown error' when tried to create universe on top of query which is based on multi provider. Could you please send me copy of program ZZ_REPAIR_HIEDIR?
Thanks,
Milind

Serializing XML Documents(not Java Serialization)

Hi,
Iam looking for a class that can serialize the XML documents.
Heres the problem in detail:
- I need to create an XML String from scratch taking data from a database.
- I created the XML Document adding the childs and attributes.
- I need an XML string from the document. Iam not exactly sure how to do this. But Apache Xerces package provides an XMLSerializer class where we can convert the document into a string.
Is there any functionality provided. If so where can i find it.
Thanks,
-Rao

Not sure if this is a bug or not (filing one just in case it is) but the following program demonstrates that with 2.0.2.9 the internal subset is serialized correctly if the document was parsed with validationMode set to true. If set to false only the entities show up in the internal subset.
package xmlbugs;
import java.io.*;
import org.w3c.dom.*;
import oracle.xml.parser.v2.*;
public class TestSerializeLocalSubset {
private static final String xml =
"<?xml version='1.0' encoding='UTF-8'?>"+
"<!DOCTYPE bar ["+
"<!ENTITY bar 'baz'>"+
"<!ELEMENT foo EMPTY >"+
"<!ELEMENT bar (foo) >"+
"]>"+
"<bar><foo/></bar>";
public static void main(String[] a_ ) throws Exception {
System.out.println("Test with parser in validation mode = false");
DOMParser d = new DOMParser();
d.setPreserveWhitespace(false);
d.setValidationMode(false);
d.parse( new StringReader(xml));
Document x = d.getDocument();
XMLDocument xx = (XMLDocument) x;
xx.print(System.out);
System.out.println("Test with parser in validation mode = true");
DOMParser d2 = new DOMParser();
d2.setPreserveWhitespace(false);
d2.setValidationMode(true);
d2.parse( new StringReader(xml));
x = d2.getDocument();
xx = (XMLDocument) x;
xx.print(System.out);
}

9.0.3 validates an invalid XML document as valid

JDeveloper 9.0.3 validates the XML document below with no errors, although it contains several. It also insists on a namespare (even a blank one) before the validator will run, even though it has an internal DTD.
Also, there is no DTD file type in JDeveloper. Why?
-----------------------Clip here-----------
<?xml version="1.0"?>
<!DOCTYPE todo [
<!ATTLIST description priority NMTOKEN "low">
<!ELEMENT description (#PCDATA)>
<!ELEMENT task (description)>
<!ELEMENT todo (task)+>
]>
<todo xmlns="">
<task>
<description priority="high">Backup sales data for last month</description>
</task>
<task>
<description priority="l ow">Complete end of month report</description>
</task>
<task>xxx</task>
</todo>

Ed,
JDev 9.0.3 supports validation based on XML Schema only, not DTD.
DTD validation is being considered for a future release, but has not
been scheduled yet so I cannot give you an idea of when it's coming.
I'll try to encourage the team to write a little Extension we could
put up on OTN to restore this validate against the DTD feature that
JDeveloper 3.2 did support.

Writing to an xml document, not working.

Hey all,
I'm trying to do something pretty simple, just setting up a phone forwarding script (I believe it is the one that came with CCX) that reads XML documents to forward and unforward the phones. But I cant for the life of me get the script to actually write to a status file on ccx. Please take a look at my script and help me out.

Figured it out. You have to write to a different directory.

XML Document Not working / Capture device problems HELP!

Whenever i open the xml file from justin.tv it always says "Log File Cannot Be Created," then ist says "Profile Vlidation"
And whenever i select my captutre card it always says " Problem With Video Capture Device"
Somone please help me!
(i have attached the xml file that keeps on crashing for me)

You are getting "Log File Cannot Be Created" error because when you download XML file from someone else computer then FMLE by default folder takes path for Log file as his "My Videos" folder. So while checking the profil, FMLE gets to know that this profile is not perfect and hence gives "Profile Validation Error" and then silently corercts those errors. After clicking OK on "Profile Validation error" window, you can go to Encoding log tab and check the changes that were made in FMLE on above the settings of your XML profile file.
You are getting "Problem With Video Capture Device" because either the drivers of your device are not corerctly isntalled on your machine or your device is busy with some other application or your device is not connected properly. Please check the drivers and connectivity of your device and make sure that your device gives RAW/Uncompressed Video format only

Orion-ejb-jar.xml is not valid

I am trying to parse orion-ejb-jar.xml as follows:
package test;
import javax.xml.parsers.*;
import org.w3c.dom.*;
import org.apache.xml.serialize.*;
import org.xml.sax.*;
import java.io.*;
public class GetFieldSize {
String filePath = null;
Document document = null;
public GetFieldSize(String filePath) {
this.filePath = filePath;
public void constructDocument() {
try {
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
DocumentBuilder builder = factory.newDocumentBuilder();
builder.parse(new InputSource(new FileReader(filePath)));
} catch (FactoryConfigurationError fce) {
fce.printStackTrace();
} catch (ParserConfigurationException pce) {
pce.printStackTrace();
} catch (SAXException se) {
se.printStackTrace();
} catch (IOException ie) {
ie.printStackTrace();
public static void main(String[] args) {
GetFieldSize getFieldSize = new GetFieldSize("Z:\\nosqms\\ProcessTools\\qTools\\qTools\\qTools\\src\\META-INF\\orion-ejb-jar.xml");
getFieldSize.constructDocument();
I got the following parse error.
oracle.xml.parser.v2.XMLParseException: Expected '>'.
void oracle.xml.parser.v2.XMLError.flushErrors()
void oracle.xml.parser.v2.NonValidatingParser.parseMarkupDecl()
void oracle.xml.parser.v2.NonValidatingParser.parseDoctypeDecl()
void oracle.xml.parser.v2.NonValidatingParser.parseProlog()
void oracle.xml.parser.v2.NonValidatingParser.parseDocument()
void oracle.xml.parser.v2.XMLParser.parse(org.xml.sax.InputSource)
org.w3c.dom.Document oracle.xml.jaxp.JXDocumentBuilder.parse(org.xml.sax.InputSource)
void test.GetFieldSize.constructDocument()
void test.GetFieldSize.main(java.lang.String[])
When I opened the orion-ejb-jar.xml in IE, I got the following error:
A string literal was expected, but no opening quote character was found. Line 87, Position 1
CDATA #IMPLIED
Seems like problem with http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd.
How to rectify it?

1: Replace
isolation (committed | serializable | uncommitted | repeatable_reads)
CDATA #IMPLIED
locking-mode (pessimistic | optimistic | read-only | old_pessimistic)
by
isolation (committed | serializable | uncommitted | repeatable_reads) #IMPLIED
locking-mode (pessimistic | optimistic | read-only | old_pessimistic) #IMPLIED
2: in
<!ELEMENT ior-security-config (transport-config?, as-context?
sas-context?) >
add the final comma:
<!ELEMENT ior-security-config (transport-config?, as-context?, sas-context?) >

Parse failed: Exception: DBD, The supplied XML is not valid?

Hi,
I have created a OLAP Universe on top of SAP BEx Query which is having Filters. Below is code generated by Universe Designer Tool ...
<FILTER KEY="[!V000002]"><CONDITION OPERATORCONDITION="Between"><CONSTANT TECH_NAME="@Prompt('Calendar Month Interval From','A','Calendar Year/Month\LovCalendar Month IntervalBase',mono,primary_key)"/><CONSTANT TECH_NAME="@Prompt('Calendar Month Interval To','A','Calendar Year/Month\LovCalendar Month IntervalBase',mono,primary_key)"/></CONDITION></FILTER>
Can anyone suggest me how to solve this.
Regards,
Ramana.

Hi all,
Just refresh the universe structure and parse it and export it.
Actually the issue is, SAP BEx Query and its filters was changed after i have created Universe so what i have done is , created a new universe and named tat universe with the actual universe name.
So the filters parsing got success.

Validation of XML document % DTD

I need method which allows to check if an XML document is valid regards its DTD. is it possible?
I use JDOM.
thanks,

I need method which allows to check if an XML
document is valid regards its DTD. is it possible?
I use JDOM.But it would be the parser that validates the XML against its DTD. JDOM is not a parser, it uses some other product (which you can specify, I believe) to do the parsing. So the answer would be yes, since parsers do exist that can validate against a DTD.

XML SAX dtd Validation Problem

Hi,
          I’m having problems getting an xml document to validate within Weblogic 8.1. I am trying to parse a document that references both a dtd and xsd. Both the schema and dtd reference need to be substituted so they use local paths. I specify the schema the parser should use and have created an entityResolver to change the dtd reference.
          When this runs as a standalone app from eclipse the file parses and validates without a problem. When deployed to the app server the process seems to be unable read the contents of the dtd. Its not that it cannot find the file (no FileNotFoundException is thrown but this can be created if I delete the dtd) rather it seems to find no declared elements.
          Initial thought was that the code didn’t have access to read the dtd from its location on disk, to check I moved the dtd to within the deployed war and reference as a resource. The problem still persists.
          Code Snippet:
          boolean isValid = false;
          try {
          // Create and configure factory
          SAXParserFactory factory = SAXParserFactoryImpl.newInstance();
          factory.setValidating(true);
          factory.setNamespaceAware(true);
          // To be notified of validation errors in the XML document,
          // add a custom error handler to the document builder
          PIMSFeedFileValidationHandler handler
          = new PIMSFeedFileValidationHandler();
          // Create and Configure Parser
          SAXParser parser = factory.newSAXParser();
          parser.setProperty(JAXP_SCHEMA_LANGUAGE, W3C_XML_SCHEMA);
          parser.setProperty(NAMESPACE_PROPERTY_KEY, getSchemaFilePath());
          // Set reader with entityResolver for dtd
          XMLReader xmlReader = parser.getXMLReader();
          xmlReader.setEntityResolver(new SAXEntityResolver(this.dtdPath));
          // convert file to URL, as it is a remote file
          URL url = super.getFile().toURL();
          // Open an input stream and parse
          InputStream is = url.openStream();
          xmlReader.setErrorHandler(handler);
          xmlReader.parse(new InputSource(is));
          is.close();
          // get the result of parsing the document by checking the
          // errorhandler's isValid property
          isValid = handler.isValid();
          if (!isValid) {
          LOGGER.warn(handler.getMessage());
          LOGGER.debug("XML file is valid XML? " + isValid);
          } catch (ParserConfigurationException e) {
          LOGGER.error("Error parsing file", e);
          } catch (SAXException e) {
          LOGGER.error("Error parsing file", e);
          } catch (IOException e) {
          throw new FeedException(e);
          return isValid;
          See stack trace below for a little more info.
          2005-01-28 10:24:09,217 [DEBUG] [file] - Attempting validation of file 'cw501205.wa1.xml' with schema at 'C:/pims-feeds/hansard/schema/hansard-v1-9.xsd'
          2005-01-28 10:24:09,217 [DEBUG] [file] - Entity Resolver is using DTD path file:C:/Vignette/runtime_services/8.1/install/common/nodemanager/
          VgnVCMServer/stage/pims-hansard/pims-hansard.war/WEB-INF/classes/com/morse/pims/cms/feed/sax/ISO-Entities.dtd
          2005-01-28 10:24:09,227 [DEBUG] [file] - Creating InputSource at: file:C:/Vignette/runtime_services/8.1/install/common/nodemanager/VgnVCMServer/stage/pims-hansard/pims-hansard.war/WEB-INF/classes/com/morse/pims/cms/feed/sax/ISO-Entities.dtd
          2005-01-28 10:24:09,718 [WARN ] [file] - org.xml.sax.SAXParseException: Element type "Hansard" must be declared.
          org.xml.sax.SAXParseException: Element type "Session" must be declared.
          org.xml.sax.SAXParseException: Element type "DailyRecord" must be declared.
          org.xml.sax.SAXParseException: Element type "Volume" must be declared.
          org.xml.sax.SAXParseException: Element type "Written" must be declared.
          org.xml.sax.SAXParseException: Element type "WrittenHeading" must be declared.
          org.xml.sax.SAXParseException: Element type "Introduction" must be declared.
          … continues for all the elements in the doc
          2005-01-28 10:24:10,519 [DEBUG] [file] - XML file is valid XML? false
          2005-01-28 10:24:10,519 [WARN ] [file] - Daily Part file 'cw501205.wa1.xml' was not valid XML and was not processed.
          Has anybody seen this behavior before with weblogic and if so how have you resolved the issue.
          Thanks in Advance
          Adam

It looks like you clicked on "Post" before you got around to explaining your problem. I don't see any error messages or any description of what was supposed to happen and what happened instead.
Now, I don't know anything about XML Schema, but just guessing at how that unique name feature might be designed, and just guessing that your unique name is actually in the <userId> element, I would suggest that this:
<xsd:unique name="un_name">
<xsd:selector xpath="USER"/>
<xsd:field xpath="."/>
</xsd:unique> is at fault because it doesn't mention the <userId> element anywhere.

Problem to validate XML document if the type of root element is abstract

I have the following XML document:
<?xml version="1.0" encoding="UTF-8"?>
<ct013/>
It corresponds to the following XSD Schema:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="ct013" type="foo"/>
     <xs:complexType abstract="true" name="foo"/>
     <xs:complexType name="fixedType">
          <xs:complexContent>
               <xs:restriction base="foo"/>
          </xs:complexContent>
     </xs:complexType>
</xs:schema>
Please take attention to the fact that the type of root element of that BDD is abstract.
XML Schema provides a mechanism to force substitution for a particular element or type. When an element or type is declared to be "abstract", it cannot be used in an instance document. When an element is declared to be abstract, a member of that element's substitution group must appear in the instance document. When an element's corresponding type definition is declared as abstract, all instances of that element must use xsi:type to indicate a derived type that is not abstract.
Declaring an element as abstract requires the use of a substitution group. Declaring a type as abstract simply requires the use of a type derived from it (and identified by the xsi:type attribute) in the instance document.
For more information of using abstract types please see chapter 4.7 Abstract Elements and Types of XML Schema Part 0: Primer Second (http://www.w3.org/TR/xmlschema-0/#abstract).
In this case there is Oracle bug when I try to validate this XML document using Oracle XDK:
String validate(String xml, String schema)
throws XSDException, XMLParseException, SAXException, IOException
System.setPropert("oracle.xml.parser.debugmode", "true");
XSDValidator xsdValidator = new XSDValidator();
XMLError xmlError = new XMLError();
xmlError.setErrorHandler(new DocErrorHandler());
XMLDocument xmlDocument = parseXMLDocument(xml);
XMLDocument schemaXMLDocument = parseXMLDocument(schema);
XMLSchema xmlSchema = (XMLSchema) new XSDBuilder().build(schemaXMLDocument, null);
xsdValidator.setError(xmlError);
xsdValidator.setSchema(xmlSchema);
xsdValidator.validate(xmlDocument);
return getValidationError(xsdValidator);
I get the following error:
Can't find resource for bundle oracle.xml.mesg.XMLResourceBundle, key XSD-2046.
I tried to validate this XML document using two other libraries - XSD Schema Validator (http://apps.gotdotnet.com/xmltools/xsdvalidator/Default.aspx) and xsdvalid-29 (http://www.w3.org/XML/Schema#XSDValid). Both libraries pointed me on the error that the type of root element is abstract and it cannot be used for doing validation.
I think that Oracle should return me explaining message but not to throw exception.
Am I right? Is there really Oracle bug or I miss something?
Any help, hits, advices would be gratfully apriciated.

Define Element1 as follows:
<xs:element name="Element1">
<xs:complexType>
<xs:complexContent>
<xs:restriction base="xs:string"/>
</xs:complexContent>
</xs:complexType>
</xs:element>
Does the XML document get validated if the element is specified as
<Element1></Element1>

Invalid XML Document in BPEL Human Task - TaskService

Hi Experts
I am getting the following run time error in BPEL console in my bpel process which has got a human task.
==================================================================
Invalid xml document.*
According to the xml schemas, the xml document is invalid. The reason is: Error::cvc-datatype-valid.1.2.1: '' is not a valid value for 'dateTime'.*
Error::cvc-type.3.1.3: The value '' of element 'expirationDate' is not valid.*
Please make sure that the xml document is valid against your schemas.*
==================================================================
BPEL console is validating all incoming and outgoing XML document against the relevant schema since the configuration property, validateXML has
set to strict in the BPE console domain, which it has to be.
This complain is regarding the element expirationDate in the response message of the human task, which cannot be explicitly set in the bpel process.
Please help me to resolve this issue.
Thanks
Jamith

Hi
This has been escalated to Oracle and has been identified as a bug.
Anyway, can you please explain bit more about you workaround?
Thanks
Jamith

XML Document not Valid

Similar Messages

Maybe you are looking for