XML validation fails

Hello,
We are trying to validate an XML against a DTD using XDK 9.2.0.5.0 and it fails. The same XML was validated without any problem earlier, but, suddenly started failing with the following error.
XML-0201: (Fatal Error) Expected name instead of .
If I open the above XML in XMLSPY or any other XML parsing tools, the tool is showing as valid xml file.
Interestingly, if I add a whitespace after encoding statement,but, before ? (<?xml version="1.0" encoding="us-ascii" ?>), the XML is valid with the XDK.
If I remove the whitespace (<?xml version="1.0" encoding="us-ascii"?>), the XML is invalid with XDK.
What could have been a problem ?
Thanks for your time.
Satya

Does the error get generated with encoding utf-8.

Similar Messages

Inbound XML validation failed against schema

Hi Experts,
we are getting mapping exception at the time of Inbound XML validation but in the trace it is not displaying
like which fields are not validating.
I have gone through the Interface mapping in that we are using 2 mapping programs one is imported archives(java mapping) for validation
and another one is for Messaging mapping.we are getting the problem at the time of validation itself,
i have navigated by double clicking on the imported archive mapping program it is taken into another page
where we will get the archive programs.we have soo many xsd files and its path, and one .java file and class file
for validatting the xsd files. up to now everything is fine.
please find the remaining question in the below post

CONTINUATION QUESTION FOR THE ABOVE
If i click on the xsd files it is displaying the complete schema structure, but in the case of 2 xsd files(those are using in one
interface where we are getting validation error)it is displaying the error like "cannot display file com/AAA/BBB/java/CCC/xi/bc/validator/xsds/<filename.xsd> unable to determine code".as per my assumption the xsd file
is not present in that perticular path, if so how can i put these xsd files into the path specified? how can i get that folders to nagvigate into that path? And also i am not able to download the xsd file from the external defination, is it work if i copy the file into note pad and by changing the extension as .xsd ?
We are using PI7.0, give me an idea how to resolve the issue
Thanks in Advance

[CC] Search for Workaround for old Bug: XML Validation fails

In Dreamweaver the validation of an XHTML document "as XML" fails.
Result:
An exception occurred! Type:NetAccessorException, Message:Could not open file: http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd[xml]
The bug seems to be very old:
http://forums.adobe.com/thread/874435
Do you know any workaround? Is there may be a plugin which can validate XML?
Thanks.

I appreciate your detailed answers, David. It's a pleasure to discuss with you
My own criterium, if a non-fixing is shameful or not, does not depend on the frequency of the usage of a function (by me or any other user).
It depends on the facts, that Adobe knows the bug since many years and that it is a bug in a very basic module - the search and replace module.
I take it as a proof of my assumption, that Adobe behaves arrogantly in many ways.
They just don't care about maintanance.
Thanks for filing the bug about "validate as xml".
I logged into my prerelease account (I took part some years ago). But it seems that I have no access to the bug database.
In my prerelease account there's no link to the bug database.
I agree with you, that concerns would have more chances to be read by developers when you talk about them in the pre release forums.
But my experiences with filing bugs are so disappointing, that I do not like to spend my time anymore for that.
While betatesting we had a "personal usability engineer" to talk to him. I talked a lot to him, constructively and polite. But in fact, he has no influence to the decisions which bugs will fixed and which not.
We can talk about the search and replace module in 10 years.
I'm sure it will look the same as today. It will have the same bugs as today. It will have the same functionality as today.
No improvement at all in such an important module.
That's my assumption based on the experience of the last 8 years.

XML Validation failing

