So you are suggesting that I define my own
xsd file and validate the instance against it ?
-Original Message-
From: Jeff Greif
[mailto:[EMAIL PROTECTED]
Sent: Sunday, January 19, 2003 11:42 PM
To: [EMAIL PROTECTED]
Subject: Re: another Validation
question
Since you are v
Hi Joseph,
I'm afraid nobody will be able to answer this w/o seeing the your code (the
one with the SAXParser).
So if you could send it (or just a fragment when you initialize SAXParser,
start parsing and process the SAX events) it would be hepful.
Plus, include Xerces version information.
thanks
Hi,
When US-ASCII encoding is specified Xerces should automatically use
ISO-8859-1 (java encoding 8859_1), so it should work fine. This is IANA-Java
encoding mapping specified in Xerces.
thanks
-Original Message-
From: Elliotte Rusty Harold [mailto:[EMAIL PROTECTED]
Sent: Monday, January
[EMAIL PROTECTED] wrote:
Hi Joseph,
I had a feeling something like that might have been the case. I'll bet
there's some difference in the way you're viewing the SAX output as
compared to the DOM output.
No, I made sure that that isn't a problem.
---
Hi,
There are examples* of reading a simple document for DOM and SAX --
wrap your input in an appropriate reader (e.g. if you read it into a string a
StringReader) and parse from that. If you're wondering whether to use SAX or
DOM -- well for such a small document I'd say it w
I've not done much with Java and never done anything with XML, and I've
looked all over for a simple example with no luck. So please excuse my
newbieness.
My Java client opens a socket and reads the following XML data:
TOWER1052195
How do I parse this so I can use it? I'm going to use the data
Write an entity resolver
(http://xml.apache.org/xerces2-j/javadocs/api/org/xml/sax/EntityResolver.html),
and returned an input source with a StringReader when the schema document
is asked.
HTH,
Sandy Gao
Software Developer, IBM Canada
(1-905) 413-3255
[EMAIL PROTECTED]
At 3:23 PM +0100 1/20/03, Hermann Angstl wrote:
Enable/disable validation doesn't change anything :((
Does this really mean that the parser can't parse US-ASCII ?
Earlier version of Java did not recognize the encoding name "ASCII".
You can try "US-ASCII" instead, but even that fails in 1.3 and
e
I saw
a thing in the ant documentation which you may be able to pick up a few tips
from - it sounds like what you are trying to do (although they validate against
DTDs). You may need to peek at their code to see how to do
it...
http://jakarta.apache.org/ant/manual/OptionalTasks/xmlvalidat
Hi,
i am using xerces (tried both, DOM and SAX) and get the following
exception:
org.xml.sax.SAXException: The encoding "ASCII" is not supported
my code:
...
Parser parser =
ParserFactory.makeParser("org.apache.xerces.parsers.SAXParser");
parser.setDocumentHandler(this);
parser.setErrorHandler(
Hi all,
Last week I sent an email regarding the xml
validation against the schema, but didn't get any reply. Please reply if
any one has answer to my question. Is it possible to validate an xml document
using a schema document (not the schema url) that is present with in the
application. If
Since you are validating the document
against the wsdl schema, it must conform to the WSDL schema. The root
element, must have element content of
?,*
? ,*,*,*,
* (and, in WSDL 1.2, *). No other
element content is permitted. At least one content element other than
documentation must be
I Have two questions,
1)
I get this following error. I understand
the meaning of it, (or I think so).
I have defined "slt"
in the wsdl file.
[Error]:20:40: cvc-complex-type.2.4.a: Invalid content
starting with element 'slt:ser
viceLinkType'. The content must match
'"http://s
13 matches
Mail list logo