Schema validation issue

Hi
We do schema validation with raise error option. But to the consumer we do not want send the SOAP Fault but a response message which has error tags.
How to do this.
Thanks,
Vinoth

Hi Vinoth,
In stage error handler, replace the content of body($body) with desired XML content(probably using a XQuery) and use Reply with success action
Regards,
Anuj

Similar Messages

XML Schema validation issue

Sorry for this post, because it really isn't a weblogic specific thing, but I can't
find my answer
anywhere else.
I am attempting to validate my xml file using an XML Schema file. The XML
Schema code looks like this:
<xsd:element name="operatingSystem">
<xsd:simpleType>
<xsd:list>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value=".*(w|W)(I|i)(n|N).*"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:list>
</xsd:simpleType>
</xsd:element>
The XML snippet looks like this:
<operatingSystem>Windows 2000</operatingSystem>
The error that I'm getting when using the SaxParser is the following:
org.xml.sax.SAXException: cvc-pattern-valid: Value '2000' is not facet-v
alid with respect to pattern '.*(w|W)(I|i)(n|N).*' for type 'null'.
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at SAXLocalNameCount.main(SAXLocalNameCount.java:272)
Somehow, the validation breaks my one string in the operatingSystem tag into
two separate strings to be validated. Can anybody give me some advice on
what to do?
Thanks in advance,
Joel

for some reason it does not like a space between "Windows" and "2000" any
character other than space is fine...
"Joel" <[email protected]> wrote in message
news:3fa9468b$[email protected]..
>
Sorry for this post, because it really isn't a weblogic specific thing,but I can't
find my answer
anywhere else.
I am attempting to validate my xml file using an XML Schema file. The XML
Schema code looks like this:
<xsd:element name="operatingSystem">
<xsd:simpleType>
<xsd:list>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value=".*(w|W)(I|i)(n|N).*"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:list>
</xsd:simpleType>
</xsd:element>
The XML snippet looks like this:
<operatingSystem>Windows 2000</operatingSystem>
The error that I'm getting when using the SaxParser is the following:
org.xml.sax.SAXException: cvc-pattern-valid: Value '2000' is not facet-v
alid with respect to pattern '.*(w|W)(I|i)(n|N).*' for type 'null'.
at org.apache.xerces.parsers.AbstractSAXParser.parse(UnknownSource)
at SAXLocalNameCount.main(SAXLocalNameCount.java:272)
Somehow, the validation breaks my one string in the operatingSystem taginto
two separate strings to be validated. Can anybody give me some advice on
what to do?
Thanks in advance,
Joel

Error : Catalog object schema validation failed in OBIEE 11.1.1.5