Hi,
I have XSD file, My application generates xml file dynamically.
When validating my xml with the XSD i am getting below exception messages.please find the code of XSD amd XML files.
org.xml.sax.SAXParseException: cvc-pattern-valid: Value '300' is not facet-valid with respect to pattern '[0-2][0-9][0-5][0-9]' for type 'TimeValidation'.
org.xml.sax.SAXParseException: cvc-type.3.1.3: The value '300' of element 'StartTime' is not valid.
org.xml.sax.SAXParseException: cvc-complex-type.2.4.d: Invalid content was found starting with element 'AutoReplyText'. No child element is expected at this point.
XSD_Code_
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<xsd:schema><xsd:element name="AutoReplyReq"><xsd:complexType><xsd:sequence><xsd:element name="TransactionID" type="TransIDValidation"/><xsd:element name="MSISDN" type="MSISDNTYPE"/><xsd:element name="Action" type="Action"/><xsd:element name="AutoReplyElements" type="AutoReplyElements" minOccurs="0" maxOccurs="10"/></xsd:sequence></xsd:complexType></xsd:element><xsd:complexType name="AutoReplyElements"><xsd:sequence><xsd:element name="AutoReplyId" type="IdValidation" minOccurs="1"/><xsd:element name="KeyWordList" type="xsd:string" minOccurs="0"/><xsd:element name="AutoReplyText" type="TextValidation" minOccurs="0"/><xsd:element name="OARuleName" type="NameValidation" minOccurs="0"/><xsd:element name="OARuleType" type="OARuleType" minOccurs="0"/><xsd:element name="OAList" type="OAListValidation" minOccurs="0"/><xsd:element name="TBSRuleName" type="NameValidation" minOccurs="0"/><xsd:element name="TBSRuleType" type="OARuleType" minOccurs="0"/><xsd:element name="StartDay" type="DayValidation" minOccurs="0"/><xsd:element name="EndDay" type="DayValidation" minOccurs="0"/><xsd:element name="StartTime" type="TimeValidation" minOccurs="0"/><xsd:element name="EndTime" type="TimeValidation" minOccurs="0"/></xsd:sequence></xsd:complexType><xsd:simpleType name="TransIDValidation"><xsd:restriction base="xsd:int"><xsd:minInclusive value="1"/></xsd:restriction></xsd:simpleType><xsd:simpleType name="NameValidation"><xsd:restriction base="xsd:string"><xsd:minLength value="1"/><xsd:maxLength value="20"/></xsd:restriction></xsd:simpleType><xsd:simpleType name="TextValidation"><xsd:restriction base="xsd:string"><xsd:minLength value="1"/><xsd:maxLength value="160"/></xsd:restriction></xsd:simpleType><xsd:simpleType name="MSISDNTYPE"><xsd:restriction base="xsd:long"><xsd:pattern value="\d{10,21}"/></xsd:restriction></xsd:simpleType><xsd:simpleType name="OAListValidation"><xsd:restriction base="xsd:string"><xsd:pattern value="([0-9,]+)"/></xsd:restriction></xsd:simpleType><xsd:simpleType name="TimeValidation"><xsd:restriction base="xsd:int"><xsd:pattern value="[0-2][0-9][0-5][0-9]"/></xsd:restriction></xsd:simpleType><xsd:simpleType name="Action"><xsd:restriction base="xsd:string"><xsd:enumeration value="Subscribe"/><xsd:enumeration value="Activate"/><xsd:enumeration value="Update"/><xsd:enumeration value="Delete"/><xsd:enumeration value="Deactivate"/><xsd:enumeration value="Unsubscribe"/></xsd:restriction></xsd:simpleType><xsd:simpleType name="OARuleType"><xsd:restriction base="xsd:string"><xsd:enumeration value="All"/><xsd:enumeration value="Specific"/></xsd:restriction></xsd:simpleType><xsd:simpleType name="IdValidation"><xsd:restriction base="xsd:int"><xsd:minInclusive value="0"/><xsd:maxInclusive value="20"/></xsd:restriction></xsd:simpleType><xsd:simpleType name="DayValidation"><xsd:restriction base="xsd:int"><xsd:minInclusive value="1"/><xsd:maxInclusive value="7"/></xsd:restriction></xsd:simpleType></xsd:schema>
XML code
<?xml version="1.0"?>
<AutoReplyReq>
<TransactionID>5</TransactionID>
<MSISDN>919988776655</MSISDN>
<Action>Activate</Action>
<AutoReplyElements>
<AutoReplyId>4</AutoReplyId>
<KeyWordList>hhhhhhhhhhhhhhhhhhhhhhhkkkkkk</KeyWordList>
<OARuleName>ppppppppp</OARuleName><OARuleType>Specific</OARuleType><OAList>7458963251</OAList><TBSRuleName>ddfdfdf</TBSRuleName><TBSRuleType>Specific</TBSRuleType><StartDay>1</StartDay><EndDay>5</EndDay><StartTime>0</StartTime><EndTime>1300</EndTime><AutoReplyText>rrrrrrrrrrrrrrrrrrrrrr</AutoReplyText></AutoReplyElements></AutoReplyReq>
Please do needful in fixing this issue.

The value '300' of element 'StartTime' is not validAccording to that you have <StartTime>300</StartTime>
<StartTime>0</StartTime>According to that you have zero. However the exception doesn't agree with you.
Please do needful in fixing this issue.It is you that wil fix this issue. All you will get here is advice and guidance.

XML validation using javax.xml.validation

Hello,
I am trying to validate some xml against my xsd.
Here is my xml:
<host>
    <status>Unknown</status>
</host>Here is my xsd:
<?xml version="1.0"?>
                                                                                                                                                             <xsd:schema targetNamespace="blah"
        xmlns:tns="blah"
        xmlns:xsd="blah">
<xsd:simpleType name="Status">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="Unknown"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:element name="host">
   <xsd:complexType>
     <xsd:all>
       <xsd:element name="status" type="tns:Status"/>
     </xsd:all>
   </xsd:complexType>
</xsd:element>
                                                                                                                                                             </xsd:schema>My test code is:
        try
            DocumentBuilder parser = DocumentBuilderFactory.newInstance().newDocumentBuilder();
            Document document = parser.parse(new File("test.xml"));
            // Create a SchemaFactory capable of understanding WXS schemas.
            SchemaFactory factory = SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI);
            // Load a WXS schema, represented by a Schema instance.
            StreamSource schemaFile = new StreamSource(new File("schema.xsd"));
            Schema schema = factory.newSchema(schemaFile);
            // Create a Validator object, which can be used to validate the document
            Validator validator = schema.newValidator();
            // Validate the DOM tree.
            validator.validate(new DOMSource(document));
        catch(Exception e)
            fail("XML validation failed: " + e.getMessage());
        }I get the following error:
ERROR: 'cvc-elt.1: Cannot find the declaration of element 'host'.'
If i replace "type=tns:Status' in the "status" element with just "type=string", it works fine.
Does anyone have any idea what the problem is?
Thank you,
David

To daft_davy:
1. Your XSD document is invalid: the xmlns attribute of schema documents must always have the following value: "http://www.w3.org/2001/XMLSchema"
All other values will result in the following validation error:
org.xml.sax.SAXParseException: s4s-elt-schema-ns: The namespace of element 'schema' must be from the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
Your XSD should look like this:
<?xml version="1.0"?>
<xsd:schema targetNamespace="blah" xmlns:tns="blah" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:simpleType name="Status">
    <xsd:restriction base="xsd:string">
      <xsd:enumeration value="Unknown"/>
    </xsd:restriction>
</xsd:simpleType>
<xsd:element name="host">
    <xsd:complexType>
      <xsd:all>
        <xsd:element name="status" type="tns:Status"/>
      </xsd:all>
    </xsd:complexType>
