I've been playing with the EntityResolver class for a bit and I think I've
got it all working, but I noticed that publicId always comes in as an empty
string. In what cases would publicId actually be populated and/or how should
my code handle it in relation to systemId.
 
Thanks.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 13, 2001 11:35 AM
To: [EMAIL PROTECTED]
Subject: RE: Using Schema Validation




You can use EntityResolver interface to tell the Parser where to look for 
schemas. You will have to implement resolveEntity(String publicid,String
SystemId) to resolve the URI. 
-----Original Message----- 
From: Beyer,Nathan [ mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] 
Sent: Thursday, September 13, 2001 9:49 AM 
To: '[EMAIL PROTECTED]' 
Subject: RE: Using Schema Validation 


Good call, I missed that one. I also had to stop declaring this feature: 
http://apache.org/xml/features/validation/dynamic
<http://apache.org/xml/features/validation/dynamic>  to true. When I left it
as 
the default false the schema validation started working. Does that feature 
somehow conflict with http://apache.org/xml/features/validation
<http://apache.org/xml/features/validation> ? 

The next issue I ran into though is the use of relative references in 
<xsd:include/> elements. For example, I have a number of schema sitting in a

directory structure that all point to various documents in the structure, 
like this: <xsd:include schemaLocation="../Message.xsd"/>. The problem I'm 
having is that when the schema is parsed it doesn't look up the included 
file relative to the schema that includes it. Do I have put absolute 
references in all of my schemas or is there some sort of URI resolver 
interface that I can implement to solve this? 

Thanks. 

-----Original Message----- 
From: Venkatesh Vedurumudi [ mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> ] 
Sent: Thursday, September 13, 2001 3:55 AM 
To: [EMAIL PROTECTED] 
Subject: Re: Using Schema Validation 


Hi Nathan Beyer, 

    For your information. 

> MyXML.xsd - 
> <?xml version="1.0" encoding="UTF-8"?> 
> <xsd:schema xmlns:xsd=" http://www.w3.org/2001/XMLSchema-instance
<http://www.w3.org/2001/XMLSchema-instance> " 

In the XML schema file, you need to mention the name space as: 

<xsd: schema xmlns:xsd= http://www.w3.org/2001/XMLSchema
<http://www.w3.org/2001/XMLSchema>  

and not as http://www.w3.org/2001/XMLSchema-instance
<http://www.w3.org/2001/XMLSchema-instance> .  

-- Venkatesh 


_________________________________________________________ 
Do You Yahoo!? 
Get your free @yahoo.com address at http://mail.yahoo.com
<http://mail.yahoo.com>  


--------------------------------------------------------------------- 
To unsubscribe, e-mail: [EMAIL PROTECTED] 
For additional commands, e-mail: [EMAIL PROTECTED] 



CONFIDENTIALITY NOTICE 

This message and any included attachments are from Cerner Corporation and
are intended only for the addressee.  The information contained in this
message is confidential and may constitute inside or non-public information
under international, federal, or state securities laws and is intended only
for the use of the addressee.  Unauthorized forwarding, printing, copying,
distributing, or using such information is strictly prohibited and may be
unlawful.  If you are not the addressee, please promptly delete this message
and notify the sender of the delivery error by e-mail or you may call
Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)
221-1024.

------------------------------------------------------------------------ 

--------------------------------------------------------------------- 
To unsubscribe, e-mail: [EMAIL PROTECTED] 
For additional commands, e-mail: [EMAIL PROTECTED] 





CONFIDENTIALITY NOTICE

This message and any included attachments are from Cerner Corporation and are 
intended only for the addressee.  The information contained in this message is 
confidential and may constitute inside or non-public information under 
international, federal, or state securities laws and is intended only for the 
use of the addressee.  Unauthorized forwarding, printing, copying, 
distributing, or using such information is strictly prohibited and may be 
unlawful.  If you are not the addressee, please promptly delete this message 
and notify the sender of the delivery error by e-mail or you may call Cerner�s 
corporate offices in Kansas City, Missouri, U.S.A at (+1) (816) 221-1024.
------------------------------------------------------------------------
Title: RE: Using Schema Validation
I've been playing with the EntityResolver class for a bit and I think I've got it all working, but I noticed that publicId always comes in as an empty string. In what cases would publicId actually be populated and/or how should my code handle it in relation to systemId.
 
Thanks.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 13, 2001 11:35 AM
To: [EMAIL PROTECTED]
Subject: RE: Using Schema Validation


You can use EntityResolver interface to tell the Parser where to look for
schemas. You will have to implement resolveEntity(String publicid,String SystemId) to resolve the URI.
-----Original Message-----
From: Beyer,Nathan [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 13, 2001 9:49 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Using Schema Validation


Good call, I missed that one. I also had to stop declaring this feature:
http://apache.org/xml/features/validation/dynamic to true. When I left it as
the default false the schema validation started working. Does that feature
somehow conflict with http://apache.org/xml/features/validation?

The next issue I ran into though is the use of relative references in
<xsd:include/> elements. For example, I have a number of schema sitting in a
directory structure that all point to various documents in the structure,
like this: <xsd:include schemaLocation="../Message.xsd"/>. The problem I'm
having is that when the schema is parsed it doesn't look up the included
file relative to the schema that includes it. Do I have put absolute
references in all of my schemas or is there some sort of URI resolver
interface that I can implement to solve this?

Thanks.

-----Original Message-----
From: Venkatesh Vedurumudi [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 13, 2001 3:55 AM
To: [EMAIL PROTECTED]
Subject: Re: Using Schema Validation


Hi Nathan Beyer,

    For your information.

> MyXML.xsd -
> <?xml version="1.0" encoding="UTF-8"?>
> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance"

In the XML schema file, you need to mention the name space as:

<xsd: schema xmlns:xsd=http://www.w3.org/2001/XMLSchema

and not as http://www.w3.org/2001/XMLSchema-instance

-- Venkatesh


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



CONFIDENTIALITY NOTICE

This message and any included attachments are from Cerner Corporation and are intended only for the addressee.  The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws and is intended only for the use of the addressee.  Unauthorized forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful.  If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816) 221-1024.

------------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to