Hi all ,
Facing the below error while accessing few reports present in a folder (Voice Tab) . But , able to access other reports present in the same folder .
Catalog object schema validation failed: /users/weblogic/sayak/TPLAN reports/Voice Tab/Net revenue per minute (ILD\/NLD)
Error Details
Error Codes: AGFIXBO2:EIRWWH9E
Location: saw.httpserver.processrequest, saw.rpc.server.responder, saw.rpc.server, saw.rpc.server.handleConnection, saw.rpc.server.dispatch, saw.threadpool, saw.threadpool, saw.threads
Also while try to edit the analysis (Net revenue per minute (ILD\/NLD) from catalog , i am getting the above error .The Reports were fine till yesterday , What could be the issue ?
Thanks

Hi Devarasu ,
Yeah .. I'm aware of this bug of 11.1.1.5 , but I'm puzzeled by the sudden impact of it . i.e , It didn't gave me the error while creating/editing the file yesterday and looked fine on dashboard as well .
However , If there's no alternative other than applying patch , then please let me know the patch ID .
And applying this patch means , just overwriting some configure files in the OBIEE home folder sructure ? or somthing else ?
Thanks

BPMN 11g - Process initiation schema validation error

Gurus,
we are facing one absurd issue.
When we create a BPMN process and expose it as a service in composite then the WSDL it creates automatically does not have 'formElementDefault' attribute under <xsd:schema > element..
hence if we test from EM after enabling schema validation [composite-->reference->properties] then it show error....else it works fine randomly...sometimes work sometimes does not.... any clue.
we have tried adding elementFormDefault="qualified" this but no luck. please suggest.
<?xml version="1.0" encoding="UTF-8"?>






<wsdl:definitions targetNamespace="http://xmlns.oracle.com/bpmn/bpmnProcess/Process" xmlns:tns="http://xmlns.oracle.com/bpmn/bpmnProcess/Process" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" >
<wsdl:types>
<xsd:schema targetNamespace="http://xmlns.oracle.com/bpmn/bpmnProcess/Process" added by me+_ elementFormDefault="qualified">
<xsd:element name="operationCallbackResponse">
<xsd:complexType>
<xsd:sequence/>
</xsd:complexType>
</xsd:element>
<xsd:element name="operation">
<xsd:complexType>
<xsd:sequence/>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
Thanks,
Biltu

Please make sure that main xsd uses import or include tag to reference both schema1.xsd and schema2.xsd. If the main xsd does not do it, Pi cannot verify it. Since you package all the files as zip file, also make sure the path for the secondary files are in proper location.
In short, the import element allows you to use schema components from any schema; the include element allows you to add all the components of an included schema to the containing schema. If the target namespace is same for both then include tag should be good enough. If you don't find one, you might have to use include tag element in the main or parent xsd file.
Edited by: Baskar Gopal on Jan 31, 2012 5:18 PM

Adapter Engine XML Schema Validation Error Surpression

We recently developed a number of web services that are called by 3rd parties outside our network. The web service request once made is picked up by a Web Dispatcher which then forwards the request to the de-central adapter. Both of these components reside within within a DMZ.
We have, as an additional security measure made use of the new Adapter Engine XML Schema validation available with PI 7.1, to ensure that the payload of incomming messages is checked to ensure that it is a known structure.
Now here is my problem, we recently had these services penetration tested by a 3rd party to ensure that they were secure and whilst the report was very good showing no major weaknesses they did pickup on a couple of items including that the fact that if the XSD to be used during payload message validation cannot be found an 'ADAPTER.JAVA_EXCEPTION' is returned to the web service consumer that highlights the path details of where the XSD should be (but could not be found).
This was viewed as useful to an attacker for a number of reasons:
1. Feedback in SQL injection attempts via verbatim DB error messages greatly improves attacker efficiency
2. Path information is useful to the attacker for OS fingerprinting, directory traversal attempts
3. Other miscellaneous stack trace information is useful to an attacker to understand how the application works
Is there anyway this can be surpressed so that the adapter does not show this information in the returned error message - see example message below ?
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: Schema MaintenanceOrderByIDQuery_sync.xsd not found in E:\usr\sap\DPI\DVEBMGS40\j2ee\cluster\server0\validation\schema\f7cd3b50a87411e08830ed9d0af006a5\urnstw.contractor.wfm.workorderretrieval\MaintenanceOrderByIDQueryRequest_Out\httpsap.comxiSAPGlobal20~Global\MaintenanceOrderByIDQuery_sync.xsd (validation\schema)
     at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1041)
     at sun.reflect.GeneratedMethodAccessor497.invoke(Unknown Source)
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: Schema Schema1.xsd not found in E:\usr\sap\DPI\DVEBMGS40\j2ee\cluster\server0\validation\schema\f7cd3b50a87411e08830ed9d0af006a5\urnstw.contractor.wfm.workorderretrieval\MaintenanceOrderByIDQueryRequest_Out\httpsap.comxiEA-APPLSEGlobal\Schema1.xsd (validation\schema)
     at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1041)

