Hey,
I feel we really should move to the latest version of the spec, even if
we don't fully implement it. Its difficult for new users, users who are
using both c + j and it makes the project seem like not a lot is
happening - even though that is not true.
If we do move, it does make sense to
I agree that we should move to the future and shed old baggage.
I propose that we create a 2.6.x branch, and get CVS HEAD headed toward
a 3.0 release, covering the latest version of the spec, which might be
unstable for a while.
Perhaps this would also be a good time (pre-branch) to move to
sub
> I feel we really should move to the latest version of the spec, even if
> we don't fully implement it. Its difficult for new users, users who are
> using both c + j and it makes the project seem like not a lot is
> happening - even though that is not true.
It definitely looks that way from th
Hello,
I think that I have read everything I can on the site, but I can't find
anything that tells me how to get the Mac OS 10 code. Is there a tar
file available or do I need to get it from the CVS repository?
I apologize if I've been blind, I really have spent a long time looking
before final
Hi Scott,
In the last version of Xerces-C, there
was fix for the DOM normalization problem. When the feature is set to false,
you'll get back the non schema normalized value. Is this still a problem
for you?
Khaled
"Scott Cantor"
<[EMAIL PROTECTED]>
02/08/2005 10:46 AM
Please respond
Wow. This is an ambitious proposal. As a user, it sounds wonderful,
including the build infrastructure cleanup. (I don't use the current
system, but posts to the list over the years have made it clear that
it's problematic for many people.) I don't know how long it might take
to accomplish it a
> In the last version of Xerces-C, there was fix for the DOM
> normalization problem. When the feature is set to false,
> you'll get back the non schema normalized value. Is this
> still a problem for you?
That particular approach is not ideal (and it's a fairly old fix, not
recent), but more
That's the fix that I'm talking about.
The DOM will store the non schema normalized value (when validation is
on and the dom normalization feature is off).
Khaled
"Scott Cantor"
<[EMAIL PROTECTED]>
02/08/2005 11:26 AM
Please respond to
xerces-c-dev
To
cc
Subject
RE: Request
I think you'll need to download and build the source. Go to
http://xml.apache.org/xerces-c/download.cgi and click the mirror link in
the second paragraph. (You can select another mirror farther down the
page.) You'll probably want xerces-c-src_2_6_0.tar.gz. Then go back to
the Xerces download p
> That's the fix that I'm talking about. The DOM will store the
> non schema normalized value (when validation is on and the
> dom normalization feature is off).
I understand that. But the Base64 datatype validator has a new flag in 2.6
that causes a strict validation against the DOM-stored val
Rush,
There are no supplied, pre-built Xerces binaries for Mac OS X.
As Jesse says, there are a number of supported ways of building Xerces
for Mac OS X. The most likely these days are the Xcode build and the
traditional command line/make build.
Another way to get Xerces for Mac OS X would be th
Hi Scott,
The way it used to work for validating
character content, was to normalize the value before passing it on to the
datatype validator. If validation is successfull we pass the normalized
value to the doucment handler. In the DOM case, the document handler will
be a DOM parser, and the par
James and Jessie,
Thanks for the help. About 20 minutes after I posted the question, I got
the *brilliant* idea to download the source tar file and see what it
contained. Lo and behold, there was the MacOS code! Doh!
Anyway, I got it yesterday and built with Xcode. I have also built and
tested
> normalized value. There's a fix after 2.6 that changed the
Sorry, when you said "last version", I assumed you meant either 2.5 or 2.6,
but not unreleased cvs. ;-)
What you describe is indeed the fix I expected.
-- Scott
-
T
Hi,
I am trying to set the feature fgXercesSchemaExternalSchemaLocation
to a schema path
Using Visual C++ and it blows up. I am using
the following code.
// Begin code.
DOMImplementation *pImpl = DOMImplementationRegistry::getDOMImplementation(gLS);
m_pValidator=((DOMImplementationLS*)pImpl)c
Am Dienstag, 8. Februar 2005 18:29 schrieb
[EMAIL PROTECTED]:
> // Problem code.
>
> m_pValidator->setFeature(XMLUni::fgXercesSchemaExternalSchemaLocation,
> pszSchemaPath);
>
> // End code
>
> psSchemaDir is a fully qualified schema path. (ie
> z:\schema\schema.xsd)
>
> My goal is to ignore the
[ http://issues.apache.org/jira/browse/XERCESC-1338?page=history ]
Alberto Massari closed XERCESC-1338:
Resolution: Duplicate
This is a duplicate of XERCESC-866, that has been fixed after 2.6 was released.
To get the fix, you can download versi
Hi everybody,
I'm about to release a commercial application, which uses Xerces-C++.
I've read the apache license v2.0 and its FAQ, and still I don't know
what exactly should I do!
I know this is tedious, but please bear with me, I'm not good at this
legal stuff.
can some one tell me some steps, wh
18 matches
Mail list logo