</xsd:element>
</xsd:schema>2. Your XML document does not match the XSD schema (even if you use the one above) for the following reasons:
a) The root element of the XML document must be associated with the namespace defined by the targetNamespace attribute of the schema.
b) The "blah" namespace at the element <status> in the XML document has to be undeclared because there is no namespace declaration to this element in the schema document either. There are to ways to do this:
<host xmlns="blah">
<status xmlns="">Unknown</status>
</host>or:
<xxx:host xmlns:xxx="blah">
<status>Unknown</status>
</xxx:host>
To watertownjordan:
The namespace URI can be virtually any string, so you don't need to specify a valid URI to define a namespace.

Newbie help please: "Validation of XML file failed."

Hopefully my question is short and easy.
I'm a developer and haven't used FrameMaker before. However for unforeseen reasons, I've inherited our technical help documentation constructed in FrameMaker which I've never used. Unfortunately I'm under a very tight deadline and I'm attempting to update our already existing and fairly extensive application help files.
However, I'm getting a "Validation of XML file failed" error for 90% of our .xml help docs. I opened our .book file in FrameMaker fairly easily, and can see all of our .xml files. However the variables already embedded in the documents aren't being recognized and seem to be causing the above error. I've located our variable definition files (xml) in the concepts folder, but FrameMaker doesn't seem to recognize them. Any suggestions on what I can check or how I can get FM to refer to the variable definitions? I'm working with a new installation of FM, is there some setup I overlooked?
Many thanks,
dana.

Sheila and Rick,
Thank you both so much for your offer of help. My apologies for not replying earlier. Other 'emergencies' and priorities at work took me in other directions. It turns out another solution has been found for the time being. But thank you again for your replies. They say a lot about this community and its support. :)
Thanks again,
dana.

Xml validation in File to RFC Sync Scenario with Validation fails message

Hi All,
We are using PI 7.4 (Dual Stack) the Requirement is File to RFC Sync Scenario(File <---> RFC).and need to do XML validation against XSD Schema. if any Validations fails Response message should send back to sender.RequestResponseBean standard module is using for File to RFC Sync scenario but how to send the response message to sender if any validation fails. adapter level XML validation is not helpful for this requirement. please help out me how to achieve the requirement with graphical mapping.
Thanks in advance.

to validate schema you cannot solve it with graphical mapping but validating the schema in the AAE or the integration engine.
y recomend you to use the AAE validation at sender side, coz the sender system will be notified in case of schema errors.
The response will be validated at Integration Server level.
you can search in the forum, you will get many document about how to configure it.
take a look to my blog: PI 7.3 - XML Validation

XML Validation - How to raise an alert

Hi PI Experts,
I enabled XML validation at "Validtion by Adapetr Engine". Its working fine. But how to integrate XML validation error with Alert Monitoring. Please advise.
Here below the error from Audit log:
2010-03-18 18:33:13     Information     The application tries to send an XI message asynchronously using connection File_http://sap.com/xi/XI/System.
2010-03-18 18:33:13     Information     Backward validation is enabled
2010-03-18 18:33:13     Error     Unable to validate the message with message ID b01d356e-1801-4b93-29fb-9ed84b25c6a3
2010-03-18 18:33:13     Error     Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: cvc-enumeration-valid: Value '11' is not facet-valid with respect to enumeration '[1, 2, 3, 4, 5, 6, 7]'. It must be a value from the enumeration. at line 15, column 34
2010-03-18 18:33:13     Error     MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: cvc-enumeration-valid: Value '11' is not facet-valid with respect to enumeration '[1, 2, 3, 4, 5, 6, 7]'. It must be a value from the enumeration. at line 15, column 34
2010-03-18 18:33:13     Error     File processing failed with com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: cvc-enumeration-valid: Value '11' is not facet-valid with respect to enumeration '[1, 2, 3, 4, 5, 6, 7]'. It must be a value from the enumeration. at line 15, column 34
Thanks...
Ravi Kanakam

Hi Ravi,
Are you getting other adapter engine alerts? Or only you are not getting xml validation ones? Also take a look at this:
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
Regards,
---Satish

XML Validation: ignore non-XML-Header in XML-file(payload): any solutions?

Dear Experts,
after I finally managed to configure the XML Validation, we're facing the next problem:
The payload of the XML files looks like that:
Abcdef#ABCDEF
AbcDef#123
<?xml version="1.0" encoding="UTF-8"?><Document xmlns.....
as you can see, there's a header which is necessary. The XML Validation works fine if the header is removed manually for testing. If the header is not removed, the validation is not possible ("Content is not allowed in prolog.")
Is it possible to realise the validation WITH that header? Can I tell SAP PI to ignore the header? Or make any changes to the XSD file?
Thanks alot!

Hi Armin,
Armin Kern wrote:
> After leaving SAP PI, those 2 lines have to be in that exact place (before the XML part) for further processing. Just deleting it wouldn't be enought. Does the complex design you mentioned complay with this requirement?
You can put it into the message instead of deleting. And rebuild the "header" in the second step. So you can fullfill the requirement. As mentioned before: The design is complex, this will lead later on to problems. Any change will be difficult, as another developer had to read a long documentation.
An alternative would be to do all with one interface mapping (without validation):
1. ABAP / Java mapping deleting the "header" (put it to memory)
2. Messges Mapping 1:1 each field (will fail in case of wrong format and act as validator)
3. ABAP / Java mapping restoring the header
4. Alert will be raised in case of an error (to get the result of the validation)
Armin Kern wrote:
> I also thought about splitting the message, deleting those 2 rows in one of the messages, sending this one message to PI again, validate it and if it is correct, send the second message (without mapping) to the final destination. No idea if that is possible at all..
As well possible. You would need a virtual receiver for the first message, which is sending back a response. For example a servlett, a proxy or a RFC module. In that design you put some logic to the sender, what is actually not bad. But if you do so, why you dont validate there as well (for example with Java)? It would make your design much easier..
Regards,
Udo