Hi,
We are having the same problem, so you are not alone.
I had an extensive call with Azure premium support and we where able to determine that:
- Nothing is missing or in the wrong place in my exported .xml file.
- Any changes to the VNET's using the web gui interface of https://manage.windowsazure.com is not possible when you have dns servers and use an gateway
- You can download the .xml configuration file of the network and make manual changes to it, then import it again , to add/remove dns servers and or subnet's.
I am currently waiting for an solution, i have let them lower the urgency from A to B (because i can make changes trough xml) and responded to the next support contact (saying he will continue with the issue) that the problems seems to be with azure and
he should speak with the previous person helping me. I have not heard from Azure support since.
SR Number:115021812414226
Open on:02/18/2015 09:28
> There are networks with and without gateways created and the issue is happening on all the networks.
> We are unable to add or remove the DNS servers. (by web gui)
> Also not able to add or remove any subnets. (by web gui)
> Every time the error message is same but the DNS server name is different. (from another subnet then the one we are changing)
> Created CRI- 3405931, but they said it will need WATS team.
> Confirmed with WATS engineer as well and moving case to WATS.
> Cx agreed to lower the severity of the case as they are able to make changes through the network configuration file.
> But they still want to get this resolved soon.
> Agreed and dropped off, reducing severity to B 24/7.
I hope microsoft is going to resolve this soon, as i do not want to edit my xml for little things like adding a subnet all the time. I have requested an status update in the issue.
Should anyone have more information on this, please share it here.

XML Schema validation error in network configuration. Missing DnsRef

When ever we try to make changes to a Virtual network we receive
XML Schema validation
error in network configuration. Missing DnsRef
We can't make any changes to the Virtual network.
The DNS ref exists as well.
Considering exporting network config and re-importing however we have a lot of networks configured and want to be sure this is the correct way to proceed.
Any feedback much appreciated.
Thanks

Hi,
We are having the same problem, so you are not alone.
I had an extensive call with Azure premium support and we where able to determine that:
- Nothing is missing or in the wrong place in my exported .xml file.
- Any changes to the VNET's using the web gui interface of https://manage.windowsazure.com is not possible when you have dns servers and use an gateway
- You can download the .xml configuration file of the network and make manual changes to it, then import it again , to add/remove dns servers and or subnet's.
I am currently waiting for an solution, i have let them lower the urgency from A to B (because i can make changes trough xml) and responded to the next support contact (saying he will continue with the issue) that the problems seems to be with azure and
he should speak with the previous person helping me. I have not heard from Azure support since.
SR Number:115021812414226
Open on:02/18/2015 09:28
> There are networks with and without gateways created and the issue is happening on all the networks.
> We are unable to add or remove the DNS servers. (by web gui)
> Also not able to add or remove any subnets. (by web gui)
> Every time the error message is same but the DNS server name is different. (from another subnet then the one we are changing)
> Created CRI- 3405931, but they said it will need WATS team.
> Confirmed with WATS engineer as well and moving case to WATS.
> Cx agreed to lower the severity of the case as they are able to make changes through the network configuration file.
> But they still want to get this resolved soon.
> Agreed and dropped off, reducing severity to B 24/7.
I hope microsoft is going to resolve this soon, as i do not want to edit my xml for little things like adding a subnet all the time. I have requested an status update in the issue.
Should anyone have more information on this, please share it here.

Problem in SAX XSD schema validator

hi
I've tried this code to validate XML using xsd file:
public static void validate(String xmlFilePath, URL schemaFileUrl)
        try
            SAXParserFactory factory = SAXParserFactory.newInstance();
            factory.setValidating(false);// stop standard validation to allow
                                            // custom schema
            factory.setNamespaceAware(true);
            SchemaFactory schemaFactory = SchemaFactory
                    .newInstance(javax.xml.XMLConstants.W3C_XML_SCHEMA_NS_URI);
            factory.setSchema(schemaFactory.newSchema(schemaFileUrl));
            SAXParser parser = factory.newSAXParser();
            XMLReader reader = parser.getXMLReader();
            // Register the error handler
            reader.setErrorHandler(new JS_ValidationError());
            // Parse the file as the first argument on the command-line
            reader.parse(xmlFilePath);
        catch (SAXException e)
            System.out.println("Error: " + e.getMessage());
            e.printStackTrace();
        } catch (IOException e)
            System.out.println("Error: " + e.getMessage());
            e.printStackTrace();
        } catch (ParserConfigurationException e)
            // TODO Auto-generated catch block
            e.printStackTrace();
    } I have called this method ,but it issues this error :"unknown protocol" followed by windows partition name, in the debug I found that the value of the url is "*file://(*windows-partiton-char)/rest of path" !!!
this should work but it doesn't!!
so how can I fix this problem?
thanks

