Cantor, Scott writes:
> I still need to test the Windows build, but I've uploaded an
> RC for 3.3.0 [1]
We've tested the RC in 90+ build configurations (all the major
platforms and compilers, but in C++11 or later only):
https://ci.stage.build2.org/@071ef8c6-5d1a-4e3d-9bd0-acc62fc51d5c
All loo
Cantor, Scott writes:
> I've resolved most of the issues I can feasibly tackle for 3.3,
> possibly a CMake change or two left if I get responses.
Sounds good, thanks for your effort!
> Should be able to spin a RC next week.
Great, will package and test.
--
Cantor, Scott writes:
> As is apparent from the Jira messages, I'm starting to look at
> a 3.3.0 to fix a bug in the Curl support along with some miscellany.
Great, thanks for your effort!
> ETA is probably October some time.
I would be happy to package the RC and test it on our 100+ build
co
Cantor, Scott writes:
> The Xerces project has released V3.2.5 of the C++ parser library [...]
Thanks for making the release and doing all the administrative stuff!
-
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
Cantor, Scott writes:
> I suggest we wait until next Wednesday and close the vote
> that morning. I should be able to complete the release and
> check in the site updates that day.
Sounds good to me, thanks!
-
To unsubscribe,
Cantor, Scott writes:
> Windows has not yet been tested.
I've built and tested using standard CMake/ninja instructions in
both debug and release build types with MSVC 17.6 (19.36.32534).
No errors, all tests passed.
> If Windows builds, this would be the candidate to vote out.
My +1 for the r
[
https://issues.apache.org/jira/browse/XERCESC-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793670#comment-17793670
]
Boris Kolpackov commented on XERCESC-2188:
--
A new PR with the fix: [h
Thomas Ranneberger writes:
> I am attempting to take provided .xsd files that detail the xml schema
> definitions of certain message types, and turn these into C++ classes
> for sending messages and validating those message fields. Does this
> sound like something Xerces is capable of doing?
The
Cantor, Scott writes:
> I am open to either doing a patch at some point after a little
> time elapses or officially moving the code base to C++-11.
I would prefer to move to C++11. If nobody cares, why create
unnecessary churn by making another release?
I propose the following plan:
1. Wait a
Cantor, Scott writes:
> I've patched the use of nullptr out simply for consistency but there's
> no apparent need to rush out a fix, so I'll let it sit for the time
> being.
I don't mind waiting (to see if anything else shakes out) but I think
we either need a bugfix release eventually or offici
Roger Leigh writes:
> nullptr is a language keyword, so that should just have worked. Unless
> an older language standard was being explicitly forced, the use of
> nullptr should be benign.
nullptr was added in C++11 so by using it you effectively drop
support for C++98/03. I personally don't
Cantor, Scott writes:
> On 10/12/22, 9:09 AM, "Boris Kolpackov" wrote:
>
> >2. We build with ICU and Curl everywhere so other transcoders
> > and netaccessors were not tested.
>
> Do you actually use them? Because in my testing, I haven't man
Cantor, Scott writes:
> I've posted a signed RC here:
> https://dist.apache.org/repos/dist/dev/xerces/c/3/sources/
We've updated our build2 package[1] to RC1 and ran the CI. Everything
seems to be fine except for the wasm32-emscripten target, which is
not unexpected. The complete list of tested
Cantor, Scott writes:
> On 10/11/22, 10:28 AM, "Boris Kolpackov" wrote:
>
> >Remind me where does the source for the front page live?
>
> doc/readme.xml I think (it's in doc, but page is from memory, should
> be clear from the commit).
That's what
Cantor, Scott writes:
> On 10/10/22, 12:17 PM, "Boris Kolpackov" wrote:
>
> >Not every application that uses Xerces-C++ is security sensitive.
>
> If that were our perspective as a project, then among other things
> there should be no networking code i
Cantor, Scott writes:
> Done, v3.2.4rc1.
Thanks!
> > The web site update embedded in it includes a note on the front page
> > that the library lacks maintainers and should not be used for new
> > projects. Are we talking about this change or something else?
>
> I changed both the front page a
Cantor, Scott writes:
> I've posted a signed RC here:
> https://dist.apache.org/repos/dist/dev/xerces/c/3/sources/
Thanks for your work on this!
The corresponding git branch is xerces-3.2 and the commit is
bfe32a149e8c ("Adjust release info."), correct? Wouldn't be
bad to tag the RC to make sur
Cantor, Scott writes:
> On 10/10/22, 10:14 AM, "Boris Kolpackov" wrote:
>
> > What would be the other options for XML Schema validation usable
> > from C++?
>
> Libxml2?
>
> Says it supports XML Schema 1.0 (which is all Xerces ever did AFAIK).
Last ti
Roger Leigh writes:
> If Xerces-C++ was to be retired, projects will need to consider other
> options, be that other libraries, or other languages.
What would be the other options for XML Schema validation usable from C++?
It's easy to say people should do this and that in the abstract. Given a
Cantor, Scott writes:
> Were it my decision, I would post a warning that the code is being
> sunsetted and anybody on it should be getting off it.
Getting off to what? Xerces-C++, with all its warts, is the only working,
open source XML Schema implementation for C/C++. And I know for a fact
that
Roger Leigh writes:
> Would it be possible to add 3.2.4 as a new unreleased version in Jira?
Done.
> As you have probably seen, Even Rouault has made several changes to
> fix bugs on the 3.2 branch, and it would be useful to release them.
Sounds good. Is Even finished with everything they wan
Michael Behrisch writes:
> I saw that there are libcurl implementations for Windows as well:
> https://stackoverflow.com/questions/53861300/how-do-you-properly-install-libcurl-for-use-in-visual-studio-2017
> but the docs say libcurl does not work with Windows. Did nobody try yet
> or are there an
We've added build2[1] build support for Xerces-C++ (in a separate
repository[2]) and it's now available as a package on cppget.org:
https://cppget.org/libxerces-c/
For now it's a uniform libcurl/ICU-based configuration on all
platforms/compilers. We are currently building and testing it for
37 bu
Roger Leigh writes:
> I'm not entirely sure how to class code written using L"". It's not really
> portable, being Windows-only as you say (Windows being the only platform
> where wchar_t is 16-bit and usable as XMLCh). And it's not strictly portable
> even to different builds of Xerces-C, given
Hi Roger,
Thanks for getting the ball rolling. See my comments below.
Roger Leigh writes:
> One of the issues I encountered was difficulty in building on modern
> platforms, Windows in particular, which was the impetus for developing
> the CMake build now incorporated officially in the Xerces-C
[
https://issues.apache.org/jira/browse/XERCESC-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17136595#comment-17136595
]
Boris Kolpackov commented on XERCESC-2204:
--
I think it's pretty cl
[
https://issues.apache.org/jira/browse/XERCESC-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17133959#comment-17133959
]
Boris Kolpackov commented on XERCESC-2204:
--
I am not sure about this. W
+1
Thanks!
-
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
Cantor, Scott writes:
> I have external constraints such that if I'm going to do this patch release
> it needs to be done next week, so any remaining work would need to be in
> this week so I can do a build for vote early next.
>
> There is nothing I would expect is getting done that I think is
Cantor, Scott writes:
> On 3/6/20, 9:56 AM, "Boris Kolpackov" wrote:
>
> > I am not aware though from the names internal/ and dom/impl/ should be
> > off-limits while everything else is probably fair game.
>
> I'm happy if we decide we just say that si
Cantor, Scott writes:
> I may have mispoke in that issue too: is there any formal definition of
> which include directories are "API" and which should be off limits for
> library clients?
I am not aware though from the names internal/ and dom/impl/ should be
off-limits while everything else is p
Cantor, Scott writes:
> Normally I wouldn't be keen to branch now if the next patch was to 3.2,
> but because the changes are so minimal now, maintaining patches to two
> branches would not be very much work.
Ok, makes sense, thanks.
-
Cantor, Scott writes:
> There's an open bug or two that probably would need to lead to an API bump
> from 3.2 and the suggestion was made that even if we may not have a ton of
> active effort, there may be value in allowing such work to occur if the
> cycles to do it happen to be available.
>
> I
The Xerces-C++ project has switched to Git and I have asked Infra to mark
everything under https://svn.apache.org/repos/asf/xerces/c/ as read-only.
As discussed, the two new repositories are:
xerces-c.git
xerces-c-admin.git
You can use either the Apache GitBox:
https://gitbox.apache.org/
Roger Leigh writes:
> I've opened an initial pull request on GitHub here:
> https://github.com/apache/xerces-c/pull/1
>
> I didn't see Scott on GitHub, so I added Boris as a reviewer. This change is
> basically to ensure that we have sanity in line ending conventions when
> making changes with c
Cantor, Scott writes:
> It's just https://gitbox.apache.org/repos/asf/reponame.git
Got it, thanks.
Are you all setup for write access to xerces-c.git? Can you maybe
push and delete a test branch just to confirm?
-
To unsubscri
I've created the xerces-c.git repository and pushed the conversion
result with the latest changes:
https://gitbox.apache.org/repos/asf?p=xerces-c.git
https://github.com/apache/xerces-c.git
If everyone is happy, I can ask Infra to mark the SVN repository
read-only (until that happens, please trea
Vincent Ulitzsch writes:
> Bhargava and I sent a PR your way using this new git:
> https://github.com/boris-kolpackov/xerces-c/pull/1
> However, it seems to me that the new git might not be the right place
> for this PR.
Correct, this is a temporary repository that I published for
Cantor, Scott writes:
> On 12/20/19, 4:21 AM, "Boris Kolpackov" wrote:
>
> > Wouldn't checking out corresponding tags from Git and SVN and then
> > running diff on the directories (ignoring .git/ and .svn/) be
> > sufficient?
>
> Yes, either way.
Cantor, Scott writes:
> I don't know enough to say what the cherry-pick warnings mean, [...]
I did a bit of googling on this one and it appears to be harmless.
> For us it took weeks of time over months to get it right, but we don't
> have that kind of time.
Right. I did spend a couple of day
Cantor, Scott writes:
> On 12/16/19, 5:08 AM, "Boris Kolpackov" wrote:
>
> > Please let me know if you see any issues. And if everything looks
> > good, I would like to proceed with pushing this to its "official"
> > place and then requesti
I've finally got around to converting the Xerces-C++ SVN repository
to Git and the result is available for inspection here:
https://github.com/boris-kolpackov/xerces-c
The conversion log (specifically, the git-svn fetch log) is available
here:
https://codesynthesis.com/~boris/tmp/xerces-sv
I see[1] that Xerces-C++ packages are no longer part of RHEL/CentOS 8.
Anyone knows the back story and if there are any alternative sources,
like Fedora's EPEL (web search didn't yield anything promising)?
Actually, scratch that, there is EPEL 8[2] and Xerces-C++ 3.2.2
is there[3].
[1]
https://
Ok, I've got the ball rolling on this, sorry for the delay:
https://issues.apache.org/jira/browse/INFRA-18755
-
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache
Cantor, Scott writes:
> On 5/13/19, 9:23 AM, "Boris Kolpackov" wrote:
>
> > I also think we can drop any mentinoning of 2-series during this
> > conversion. There are, however, other bits of the documentation
> > (like Doxygen-generated). Here is step #15 th
Roger Leigh writes:
> Mentioned briefly a few months back, but we could take the Git migration as
> an opportunity to convert the old StyleBook XML to Markdown and move the
> docs to github pages, generated directly from git automatically.
I assume the "github pages" part is acceptable to Apache
Cantor, Scott writes:
> On 4/29/19, 10:34 AM, "Boris Kolpackov" wrote:
>
> > The latter two are direct copies from the web/ and admin/ SVN directories.
>
> I believe that the web/ repository is actually directly published as
> the web site, so there probably is
Roger Leigh writes:
> > xerces-cxx.git
> > xerces-cxx-web.git
> > xerces-cxx-admin.git
>
> Do we need "-cxx" as a suffix here, or would "-c" be better?
Yes, good point. Our source distributions are called xerces-c, binary
packages seem to also be called like that (e.g., Debian's, libxerces-c).
The vote to migrate the Xerces-C++ repository from SVN to Git has
passed and I would like to discuss the next step.
According to https://gitbox.apache.org, this should be as easy
as opening and issue with the Apache Infra. Before doing this,
however, it would be good to agree on the desired reposi
Boris Kolpackov writes:
> I would like to call for a vote to migrate Xerces-C++ SVN repositories
> to Git, specifically, to the Apache Gitbox service:
>
> https://gitbox.apache.org/
The vote passes with 7 in favor and 0 against.
Shortly I am going to send an email to c-dev with
I would like to call for a vote to migrate Xerces-C++ SVN repositories
to Git, specifically, to the Apache Gitbox service:
https://gitbox.apache.org/
This is my +1.
-
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
F
Roger Leigh writes:
> With the reboot of the Xalan PMC, the Xalan SVN repositories are currently
> being converted to Gitbox.
For those unaware, Gitbox is the Apache's Git service with writable
mirroring on GitHub:
https://gitbox.apache.org/
> Would it please be possible to do this for the Xe
Cantor, Scott writes:
> Practically speaking, the security process and the web site have been the
> main sources of friction for me, and I think the latter is definitely a
> choice. We could simply accept that it's not viable and shut it down in
> favor of a simple wiki page with the download lin
Roger Leigh writes:
> I'm doing all my work in git using the git mirror anyway,, so I would be
> more than happy to use git for the main repository. It's much more
> efficient.
Great!
> Regarding build2, are there sufficient benefits over the existing autotools
> and cmake build to make it wo
Cantor, Scott writes:
> No concerns with git, if that's something Apache allows as the
> "official" repo now [...]
I would sure hope so.
> My only concern with the build system is that I need the autoconf
> support so as long as that's not going anywhere, anything else is
> up to the people of
I would like to add support for the build2[1] build system, similar
to how it was done recently for CMake. One of the benefits will be
continuous building and testing[2] on a wide range of platforms and
compilers[3] (currently 33). I am committing to maintaining this
support going forward.
Before
+1 & thanks for all the hard work!
Boris
-
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
Cantor, Scott writes:
> I don't know what the baseline has been for the code base, is C99 a
> reasonable requirement?
>
> I need SIZE_MAX to fix some bounds checking errors, just need to know
> if I need to waste time on an autoconf test for it.
My experience has been that supporting a standard
Roger Leigh writes:
> If we every wanted to drop the Autotools to only have one system to
> maintain, this would provide compatibility with a traditional
> configure/make/make install workflow. I'm not suggesting doing this at this
> point in time, just wanted to mention the existence of this so
Hi Scott,
Cantor, Scott writes:
> If anybody who knows the DOM impl could weigh in on what the heck that
> code in DOMCasts.hpp/cpp was doing and why, I'd welcome the perspective.
Yeah, infamous Xerces-C++ brain-death ;-)
Try to replace this (and if it works other similar) function with:
temp
Hi All,
Cantor, Scott writes:
> So I'm inclined to do the very ugly work of figuring out what's
> missing from the trunk and reviewing all the additional work
> there that was done before the project went into moribundity,
> and try and get a 3.2 out the door this summer.
That would be great.
+1, Thanks Scott! Unfortunately couldn't find time to test.
Boris
-
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
+1
Thanks, Scott, you are the man!
Boris
-
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
Hi Scott,
Cantor, Scott writes:
> I have one last TODO, which is to rewrite the admin/release-procedure
> file to reflect the actual process [...]
Yes, that would definitely be very helpful. I haven't done it myself
when I did the release which I regretted many, many times.
Thanks again for yo
+1
Thanks, Scott!
Boris
-
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
Hi Scott,
Cantor, Scott writes:
> I don't either, but to be blunt, the branch shouldn't be in the state it's
> in if you think it needs that much testing, because if a security issue
> pops up, you don't have the luxury of taking a lot of time.
>
> I completely understand your point about usi
Hi Scott,
Cantor, Scott writes:
> It's been years, Boris. I think you're being very aggressive here with
> somebody trying to help and able to do so only within the limits of his
> own funding and project needs. That's how this stuff works. If you're
> going to set requirements that I can't m
Hi Scott,
Cantor, Scott writes:
> I've reviewed all the resolved issues against the trunk, and backported
> 15-20 or so to the branch.
>
> Once I have access I'll commit.
Before you do this have someone review your back-ports to double
check there are no ABI breakages.
Boris
---
Hi Scott,
Cantor, Scott writes:
> I definitely don't have the cycles for a beta and it wouldn't fit my
> timeline anway.
Then you shouldn't be making the release.
> I'm on VC10 for my builds, and I believe those are already there.
What about other users of Xerces-C++? When we publish a new
Hi Scott,
Cantor, Scott writes:
> Correction, it's not an ABI change, the pool entry class isn't exported on
> Windows...
What about other platforms?! If this class is defined in a public header
(i.e., a header that is installed) and the function is virtual, then this
is an ABI change.
Boris
Hi Scott,
Cantor, Scott writes:
> FWIW, I've done very little testing of trunk other than building it,
> so I don't have a sense of how good a shape it's in or how much has
> changed.
Unless you are prepared to do a good amount of testing (I can help
somewhat but you will have to take the lead,
Hi,
I am pleased to announce the release of CodeSynthesis XSD 4.0.0.
XSD is an open source, cross-platform W3C XML Schema to C++ data
binding compiler. Provided with a schema, it generates C++ classes
that represent the given vocabulary as well as XML parsing and
serialization code. You can then
hat you also file a bug report in Jira (and attach
the test case) so that this doesn't get lost. We can then try to fix
it for the next release.
Boris
--
Boris Kolpackov, Code Synthesishttp://codesynthesis.com/~boris/blog
Compiler-based ORM system for C++ http://codesynthesis.com/
] http://www.codesynthesis.com/products/xsd
Boris
--
Boris Kolpackov, Code Synthesishttp://codesynthesis.com/~boris/blog
Compiler-based ORM system for C++ http://codesynthesis.com/products/odb
Open-source XML data binding for C++ http://codesynthesis.com/products/xsd
XML
Hi Scott,
Cantor, Scott writes:
> I'm happy to spend some time testing the build on my supported platforms
> once it's ready to go.
Yes, that would great. The more testing we can get done, the better.
> I would suggest as a way of perhaps reducing time commitment than actually
> producing bin
nd try to fix some
new bugs that have been uncovered since the 3.1.0 release. Not sure
if you would like to wait or if you want to press ahead. But your
help would be greatly appreciated.
Boris
--
Boris Kolpackov, Code Synthesishttp://codesynthesis.com/~boris/blog
Compiler-based ORM system
Sounds good to me. +1.
Boris
-
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
Hi,
shath...@e-z.net writes:
> FYI: Windows - Cygwin and MinGW
>
> These systems are deprecated.
I don't think anyone deprecated MinGW. Everything should build
fine with autotools and I see at least MinGW supported in the
future.
Boris
--
Boris Kolpackov, Code Synthes
n results for icXML in two configurations, single-
threaded and with 2 threads. Is there any documentation that
describes these extra parameters/options/etc. In other words,
how would I go about specifying the number of threads?
[1] http://www.codesynthesis.com/products/xsd/
Boris
--
shath...@e-z.net writes:
> The current xerces-c released version is 3.1.1 -- the development
> svn.a.o/xerces/c/trunk still references 3.1.0 in the following files.
The trunk will eventually become 3.2.0.
Boris
--
Boris Kolpackov, Code Synthesishttp://codesynthesis.com/~bori
[
https://issues.apache.org/jira/browse/XERCESC-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084825#comment-13084825
]
Boris Kolpackov commented on XERCESC-1971:
--
Nathaniel, Xerces-C++ 2.8.0 i
cesc_3_1::isAlias(struct HKEY__ * const,char * const,unsigned int)"
> (?isAlias@xercesc_3_1@@YA_NQAUHKEY__@@QADI@Z)
You are linking to a static version of Xerces-C++ library. All the unresolved
symbols are Registry functions. You need to link your application to
Advapi32.lib.
Boris
--
Boris
[
https://issues.apache.org/jira/browse/XERCESC-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002969#comment-13002969
]
Boris Kolpackov commented on XERCESC-1959:
--
Daniel, I agree the cur
e performs various tests and some of them
are expected to fail on some platforms. If you see no errors in
STDERR and the script existed with 0, then everything went fine.
Boris
--
Boris Kolpackov, Code Synthesishttp://codesynthesis.com/~boris/blog
Compiler-based ORM system for C++
is no "out of box" binaries is there a way to build it for
> pa-risc 32 bit.
Follow the build instructions for UNIX and add --disable-shared to the
configure command line.
Boris
--
Boris Kolpackov, Code Synthesishttp://codesynthesis.com/~boris/blog
Compiler-bas
[
https://issues.apache.org/jira/browse/XERCESC-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov updated XERCESC-1951:
-
Fix Version/s: (was: 3.1.1)
Thanks for the patch.
> Missing Libs.private in
[
https://issues.apache.org/jira/browse/XERCESC-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov updated XERCESC-1950:
-
Attachment: test.xml
> Build-in UCS4 transcoder does not respect endian
: Utilities
Affects Versions: 3.1.1
Environment: any
Reporter: Boris Kolpackov
Fix For: 3.1.2, 3.2.0
Attachments: test.xml
Built-in UCS4 transcoder does not respect endianess of the requested encoding.
Try this on the attached test file:
DOMPrint -wenc=UCS
[
https://issues.apache.org/jira/browse/XERCESC-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov updated XERCESC-1947:
-
Fix Version/s: 3.2.0
3.1.2
Ben, the reason I am interested in
[
https://issues.apache.org/jira/browse/XERCESC-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920195#action_12920195
]
Boris Kolpackov commented on XERCESC-1947:
--
Ben, is this only a proble
[
https://issues.apache.org/jira/browse/XERCESC-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov updated XERCESC-1936:
-
Fix Version/s: 3.1.2
3.2.0
4.0.0
Yes, I just
[
https://issues.apache.org/jira/browse/XERCESC-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901970#action_12901970
]
Boris Kolpackov commented on XERCESC-1451:
--
Daniel, Have you tried the la
[
https://issues.apache.org/jira/browse/XERCESC-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov updated XERCESC-1940:
-
Fix Version/s: 3.1.2
3.2.0
Thanks for the report, Anil. I am
[
https://issues.apache.org/jira/browse/XERCESC-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov updated XERCESC-1936:
-
Hi,
Can you attach the sample files to the bug report? The content that you have
pasted
n validation error). For a more detailed discussion of
this topic, see the following post:
http://www.codesynthesis.com/pipermail/xsd-users/2008-January/001443.html
Boris
--
Boris Kolpackov, Code Synthesishttp://codesynthesis.com/~boris/blog
Open-source XML data binding fo
e to a newer version of VC++. The project files that
are supported all provide static library.
Boris
--
Boris Kolpackov, Code Synthesishttp://codesynthesis.com/~boris/blog
Open-source XML data binding for C++ http://codesynthesis.com/products/xsd
XML data binding for embedded systems
: SAX/SAX2
Affects Versions: 3.1.1
Reporter: Boris Kolpackov
Fix For: 3.1.2, 3.2.0, 4.0.0
When you have something like xmlns:foo="foo", SAX2 reports the 'xmlns:foo'
attribute as belonging to the XML namespace. However, if the namespace is
declared
lidation errors are detected only
after the SAX events have been fired).
Also, the XML Schema 1.1 spec is not yet a recommendation. I am not
very familiar with the W3 process, but isn't it still a moving target?
Boris
--
Boris Kolpackov, Code Synthesishttp://codesynthesis.com/~boris/b
Versions: 3.1.1
Reporter: Boris Kolpackov
Fix For: 3.1.2, 3.2.0
There are three ways to represent Windows network share paths in URI that are
in use today:
file://host/path
file:host/path
file:/host/path
Xerces-C++ only supports the later two. The first encoding
[
https://issues.apache.org/jira/browse/XERCESC-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov closed XERCESC-1930.
Resolution: Invalid
> CRLF is replaced by sp
1 - 100 of 938 matches
Mail list logo