XML parsing failed because ""

Hi ,
     I am facing issue while building composite in jdeveloper.It is showing below error.Please Suggest how to proceed further.
Error: XML parsing failed because ""
Buildfile: C:\Oracle\Middleware\jdeveloper\bin\ant-sca-compile.xml
scac:
     [scac] Validating composite "C:\MR96\BPEL Services\MOOA_businesservices\AddComponent\composite.xml"
     [scac] Setting BPELC option 'classpath' to C:\Oracle\Middleware\modules\com.oracle.toplink_1.0.0.0_11-1-1-5-0.jar;C:\Oracle\Middleware\modules\org.eclipse.persistence_1.1.0.0_2-1.jar;C:\Oracle\Middleware\modules\com.bea.core.antlr.runtime_2.7.7.jar;C:\Oracle\Middleware\modules\javax.persistence_1.0.0.0_2-0-0.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xmlparserv2.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xml.jar;C:\Oracle\Middleware\jdeveloper\jdev\extensions\oracle.sca.modeler.jar;C:\Oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime.jar;C:\Oracle\Middleware\jdeveloper\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;C:\Oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel.jar;C:\Oracle\Middleware\jdeveloper\soa\modules\oracle.soa.mediator_11.1.1\mediator_client.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.mds_11.1.1\mdsrt.jar;;C:\MR96\BPEL Services\MOOA_businesservices\AddComponent\SCA-INF\classes
     [scac] java.lang.NullPointerException
     [scac] at com.collaxa.cube.lang.compiler.map.bpel.BPELProcess.lookupInitiationInfo(BPELProcess.java:1010)
     [scac] at com.collaxa.cube.lang.compiler.map.bpel.BPELProcess.addOnMessage(BPELProcess.java:903)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parseOnMessage(BpelParser.java:1597)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.startElement(BpelParser.java:587)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parseElement(BpelParser.java:492)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parseElement(BpelParser.java:499)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parseElement(BpelParser.java:499)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parseElement(BpelParser.java:499)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parseElement(BpelParser.java:499)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parseElement(BpelParser.java:499)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parseElement(BpelParser.java:499)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parseElement(BpelParser.java:499)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parseElement(BpelParser.java:499)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parseElement(BpelParser.java:499)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parseElement(BpelParser.java:499)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parseElement(BpelParser.java:499)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parseElement(BpelParser.java:499)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parseElement(BpelParser.java:499)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parseElement(BpelParser.java:499)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parseElement(BpelParser.java:499)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parseElement(BpelParser.java:499)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parseElement(BpelParser.java:499)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parse(BpelParser.java:455)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BpelParser.parse(BpelParser.java:402)
     [scac] at com.collaxa.cube.lang.compiler.bpel.BPELValidator.validate(BPELValidator.java:65)
     [scac] at com.collaxa.cube.lang.compiler.BPEL1Processor.validate(BPEL1Processor.java:329)
     [scac] at com.collaxa.cube.lang.compiler.BPEL1Processor.process(BPEL1Processor.java:153)
     [scac] at com.collaxa.cube.lang.compiler.CubeParserHelper.compile(CubeParserHelper.java:47)
     [scac] at oracle.fabric.bpel.bpelc.BPELComponentValidator.validate(BPELComponentValidator.java:40)
     [scac] at oracle.soa.scac.ValidateComposite.validateComponentTypeServicesReferences(ValidateComposite.java:1051)
     [scac] at oracle.soa.scac.ValidateComposite.doValidation0(ValidateComposite.java:502)
     [scac] at oracle.soa.scac.ValidateComposite.doValidation(ValidateComposite.java:481)
     [scac] at oracle.soa.scac.ValidateComposite.run0(ValidateComposite.java:206)
     [scac] at oracle.soa.scac.ValidateComposite.run(ValidateComposite.java:187)
     [scac] at oracle.soa.scac.ValidateComposite.main(ValidateComposite.java:179)
     [scac] AddComponentProcess.bpel: error: XML parsing failed because ""
BUILD FAILED
C:\Oracle\Middleware\jdeveloper\bin\ant-sca-compile.xml:278: Java returned: 1 Check log file : C:\MR96\BPEL Services\MOOA_businesservices\AddComponent\SCA-INF\classes\scac.log for errors
Total time: 1 minute 27 seconds
Thanks

Hi,
Please give a try to this:(Take back up before doing this)
1. Download PATCH 11066656 .
2. Go to your JDEV_HOME/jdeveloper/soa/modules/oracle.soa.bpel_11.1.1/
and make a backup copy of orabpel.jar.
3. Copy the file orabpel.jar from patch 11066656 to JDEV_HOME/jdeveloper/soa/modules/oracle.soa.bpel_11.1.1/.
4. Restart JDeveloper.
5. Now the project should compile without the SCAC error.
This was fixed in 11.7 but since you are getting SCAC so asked the above action plan.
If it did not resolves see below steps:
=============================================================
File will be there but a class is missing which might cause this.
If you have same soa version 11.1.1.7.0 can you check that fabricruntime.jar from soa home and jdev home size is same?
In soa home it will be under Oracle_SOA/soa/modules directory.
If size is not same replace jdev fabricruntime.jar from soa home.
Also can you confirm on:
Please let me know whether you are able to deploy from EM or getting same error during deployment also? or from ant script.

BPEL validation failed in "SOA Order Booking" Applicaton sample