someone sent me this code to fix,it works:
package schemaValidationPackage;
* XsdSchemaSaxValidator.java
* Copyright (c) 2007 by Dr. Herong Yang. All rights reserved.
import javax.xml.validation.SchemaFactory;
import javax.xml.validation.Schema;
import javax.xml.XMLConstants;
import javax.xml.parsers.ParserConfigurationException;
import javax.xml.parsers.SAXParser;
import javax.xml.parsers.SAXParserFactory;
import javax.xml.transform.sax.SAXSource;
import org.xml.sax.InputSource;
import org.xml.sax.SAXException;
import org.xml.sax.XMLReader;
import javax.xml.validation.Validator;
import java.io.*;
import java.net.URL;
//also thanks for developer Hind Abd-El-Khalek
public class XsdSchemaSaxValidator {
     public static void validate(String xmlFilePath, URL schemaFileUrl)
        try
            SAXParserFactory factory = SAXParserFactory.newInstance();
            factory.setValidating(false);// stop standard validation to allow
                                            // custom schema
            factory.setNamespaceAware(true);
            SchemaFactory schemaFactory = SchemaFactory
                    .newInstance(javax.xml.XMLConstants.W3C_XML_SCHEMA_NS_URI);
            factory.setSchema(schemaFactory.newSchema(schemaFileUrl));
            SAXParser parser = factory.newSAXParser();
            XMLReader reader = parser.getXMLReader();
            // Register the error handler
            reader.setErrorHandler(new JS_ValidationError());
            // Parse the file as the first argument on the command-line
            reader.parse(xmlFilePath);
        catch (SAXException e)
            System.out.println("Error: " + e.getMessage());
            e.printStackTrace();
        } catch (IOException e)
            System.out.println("Error: " + e.getMessage());
            e.printStackTrace();
        } catch (ParserConfigurationException e)
            // TODO Auto-generated catch block
            e.printStackTrace();
