[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

[xsl] Re: Getting info of runtime failure in saxon environment

Subject: [xsl] Re: Getting info of runtime failure in saxon environment
From: Karlmarx R <karlmarxr@xxxxxxxxx>
Date: Wed, 27 Feb 2013 17:25:03 +0800 (SGT)

Thanks Wendell. To answer your quesions, para wise:
(A) They will use browser
for basic well-formedness and this is not an issue. But the requirement is to
identify where the problem lies within xml.

(B) Yes, this is the issue, to
get better feedback. They get the input XML from oracle. Some internal oracle
function does the data extraction and forms the XML. A unix based cron job
does this overnight (i don't have much info but can get if needed). After that
that input (which may not be WELL-FORMED) is supposed to go thru
transformation in xsl-saxon (on unix) and here the failure won't five that
much clue. 

What I do know is that at times the data comes with some "chars"
that makes the XML not well formed. I have asked them whether they can do some
basic cleaning(?) during the data extraction within oracle function. This
seems to be the best wayto me, but at the same time would like to know the
possibilities of:
 (1) if saxon failure can give some additional info that
"line num so on so" is incorrect ot whatever, along with the error msg it
gets. This I understand is not possible from your prev reply. So.. [OR]
okay after seeing the failure, they open that in some tools(?, currently it is
browser) which points them  "line num so on so" is incorrect so that they open
it in notepad++ sort of text editor and look into that to fix!!. so

(C) Pls
can you recommend some lightweight XML editors that they can use / try to
detect the error in xml in the above scenario?

Tue, 26 Feb 2013 15:41:38 -0500
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Wendell Piez <wapiez@xxxxxxxxxxxxxxx>
Subject: Re: [xsl] Re: Getting info of
runtime failure in saxon environment

Hi Karl,
I'm afraid your question doesn't have a single answer. It depends on
too many
local factors.

There are plenty of XML processors available which you can use
to test
files for basic syntactic correctness (well-formedness); any computer
you buy nowadays already comes with several. Your browser is one. You
ask your users to open their files in a browser and make sure
they don't get
syntax errors.

But when they make mistakes and have to fix something, what
will they
be able to do to correct them? They probably need better feedback
an ugly error message if something is wrong, or not much of anything
everything is okay. What applications are they already using to
create and
edit their XML?

Building this kind of workflow means not only deploying the
tools, but
also providing the support. In fact, I think the support comes
If your users don't have the technical expertise to be responsible for
themselves, you need someone whose role it is to share the
responsibility and
to help others learn to do so. They will find (or
build) tools that work well
for the problem domain and the tools the
users are already familiar with.
These might be lightweight XML
editors, or web services where you can upload
files, or command-line
utilities that can be called from a text editor, or any
number of
other things.

Cheers, Wendell

Current Thread