Apache ant log error message as follows:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Buildfile: C:\Documents and Settings\wbrkadm\Desktop\OEMS\ESBSamples\QuickStart\soademo_101310_prod\SOADEMO\SOAOrderBooking\build.xml
pre-deploy:
validateTask:
[echo]
| Validating workflow
[validateTask] url is file:/C:/jdevstudiobase10132/integration/bpm/support/files/WorkflowTaskDefinition.xsd
[validateTask] Validation of workflow task definitions is completed without errors
deployDecisionServices:
[echo]
| Deploying decision services for SOAOrderBooking on localhost, port 8888
[deployDecisionServices] 07/09/03 10:29:33 Notification ==>Application Deployer for rules_default_SOAOrderBooking_1_0_DecisionService STARTS.
[deployDecisionServices]
[deployDecisionServices] 07/09/03 10:29:33 Notification ==>Undeploy previous deployment
[deployDecisionServices]
[deployDecisionServices] 07/09/03 10:29:33 Notification ==>Initialize C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\rules_default_SOAOrderBooking_1_0_DecisionService.ear begins...
[deployDecisionServices]
[deployDecisionServices] 07/09/03 10:29:34 Notification ==>Initialize C:\product\10.1.3.1\OracleAS_1\j2ee\home\applications\rules_default_SOAOrderBooking_1_0_DecisionService.ear ends...
[deployDecisionServices]
[deployDecisionServices] 07/09/03 10:29:34 Notification ==>Starting application : rules_default_SOAOrderBooking_1_0_DecisionService
[deployDecisionServices]
[deployDecisionServices] 07/09/03 10:29:34 Notification ==>Initializing ClassLoader(s)
[deployDecisionServices]
[deployDecisionServices] 07/09/03 10:29:34 Notification ==>Initializing EJB container
[deployDecisionServices]
[deployDecisionServices] 07/09/03 10:29:34 Notification ==>Loading connector(s)
[deployDecisionServices]
[deployDecisionServices] 07/09/03 10:29:34 Notification ==>Starting up resource adapters
[deployDecisionServices]
[deployDecisionServices] 07/09/03 10:29:34 Notification ==>Initializing EJB sessions
[deployDecisionServices]
[deployDecisionServices] 07/09/03 10:29:34 Notification ==>Committing ClassLoader(s)
[deployDecisionServices]
[deployDecisionServices] 07/09/03 10:29:34 Notification ==>Initialize DecisionService-web begins...
[deployDecisionServices]
[deployDecisionServices] 07/09/03 10:29:34 Notification ==>Initialize DecisionService-web ends...
[deployDecisionServices]
[deployDecisionServices] 07/09/03 10:29:34 Notification ==>Started application : rules_default_SOAOrderBooking_1_0_DecisionService
[deployDecisionServices]
[deployDecisionServices] 07/09/03 10:29:34 Notification ==>Application Deployer for rules_default_SOAOrderBooking_1_0_DecisionService COMPLETES. Operation time: 1250 msecs
[deployDecisionServices]
[deployDecisionServices] Successfully deployed decision services on server "localhost"
compile:
[echo]
| Compiling bpel process SOAOrderBooking, revision 1.0
[bpelc] ORABPEL-01021
[bpelc]
[bpelc] BPEL validation failed.
[bpelc] BPEL source validation failed, the errors are:
[bpelc]
[bpelc] [Error ORABPEL-10903]: failed to read wsdl
[bpelc] [Description]: in "bpel.xml", Failed to read wsdl.
[bpelc] Error happened when reading wsdl at "http://localhost:8888/esb/wsil/Fulfillment/OrderFulfillment?wsdl", because "Error reading import of http://localhost:8888/esb/wsil/Fulfillment/OrderFulfillment?wsdl: Failed to read WSDL from http://01HW127690.India.TCS.com:8888/esb/slide/ESB_Projects/SOADEMO_FulfillmentESB/Fulfillment_OrderFulfillment.wsdl: HTTP connection error code is 407".
[bpelc] Make sure wsdl exists at that URL and is valid.
[bpelc] .
[bpelc] [Potential fix]: If your site has a proxy server, then you may need to configure your BPEL Server, designer and browser with your proxy server configuration settings (see tech note on http://otn.oracle.com/bpel for instructions).
[bpelc] .
[bpelc]
[bpelc]      at com.collaxa.cube.lang.compiler.CubeProcessor.validateClientSide(CubeProcessor.java:1133)
[bpelc]      at com.collaxa.cube.lang.compiler.CubeProcessor.transformClientSide(CubeProcessor.java:449)
[bpelc]      at com.collaxa.cube.lang.compiler.CubeParserHelper.compileClientSide(CubeParserHelper.java:83)
[bpelc]      at com.collaxa.cube.ant.taskdefs.Bpelc.execute(Bpelc.java:626)
[bpelc]      at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[bpelc]      at org.apache.tools.ant.Task.perform(Task.java:364)
[bpelc]      at org.apache.tools.ant.Target.execute(Target.java:341)
[bpelc]      at org.apache.tools.ant.Target.performTasks(Target.java:369)
[bpelc]      at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[bpelc]      at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
[bpelc]      at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
[bpelc]      at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[bpelc]      at oracle.jdevimpl.ant.runner.AntLauncher.launch(AntLauncher.java:321)
[bpelc]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[bpelc]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[bpelc]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[bpelc]      at java.lang.reflect.Method.invoke(Method.java:585)
[bpelc]      at oracle.jdevimpl.ant.runner.InProcessAntStarter.runAnt(InProcessAntStarter.java:295)
[bpelc]      at oracle.jdevimpl.ant.runner.InProcessAntStarter.mav$runAnt(InProcessAntStarter.java:43)
[bpelc]      at oracle.jdevimpl.ant.runner.InProcessAntStarter$1.run(InProcessAntStarter.java:71)
[bpelc] BPEL validation failed.
[bpelc] BPEL source validation failed, the errors are:
[bpelc]
[bpelc] [Error ORABPEL-10903]: failed to read wsdl
[bpelc] [Description]: in "bpel.xml", Failed to read wsdl.
[bpelc] Error happened when reading wsdl at "http://localhost:8888/esb/wsil/Fulfillment/OrderFulfillment?wsdl", because "Error reading import of http://localhost:8888/esb/wsil/Fulfillment/OrderFulfillment?wsdl: Failed to read WSDL from http://01HW127690.India.TCS.com:8888/esb/slide/ESB_Projects/SOADEMO_FulfillmentESB/Fulfillment_OrderFulfillment.wsdl: HTTP connection error code is 407".
[bpelc] Make sure wsdl exists at that URL and is valid.
[bpelc] .
[bpelc] [Potential fix]: If your site has a proxy server, then you may need to configure your BPEL Server, designer and browser with your proxy server configuration settings (see tech note on http://otn.oracle.com/bpel for instructions).
[bpelc] .
[bpelc]
BUILD FAILED
C:\Documents and Settings\wbrkadm\Desktop\OEMS\ESBSamples\QuickStart\soademo_101310_prod\SOADEMO\SOAOrderBooking\build.xml:72: Validation error
Total time: 11 seconds
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are using compatible JDevelopers.
Can you please confirm that it is the deployment of the BPEL process that is failing and not the ESB.
You should be able to select 'Not Sepcified' for the My Role in the partner link page. If you can't then that partner link do not have a role for my role.
If you don't get anything to select in partner link type then JDeveloper cannot connect to the WSDL location.
If you are able to connect via a browser then there must be an issue with the proxy configuration in JDeveloper. These setting should look exactly the same as your browser.
cheers
James

Handling empty values during xml validation

Hello experts,
I have a file to file scenario in PI 7.1. I am using xml validation to validate the incoming source file. There are various types of fields in the incoming file including int, decimal and string. They can have a certain enumeration of values but can also have a blank value.
For example field 'Num' of type int can have values 1,2,3 or a blank value.
But I am not able to define a blank value for the field in the enumeration during definition. Therefore a blank value in the input file fails during the validation stage.
Is there any workaround for this?
Thanks!
RR

This is a basic problem. When you define a field as integer you cannot declare blank space which represents String type.
So for your case make the value 'zero' instead of blank, if you want do declare the field as integer and as below...
<xs:element name="Num">
<xs:simpleType>
    <xs:restriction base="xs:integer">
      <xs:pattern value="[0-3]"/>
    </xs:restriction>
</xs:simpleType>
</xs:element>
Also refer this page for further reference.
http://www.w3schools.com/schema/schema_facets.asp

Eclipse XQuery expression validation failed: The current configuration is out of sync with the XQuery resource in the repository.

I created a wsdl based on a dbadapter in jdeveloper, imported into eclipse and created the biz and the proxy and uploaded to oracle service bus, it works fine,
but happens now that i need to have a xsd and wsdl with business names and not table names, invented to create a xsd and wsdl file in jdeveloper
and then went to eclipse and tried t xquery tranformation, but when i add the replace in the message flow in the filed in Variable : body and Expression i look for the xquery and in the binding trying to put
$body/input parameter, get the following error [RouteNode1, Replace action] XQuery expression validation failed: The current configuration is out of sync with the XQuery resource in the repository.
what im doing wrong or its configuration
thanks in advance sonia

thanks
ok have created a table with only in column varchar2(1)
then the type object and the procedure to insert it works the proxy in the osb if i test it inserts
now in jdeveloper i created an xml file with
<?xml version="1.0" encoding="windows-1252" ?>
<vessel>
<barco>a</barco>
</vessel>
then i created a xsd based on this xml, and a wsdl based on the xsd
in eclipse created a xquery transformation and selected source as the xsd created in adf and target the xsd input parameter, dont know why in the purple ball of the input parameter it puts a ?, an a f.
then in the proxy xpath not writing anything in variable body and in the expression select the xquery and in binding select the parameter

Validation Failed. Creation Web Service Proxy

Hi, all
I've got a problem with JDeveloper 10.1.3 when I try to create a web serviceproxy using the wizard.
My service class is next,
package swa;
import java.awt.Graphics;
import java.awt.Image;
import java.awt.Toolkit;
import java.awt.color.ColorSpace;
import java.awt.geom.AffineTransform;
import java.awt.image.AffineTransformOp;
import java.awt.image.BufferedImage;
import java.awt.image.ColorConvertOp;
import java.awt.image.RescaleOp;
import javax.xml.soap.AttachmentPart;
import javax.xml.soap.MessageFactory;
import javax.xml.soap.SOAPException;
import javax.xml.soap.SOAPMessage;
public class ImgToolbox {
public final static int FLIP_VERTICAL = 0;
public final static int FLIP_HORIZONTAL = 1;
public final static int FLIP_VERTICAL_HORIZONTAL = 2;
public AttachmentPart toGray(AttachmentPart imagen){
AttachmentPart apRetorno = null;
try{
Image image = (Image)imagen.getContent();
BufferedImage originalImage = new BufferedImage(image.getWidth(null), image.getHeight(null), BufferedImage.TYPE_INT_RGB);
ColorSpace cs = ColorSpace.getInstance(ColorSpace.CS_GRAY);
ColorConvertOp op = new ColorConvertOp(cs, null);
BufferedImage grayImage = op.filter(originalImage, null);
// Creación del AttachmentPart con la nueva imagen
MessageFactory mf = MessageFactory.newInstance();
SOAPMessage message = mf.createMessage();
apRetorno = message.createAttachmentPart();
apRetorno.setContent(Toolkit.getDefaultToolkit().createImage(grayImage.getSource()),"image/jpeg");
} catch(SOAPException e){
System.out.println("Error, en el mensaje SOAP.");
return apRetorno;
public AttachmentPart flip(AttachmentPart ap, int tipo){
AttachmentPart apRetorno = null;
try{
Image image = (Image)ap.getContent();
BufferedImage originalImage = new BufferedImage(image.getWidth(null), image.getHeight(null), BufferedImage.TYPE_INT_RGB);
AffineTransform tx = null;
AffineTransformOp op = null;
switch(tipo){
case FLIP_VERTICAL : {
tx = AffineTransform.getScaleInstance(1, -1);
tx.translate(0, -image.getHeight(null));
break;
case FLIP_HORIZONTAL : {
tx = AffineTransform.getScaleInstance(-1, 1);
tx.translate(-image.getWidth(null), 0);
break;
case FLIP_VERTICAL_HORIZONTAL : {
tx = AffineTransform.getScaleInstance(-1, -1);
tx.translate(-image.getWidth(null), -image.getHeight(null));
break;
op = new AffineTransformOp(tx, AffineTransformOp.TYPE_NEAREST_NEIGHBOR);
BufferedImage flipImage = op.filter(originalImage, null);
// Creación del AttachmentPart con la nueva imagen
MessageFactory mf = MessageFactory.newInstance();
SOAPMessage message = mf.createMessage();
apRetorno = message.createAttachmentPart();
apRetorno.setContent(Toolkit.getDefaultToolkit().createImage(flipImage.getSource()),"image/jpeg");
} catch (SOAPException e) {
System.out.println("Error, en el mensaje SOAP.");
return apRetorno;
public AttachmentPart resize(AttachmentPart img,float escala){
AttachmentPart apRetorno = null;
try{
Image image = (Image)img.getContent();
BufferedImage originalImage = new BufferedImage(image.getWidth(null), image.getHeight(null), BufferedImage.TYPE_INT_RGB);
// Se rellena la BufferedImage con la imagen original
Graphics g = originalImage.createGraphics();
g.drawImage(image, 0, 0, null);
g.dispose();
// Modificación de la imagen original
RescaleOp op = new RescaleOp(escala, 0, null);
BufferedImage tempImage = op.filter(originalImage, null);
// Creación del AttachmentPart con la nueva imagen
MessageFactory mf = MessageFactory.newInstance();
SOAPMessage message = mf.createMessage();
apRetorno = message.createAttachmentPart();
apRetorno.setContent(Toolkit.getDefaultToolkit().createImage(tempImage.getSource()),"image/jpeg");
} catch (SOAPException e) {
System.out.println("Error, en el mensaje SOAP.");
return apRetorno;
the wizard creates a JAX-RPC web service without problems from this class. However, if I click on "Regenerate Web Service from WSDL..." the method fails and throws a exception. The trace is next :
java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
     at java.util.ArrayList.RangeCheck(ArrayList.java:547)
     at java.util.ArrayList.get(ArrayList.java:322)
     at oracle.jdeveloper.webservices.model.SOAPBinding.<init>(SOAPBinding.java:243)
     at oracle.jdeveloper.webservices.model.Binding.create(Binding.java:668)
     at oracle.jdeveloper.webservices.model.WebService.createServiceFromWSDL(WebService.java:2275)
     at oracle.jdeveloper.webservices.model.WebService.createServiceFromWSDL(WebService.java:2117)
     at oracle.jdeveloper.webservices.model.java.JavaWebService.saveEditTopDown(JavaWebService.java:1704)
     at oracle.jdevimpl.webservices.WebServicesAddin$2.run(WebServicesAddin.java:2261)
     at oracle.jdeveloper.webservices.model.GeneratorUI$GeneratorAction.run(GeneratorUI.java:446)
     at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
     at java.lang.Thread.run(Thread.java:595)
WSDL FILE GENERATED BY THE WIZARD
<definitions
name="ImgToolboxWS"
targetNamespace="http://swa/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://swa/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns0="http://swa/types/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns1="http://ws-i.org/profiles/basic/1.1/xsd"
>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://ws-i.org/profiles/basic/1.1/xsd"
elementFormDefault="qualified" xmlns:tns="http://ws-i.org/profiles/basic/1.1/xsd">
<import namespace="http://swa/types/"/>
<simpleType name="swaRef">
<restriction base="xsd:anyURI"/>
</simpleType>
</schema>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://swa/types/"
elementFormDefault="qualified" xmlns:tns="http://swa/types/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap12-enc="http://www.w3.org/2003/05/soap-encoding"
xmlns:ns1="http://ws-i.org/profiles/basic/1.1/xsd">
<import namespace="http://ws-i.org/profiles/basic/1.1/xsd"/>
<complexType name="flip">
<sequence>
<element name="ap" type="ns1:swaRef" nillable="true"/>
<element name="tipo" type="int"/>
</sequence>
</complexType>
<complexType name="flipResponse">
<sequence>
<element name="result" type="ns1:swaRef" nillable="true"/>
</sequence>
</complexType>
<complexType name="resize">
<sequence>
<element name="img" type="ns1:swaRef" nillable="true"/>
</sequence>
</complexType>
<complexType name="resizeResponse">
<sequence>
<element name="result" type="ns1:swaRef" nillable="true"/>
</sequence>
</complexType>
<complexType name="toGray">
<sequence>
<element name="imagen" type="ns1:swaRef" nillable="true"/>
</sequence>
</complexType>
<complexType name="toGrayResponse">
<sequence>
<element name="result" type="ns1:swaRef" nillable="true"/>
</sequence>
</complexType>
<element name="flipElement" type="tns:flip"/>
<element name="flipResponseElement" type="tns:flipResponse"/>
<element name="resizeElement" type="tns:resize"/>
<element name="resizeResponseElement" type="tns:resizeResponse"/>
<element name="toGrayElement" type="tns:toGray"/>
<element name="toGrayResponseElement" type="tns:toGrayResponse"/>
</schema>
</types>
<message name="ImgToolboxWS_flip">
<part name="parameters" element="tns0:flipElement"/>
</message>
<message name="ImgToolboxWS_flipResponse">
<part name="parameters" element="tns0:flipResponseElement"/>
</message>
<message name="ImgToolboxWS_resize">
<part name="parameters" element="tns0:resizeElement"/>
</message>
<message name="ImgToolboxWS_resizeResponse">
<part name="parameters" element="tns0:resizeResponseElement"/>
</message>
<message name="ImgToolboxWS_toGray">
<part name="parameters" element="tns0:toGrayElement"/>
</message>
<message name="ImgToolboxWS_toGrayResponse">
<part name="parameters" element="tns0:toGrayResponseElement"/>
</message>
<portType name="ImgToolboxWS">
<operation name="flip">
<input message="tns:ImgToolboxWS_flip"/>
<output message="tns:ImgToolboxWS_flipResponse"/>
</operation>
<operation name="resize">
<input message="tns:ImgToolboxWS_resize"/>
<output message="tns:ImgToolboxWS_resizeResponse"/>
</operation>
<operation name="toGray">
<input message="tns:ImgToolboxWS_toGray"/>
<output message="tns:ImgToolboxWS_toGrayResponse"/>
</operation>
</portType>
<binding name="ImgToolboxWSSoap12Http" type="tns:ImgToolboxWS">
<soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="flip">
<soap12:operation soapAction="http://swa//flip" soapActionRequired="false"/>
<input>
<mime:multipartRelated>
<mime:part>
<soap12:body use="literal" parts="parameters"/>
</mime:part>
</mime:multipartRelated>
</input>
<output>
<mime:multipartRelated>
<mime:part>
<soap12:body use="literal" parts="parameters"/>
</mime:part>
</mime:multipartRelated>
</output>
</operation>
<operation name="resize">
<soap12:operation soapAction="http://swa//resize" soapActionRequired="false"/>
<input>
<mime:multipartRelated>
<mime:part>
<soap12:body use="literal" parts="parameters"/>
</mime:part>
</mime:multipartRelated>
</input>
<output>
<mime:multipartRelated>
<mime:part>
<soap12:body use="literal" parts="parameters"/>
</mime:part>
</mime:multipartRelated>
</output>
</operation>
<operation name="toGray">
<soap12:operation soapAction="http://swa//toGray" soapActionRequired="false"/>
<input>
<mime:multipartRelated>
<mime:part>
<soap12:body use="literal" parts="parameters"/>
</mime:part>
</mime:multipartRelated>
</input>
<output>
<mime:multipartRelated>
<mime:part>
<soap12:body use="literal" parts="parameters"/>
</mime:part>
</mime:multipartRelated>
</output>
</operation>
</binding>
<service name="ImgToolboxWS">
<port name="ImgToolboxWSSoap12HttpPort" binding="tns:ImgToolboxWSSoap12Http">
<soap12:address location="http://192.168.0.6:8888/Capitulo3-SwA-context-root/ImgToolboxWSSoap12HttpPort"/>
</port>
</service>
</definitions>
If I only expose the toGray method as a Web Service all works fine. Any combinatio with other methods won't work. It's very strange.
When I try to create a proxy using the wizard JDeveloper shows me next error message :
Validation Failed
...wsdl file does not contain sufficient information to create a proxy. At least one port type and a binding of the are required.
Any reply will be greatly appreciated.
Best regards.

I am getting this error by generating a web service from pl/sql procedure. Just one package, just one procedure. Error stack:
java.lang.NullPointerException
     at oracle.jdevimpl.webservices.generator.WrapperClassGenerator.generate(WrapperClassGenerator.java:262)
     at oracle.jdevimpl.webservices.generator.SPWebServiceGenerator$1.run(SPWebServiceGenerator.java:285)
     at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
     at java.lang.Thread.run(Thread.java:595)
The pl/sql package header looks like this:
CREATE OR REPLACE package ADMIN.etis_autent as
procedure autent(
     ps_kasutajatunnus in varchar2,
     ps_parool in varchar2,
     ps_isikukood out varchar2,
     ps_eesnimi out varchar2,
     ps_perekonnanimi out varchar2
end etis_autent;
/

Regarding error in xml validation 7.1

Hi
I am doing file to idoc scenario. In the sender agreement i selected validation by Adapter and uploaded the particular xsd.after executing the scenario in runtime workbench it is showing sucessfully processed but in the MDT audit log I am getting following error.without validation the file is posting in target system.but when I check the validation by adapter it is giving following error.
Received XI System Error. ErrorCode: CX_XMS_SYSERR_VALIDATION ErrorText: not used at the moment. ErrorStack: System error occurred during XML validation
Transmitting the message to endpoint http://orcdapp1.edfapps.edfenergy.net:51100/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: CX_XMS_SYSERR_VALIDATION:not used at the moment..
Please give me your inputs.
Regards
venkat.

Hi Venky,
This error due to incorrect path So please check whether you have used the correct path or not?
Create appropriate directories structure where we have to save your structure (xsd).
\usr\sap\<system id>\SYS\global\xi\runtime_server\A\B\C\D\E\F
A - validation
B - schema
C - GUID of the SWCV where service interface reside.
D - Repository Namespace where Service Interface is created.
E - Service Interface Name
F - Repository Namespace where Message Type or External Definition is assigned.
Note: if your ESR namespace contains special character then do replace it with u201C~u201D in folder name.
If namespace is http://abc.com/XI/FileToFile then folder name should be replace with httpabc.comXI~FileToFile
Export schema from the ESR and save it in folder u201CFu201D with name <<RootElementOfMessageType>>.xsd. So in this case it is MT_File_Sender.xsd
Regards,
Sameer
Edited by: sameer Khanna on May 27, 2009 10:14 AM

XML validation fails

Similar Messages

Maybe you are looking for