public static void validateXml(Schema schema, String xmlName) {
    try {
      // creating a Validator instance
      Validator validator = schema.newValidator();
      // preparing the XML file as a SAX source
      SAXSource source = new SAXSource(
        new InputSource(new java.io.FileInputStream(xmlName)));
      // validating the SAX source against the schema
      validator.validate(source);
      System.out.println();
      System.out.println("Validation passed.");
    } catch (Exception e) {
      // catching all validation exceptions
      System.out.println();
      System.out.println(e.toString());
public static Schema loadSchema(String name) {
    Schema schema = null;
    try {
      String language = XMLConstants.W3C_XML_SCHEMA_NS_URI;
      SchemaFactory factory = SchemaFactory.newInstance(language);
      schema = factory.newSchema(new File(name));
    } catch (Exception e) {
      System.out.println(e.toString());
    return schema;
}

Schema validation for XMLType Clob vs Binary

Hi
Whilst looking at 11g R2 for use in validating XML against schemas, I have noticed that validation of XML using xmlDoc.schemavalidate() on a XMLType of CLOB would appear to be using a different schema validation process to validating by inserting into a column of XMLType of Binary.
A couple of things that drew my attention to this is 1) the slight difference in error message format , and 2) the fact that the validation for the Binary XMLType was detecting an error with a date format whilst validation of the CLOB wasn't.
Can anyone recommend which is the more thorough / robust of two ways to validate against a schema.
Many Thanks
Lawrence

You'll find the {forum:id=34} forum the more appropriate location for this question. Include all 4 digits of your version and if possible a short script that shows the issue you found.
Look in the [url https://wikis.oracle.com/display/Forums/Forums+FAQ]FAQ for how to use the tag to wrap your sample code and retain formatting when posting. This would include how the schema is registered (I'm assuming you did at least).

Catalog object schema validation failed(AGFIXBO2:EIRWWH9E)

Hi,
After copying my catalog from OBIEE 11.1.1.6.*0* (Build 120104.0800 64-bit) to 11.1.1.6.*7* (Build 121219.1257 64-bit).
Many of my report (particularly those with graphs) was not valid.
I have this message :
Catalog object schema validation failed: /shared/...
Error Details
Error Codes: AGFIXBO2:EIRWWH9E
Location: saw.httpserver.processrequest, saw.rpc.server.responder, saw.rpc.server, saw.rpc.server.handleConnection, saw.rpc.server.dispatch, saw.threadpool.socketrpcserver, saw.threads
The current xml is invalid with the following errors: Bad xml instance! <?xml version="1.0"?> <saw:report xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" .... Message:Value 'actual' is not in enumeration .
Please someone has any ideas to solve this issues.

Hello,
Check is post : Catalog object schema validation failed: 11.1.1.6.7 Patchset
Also check this note : OBIEE 11g: Error: "Catalog object schema validation failed...Error Codes: AGFIXBO2:EIRWWH9E" After Upgrade [ID 1247125.1]
Hope this helps. Pls mark if it does.
Thanks,
SVS

Excel cannot open the new form. The Form contains schema validation errors.

i am running the approval workflow on a document library, while trying to open Excel
file i get the error.
Excel cannot open the new form. The Form contains schema validation errors.
Detailed error:
Element '{http://schemas.microsoft.com/office/infopath/2009/WSSList/dataFields}Body' is
unexpected according to content model of parent element '{http://schemas.microsoft.com/office/infopath/2009/WSSList/dataFields}SharePointListItem_RW'.<o:p></o:p>
Expecting: {http://schemas.microsoft.com/office/infopath/2009/WSSList/dataFields}WorkflowLink,
{http://schemas.microsoft.com/office/inf....
neeraj

Hi,
According to your description, my understanding is that when you are running approval workflow and opening the Excel file, then it will occur the error above.
For a better troubleshooting, I suggest you can try to create a new normal excel file and then run the workflow and open the file to test if it works. It will help to figure out if this is the file itself issue or the SharePoint issue.
Also, please provide some more detailed information such as screen capture, it will easier to find the root cause of the issue.
Thanks
Best Regards
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Trouble with notifications - failed schema validation

I am trying to send an Email notification from a workflow and am getting the following error:
System.Web.Services: System.Web.Services.Protocols.SoapException: The request failed schema validation: The element 'Message' in namespace 'http://schemas.microsoft.com/exchange/services/2006/types' has invalid child element 'Header' in namespace 'http://schemas.xmlsoap.org/soap/envelope/'.
List of possible elements expected: 'Sensitivity, Body, Attachments, DateTimeReceived, Size, Categories, Importance, InReplyTo, IsSubmitted, IsDraft, IsFromMe, IsResend, IsUnmodified, InternetMessageHeaders, DateTimeSent, DateTimeCreated, ResponseObjects,
ReminderDueBy, ReminderIsSet, ReminderMinutesBeforeStart, DisplayCc, DisplayTo, HasAttachments, ExtendedProperty, Culture, Sender, ToRecipients, CcRecipients, BccRecipients, IsReadReceiptRequested, IsDeliveryReceiptRequested, ConversationIndex, ConversationTopic,
From, InternetMessageId, IsRead, IsResponseRequested, References, ReplyTo' in namespace 'http://schemas.microsoft.com/exchange/services/2006/types'.
   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.ResourceManagement.WebServices.Mail.Exchange.ExchangeServiceBinding.CreateItem(CreateItemType CreateItem1)
   at Microsoft.ResourceManagement.Mail.ExchangeProxy.ExecuteCreateItem(CreateItemType request)
   at Microsoft.ResourceManagement.Mail.ExchangeServer.SendNotification(NotificationMessage message)
   at Microsoft.ResourceManagement.Mail.NotificationMessage.Send(Int32 timeoutInMilliseconds)
   at Microsoft.ResourceManagement.Workflow.Hosting.SendMailWorkItemProcessor.SendMailMessage(MessageContent messageContent, Int32 timeoutInMilliseconds)
   at Microsoft.ResourceManagement.Workflow.Hosting.SendMailWorkItemProcessor.ProcessWorkItem(WorkItem workItem
It appears that the Exchange web service doesn't like the schema FIM is presenting. Anyone seen this? Is there a trace setting that will dump out the call to the Exchange
server?
I have tested that I can hit
https://fqdn_server/ews/exchange.asmx
from the FIM Service account and the certificate is correct.

After getting product support involved, it turns out that we were pointing the FIM Service at an Exchange 2013 server but the mailbox had been created on and was physically stored on an Exchange 2010 server. By pointing FIM at the 2010 server or by trying
to send notifications to mailboxes on the 2013 server, we could make it work. Moving the mailbox from the 2010 server to the 2013 server did not solve the problem. It had something to do with mailboxes that were originally created on a 2010 server but
were accessed over EWS from a 2013 server.
It also was not a FIM issue. We used an EWS diagnostic tool (EWSEditor) to test outside of FIM and saw the same results.
The final result to get the specific user working for notifications was to create a new mailbox for them on the Exchange 2013 server.

InfoPath - "Schema validation found non-data type errors." at XmlWriter.Close()

Greetings,
I'm creating a form that allows for emailing attachments however I am having an issue. When I try to attach a file, I get an "Schema validation found non-data type errors." error message. It seems like it's something with the XML structure and
I cannot find anything wrong.
Here is the code:
string myNamespace = NamespaceManager.LookupNamespace("my");
using (XmlWriter writer = MainDataSource.CreateNavigator().SelectSingleNode("/my:myFields/my:Email/my:AttachmentGroup", NamespaceManager).AppendChild())
//Write to XML
InfoPathAttachmentEncoder myEncoder = new InfoPathAttachmentEncoder(currentFile);
writer.WriteStartElement("Attachments", myNamespace);
writer.WriteElementString("attachment", myNamespace, myEncoder.ToBase64String());
writer.WriteElementString("attachmentCheckbox", myNamespace, "false");
writer.WriteEndElement();
writer.Close();
Here is the structure of the XML (root node is myFields):
<my:Email>
<my:AttachmentGroup>
<my:Attachments>
<my:attachment xsi:nil="true"></my:attachment>
<my:attachmentCheckBox>false</my:attachmentCheckBox>
</my:Attachments>
</my:AttachmentGroup>
<my:emailAddress>[email protected]</my:emailAddress>
<my:subject>Paychex ESR Services Paperwork</my:subject>
<my:body/>
<my:selectAll>false</my:selectAll>
</my:Email>
Attachments is the repeating group in this case.
Can anyone spot where the error is coming from?
Thanks!

HI,
I fixed it:
Below code is used to fix:
[CODE]
XPathNavigator xfield = null;
DateTime dtmyRecievedDate;
dtmyRecievedDate = Convert.ToDateTime(objInfopathFormcData.myRecievedDate);
if (objFormcData.FcCompletionDate != null)
xfield = myRoot.SelectSingleNode("/my:myFields/my:field97", NamespaceManager);
DeleteNil(xfield);
xfield.SetValue(dtmyRecievedDate.GetDateTimeFormats().GetValue(5).ToString());
// method to delete xsi:nil
private void DeleteNil(XPathNavigator nav1)
if (nav1.MoveToAttribute("nil", "http://www.w3.org/2001/XMLSchema-instance"))
nav1.DeleteSelf();
[/CODE]
Thank you

Getting schema validation working in Eclipse with Coherence 3.7.1.0

Just wondered if anyone had got schema validation to work in Eclipse (3.5 - Galileo) for Coherence 3.7.1.0?
The Coherence developer docs show that you should add sections like this:
<pof-config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://xmlns.oracle.com/coherence/coherence-pof-config"
xsi:schemaLocation="http://xmlns.oracle.com/coherence/coherence-pof-config
coherence-pof-config.xsd">
However, if I use that "shortened" form (for cache, pof, etc. configs) Eclipse gives a warning "No grammar constraints (DTD or XML schema) detected for the document." and the schema validation fails to work (i.e. no "auto pop-ups" when entering content, and rubbish content is gladly accepted.)
In Coherence 3.7.0, I'd used the following "extended" form (note the longer "schemaLocation") to get things working correctly:
<pof-config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://xmlns.oracle.com/coherence/coherence-pof-config"
xsi:schemaLocation="http://xmlns.oracle.com/coherence/coherence-pof-config
http://xmlns.oracle.com/coherence/coherence-pof-config/1.0/coherence-pof-config.xsd">
Also note that entering the "http://xmlns.oracle.com/coherence/coherence-pof-config/1.0/coherence-pof-config.xsd" in a web browser opens the xsd, as you'd expect.
Now...
I'm looking at the PofAnnotationSerializer in 3.7.1.0 and the "auto indexing" option. The declaration in my pof file for it fails as the "class" (or fully-qualified java.lang.Class version) in the "init-params" section isn't valid. If I look at the xsd on the url above, this is indeed the case, that option does not appear.
However, if I look at the POF xsd in the coherence.jar file for 3.7.1.0, the "class" option has been added, and has a newer 'version="1.1"' added to it's schema declaration. So I therefore tried to point my "extended" declaration to point to " http://xmlns.oracle.com/coherence/coherence-pof-config/1.1/coherence-pof-config.xsd", in order to get schema validation to work in Eclipse with this new schema. Unfortunately that url doesn't exist - you get a "Content Server Request Failed" error.
So, I guess my question is, is there a way to get myself pointed at the 1.1 versions of the xsd's so I can have schema validation working in Ecliipse? Or is there another workaround (did a bit of Googling, but that mainly seemed to be people switching validation off to simply get rid of the error...)
Cheers,
Steve

Cheers, Dave.
I had in fact had a try at extracting the xsd and pointing to it directly, and that did indeed work (had to do this following the same steps shown below using an "entry" in the XML Catalog.)
I had a look around at some of the other "entries" in Eclipse by default and noticed that they actually refer to xsd's directly within the jars, hence saving the extraction step and keeping screw-ups down to a minimum; a bit of playing around to get the syntax right and I finally managed to get it working.
For those who are interested (NB. my Coherence 3.7.1.0 install is in a directory "c:\coherence3.7"), the steps are:
In Eclipse, Go to Window->Preferences->XML->XML Catalog. Then create a "User Specified Entry".
In the "Location", add (without the quotes): "jar:file:/C:/coherence3.7/coherence/lib/coherence.jar!/coherence-pof-config.xsd"
In the "Key Type", add (without the quotes): "Namespace Name"
In the "Key", add (without the quotes): "http://xmlns.oracle.com/coherence/coherence-pof-config"
The schema validation now works fine. Eclipse shows no warnings/errors, and the auto-complete and validation are fully functional.
Still, it would be nice to get the "1.1" urls updated to point to the schemas on the Oracle site, to avoid all our developers from having to make these changes (and of course avoid them pointing at an older, out-of-date local install of coherence.)
Cheers,
Steve

Schema Validator does not honor "nullable" attribute

Oracle XML Schema validator v1.0 does not seem to honor "nullable" schema attribute as in:
<xsd:element name='myelem' type='xsd:string' nullable='true'/>
On input
<myelem/> or <myelem></myelem>
it reports:
Element not completed: 'myelem'
Thanks
null

My mistake. Input must be specified as:
<myelem xsi:null="true">
where
xmlns:xsi="http://www.w3.org/1999/XMLSchema/instance"
null

"Schema validation found non-data type errors" error when passing a string value to date field in infopath

Hi,
I have an infopath web brower enabled form. In the form i have a date field.
I am passing the data from the database to that field using the C# code.
But, as the field from database is coming as string, i am getting an error, and i am not able to assign the value.
I get the date value from database as "3/25/2011 12:00:00 AM"
I used the below code:
[CODE]
if (objInfopathFormcData.myRecievedDate != null)
myRoot.SelectSingleNode("/my:myFields/my:field97", NamespaceManager).SetValue(objInfopathFormcData.myRecievedDate);
[/CODE]
I am getting the error as "Schema validation found non-data type errors".
How to set the value for a date field in Infopath.
Thank you

HI,
I fixed it:
Below code is used to fix:
[CODE]
XPathNavigator xfield = null;
DateTime dtmyRecievedDate;
dtmyRecievedDate = Convert.ToDateTime(objInfopathFormcData.myRecievedDate);
if (objFormcData.FcCompletionDate != null)
xfield = myRoot.SelectSingleNode("/my:myFields/my:field97", NamespaceManager);
DeleteNil(xfield);
xfield.SetValue(dtmyRecievedDate.GetDateTimeFormats().GetValue(5).ToString());
// method to delete xsi:nil
private void DeleteNil(XPathNavigator nav1)
if (nav1.MoveToAttribute("nil", "http://www.w3.org/2001/XMLSchema-instance"))
nav1.DeleteSelf();
[/CODE]
Thank you

Schema validation issue

Similar Messages

Maybe you are looking for