+1
On 22/04/2019 17:27, Boris Kolpackov wrote:
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 unsubscr
+1
On 26/02/2018 01:04, Cantor, Scott wrote:
I'd like to request a vote to release Xerces-C 3.2.1 based on the RC4 artifact
posted last week [1].
Please respond by mid-week.
This is my +1.
-- Scott
[1] https://dist.apache.org/repos/dist/dev/xerces/c/3/sources/
---
+1 - thank you!
On 18/03/2015 17:43, Santosh Kalsangrah wrote:
+1
Thanks,
Santosh K
-Original Message-
From: Boris Kolpackov [mailto:bo...@codesynthesis.com]
Sent: Wednesday, March 18, 2015 9:25 PM
To: c-us...@xerces.apache.org; priv...@xerces.apache.org;
c-dev@xerces.apache.org
Subje
I didn't review the patch, but Rob's summary of the changes seems
correct from my knowledge of the XML 5th edition changes. Basically the
XML 1.1 name chars are now the XML 5th edition name chars.
John
On 02/05/13 06:23, Gareth Reakes wrote:
Hey Rob,
Thats great. I am not knowledgeab
Hi Rob,
I've been following the development of Parabix for a number of years,
and I'm excited that you're considering releasing it under the Apache
Licence.
I contribute to an XQuery library called XQilla that is based on top of
Xerces-C. It would be interesting to see if I could get XQilla
I was inclined to add a getEncoding method to
BinInputStream.
Alberto
Il 13/06/2011 12:04, John Snelson ha scritto:
Hi Alby,
I added BinInputStream::getContentType() some time ago so that I could
accomplish this kind of thing in XQilla. My guess is that you can build
Xerces-C stream encoding support on t
Hi Alby,
I added BinInputStream::getContentType() some time ago so that I could
accomplish this kind of thing in XQilla. My guess is that you can build
Xerces-C stream encoding support on top of this. InputSource currently
has a getEncoding() method, but the HTTP call hasn't been made by this
changed to this one, so that I can log into JIRA again and take a
proper look at resolving this bug?
Thanks,
John Snelson
On 17 Apr 2011, at 23:03, Eric Swalens (JIRA) wrote:
>
> [
> https://issues.apache.org/jira/browse/XERCESC-1963?page=com.atlassian.jira.plugin.system.iss
to make sure they work for this release and to continue actively
maintaining them for future releases.
Here is my +1 for the rc1.
Boris
--
John Snelson, Oracle Corporationhttp://snelson.org.uk/john
Berkeley DB XML:http://oracle.com/database/berkeley-db/xml
XQilla
OM-Level-2-Core/core.html#Core-Document-importNode
If someone can verify that I'm correct, I'm happy to go ahead and create
a fix for this.
John
--
John Snelson, Oracle Corporationhttp://snelson.org.uk/john
Berkeley DB XML:http://oracle.com/database/be
areth
--
Gareth Reakes, CTO WE7 - Great Music, Free
+44-20-7117-0809http://www.we7.com
<http://www.we7.com/>
--
John Snelson, Oracle Corporationhttp://snelson.org.uk/john
Berkeley DB XML:http://oracle.com/database/berkeley-db
[
https://issues.apache.org/jira/browse/XERCESC-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693738#action_12693738
]
John Snelson commented on XERCESC-1858:
---
I did test with a zero length string
[
https://issues.apache.org/jira/browse/XERCESC-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12690126#action_12690126
]
John Snelson commented on XERCESC-1858:
---
David - I think we just stepped on
[
https://issues.apache.org/jira/browse/XERCESC-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Snelson reassigned XERCESC-1858:
-
Assignee: John Snelson
> Using TranscodeToStr with strings shorter than two charact
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
--
John Snelson, Oracle Corporationhttp://snelson.org.uk/john
Berkeley DB XML:http://oracle.com/database/berkele
#x27;xerces-3.0' branch.
My +1.
Boris
--
John Snelson, Oracle Corporationhttp://snelson.org.uk/john
Berkeley DB XML:http://oracle.com/database/berkeley-db/xml
XQilla: http://xq
Boris Kolpackov wrote:
John Snelson writes:
I propose that we change XMLMutex to store the MemoryManager it was
created with, and use that in it's destructor to release it's mutex.
Yes, that sounds like the right thing to do. If you are making the
change, can you commit it to both
Mutex to store the MemoryManager it was
created with, and use that in it's destructor to release it's mutex.
Any opinions?
John
--
John Snelson, Oracle Corporationhttp://snelson.org.uk/john
Berkeley DB XML:http://oracle.com/database/berkele
w.we7.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
John Snelson, Oracle Corporationhttp://snelson.org.uk/john
Berkeley DB XML:http://oracl
[
https://issues.apache.org/jira/browse/XERCESC-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Snelson resolved XERCESC-1829.
---
Resolution: Fixed
I've just got my commit access, so I've committed the fix fo
[
https://issues.apache.org/jira/browse/XERCESC-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Snelson closed XERCESC-1829.
-
> Buffer overrun in TranscodeFromStr
> --
>
>
[
https://issues.apache.org/jira/browse/XERCESC-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Snelson reassigned XERCESC-1829:
-
Assignee: John Snelson
> Buffer overrun in TranscodeFrom
[
https://issues.apache.org/jira/browse/XERCESC-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Snelson updated XERCESC-1829:
--
Attachment: transcode_patch
A patch for the bug.
> Buffer overrun in TranscodeFrom
: 3.0.0
Reporter: John Snelson
Fix For: 3.0.0
Attachments: transcode_patch
I've just found a buffer overrun bug in the TranscodeFromStr class I added
recently.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment t
+1
Thanks for all your work, Boris.
Gareth Reakes wrote:
Hey guys,
Boris has been doing a lot of good work first as a contributor and,
for some time now, as a committer. I would like to propose that we ask
Boris to join the PMC to recognise this work.
+1
Gareth
--
John Snelson
[
https://issues.apache.org/jira/browse/XERCESC-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Snelson updated XERCESC-1816:
--
Attachment: regex_patch2
Further testing revealed a newly introduced bug in case-insensitive
[
https://issues.apache.org/jira/browse/XERCESC-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Snelson updated XERCESC-1816:
--
Attachment: (was: regex_patch)
> Multi-character escape classes don't work corr
[
https://issues.apache.org/jira/browse/XERCESC-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Snelson updated XERCESC-1816:
--
Attachment: regex_patch
Same again, but with the correct patch now :-)
> Multi-charac
[
https://issues.apache.org/jira/browse/XERCESC-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Snelson updated XERCESC-1816:
--
Attachment: (was: regex_patch)
> Multi-character escape classes don't work corr
[
https://issues.apache.org/jira/browse/XERCESC-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Snelson updated XERCESC-1816:
--
Attachment: regex_patch
This patch implements XPath 2.0 / XQuery regular expression
which compiles with
Xerces-C 3.0 beta?
I'm working on a project which has/will have dependencies on Xerces-C
3.0, but
I would like to start using the full XPath feature of XQilla.
Regards and thank you very much.
= Jatayu
On Mon, Jul 7, 2008 at 11:04 AM, John Snelson <[EMAIL PROTECTED]
&
[
https://issues.apache.org/jira/browse/XERCESC-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613690#action_12613690
]
John Snelson commented on XERCESC-1816:
---
I agree - I'd be in favour of
[
https://issues.apache.org/jira/browse/XERCESC-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613584#action_12613584
]
John Snelson commented on XERCESC-1816:
---
Maybe mistakenly, I was under
ces-C++
Issue Type: Bug
Components: Validating Parser (XML Schema)
Affects Versions: 2.8.0, 3.0.0
Reporter: John Snelson
The regular expressions "\i", "\I", "\c" and "\C" do not work as specified in
the XML Schema specifi
[
https://issues.apache.org/jira/browse/XERCESC-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Snelson updated XERCESC-1805:
--
Attachment: curl_and_local_code_page_patch
This patch fixes CurlURLInputStream
Hi everyone,
I thought it might interest you that I've now got the current SVN
version of XQilla compiling against the current SVN version of Xerces-C
3.0. All the XQilla tests pass, so everything looks good from my
perspective.
John
--
John Snelson, Oracle Corporation
[
https://issues.apache.org/jira/browse/XERCESC-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606799#action_12606799
]
John Snelson commented on XERCESC-1805:
---
Hi Boris,
The getContentType() me
) is const and returns non-
> const node). Are there any problems with returning non-const node?
I think returning a non-const node would be fine.
John
--
John Snelson, Oracle Corporationhttp://snelson.org.uk/john
Berkel
[
https://issues.apache.org/jira/browse/XERCESC-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Snelson closed XERCESC-1803.
-
Thanks Boris.
> Bug fixes and improvements for RegularExpression cl
[
https://issues.apache.org/jira/browse/XERCESC-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606334#action_12606334
]
John Snelson commented on XERCESC-1805:
---
Hi Boris,
I believe there are
[
https://issues.apache.org/jira/browse/XERCESC-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604514#action_12604514
]
John Snelson commented on XERCESC-1809:
---
Hi Boris,
This definitely looks li
[
https://issues.apache.org/jira/browse/XERCESC-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Snelson updated XERCESC-1805:
--
Attachment: xercesc_3_0_content_type_patch
This patch implements the BinInputStream
: 3.0.0
Reporter: John Snelson
Fix For: 3.0.0
A lot of algorithms need access to the HTTP "Content-Type" header, to decide
how to parse a file, or what encoding it is in - for instance see XSLT 2.0's
unparsed-text() function:
http://www.w3.org/TR/xslt20/#un
[
https://issues.apache.org/jira/browse/XERCESC-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Snelson closed XERCESC-1802.
-
Thanks Alby
> Improvements to the DOM 3 XPath
[
https://issues.apache.org/jira/browse/XERCESC-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Snelson updated XERCESC-1803:
--
Attachment: xercesc_3_0_regex_patch
This patch makes the RegularExpression class thread-safe
Components: Miscellaneous
Affects Versions: 3.0.0
Reporter: John Snelson
Fix For: 3.0.0
RegularExpression is not thread safe or consistent with it's use of
MemoryManager. It's also not quite flexible enough to implement XSLT 2.0's
analyze-string, and it
[
https://issues.apache.org/jira/browse/XERCESC-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Snelson updated XERCESC-1802:
--
Attachment: xpath_api_patch
A patch that makes these changes against Xerces-C 3.0.0
: 3.0.0
Reporter: John Snelson
Fix For: 3.0.0
Attachments: xpath_api_patch
The DOM 3 XPath API can be improved by adding some useful methods to the API:
DOMXPathNSResolver::addNamespaceBinding()
DOMXPathNSResolver::release()
and by modifying DOMDocument
Boris Kolpackov wrote:
John Snelson <[EMAIL PROTECTED]> writes:
5) Problem:
RegularExpression is not thread safe or consistent with it's use of
MemoryManager. It's also not quite flexible enough to implement XSLT
2.0's analyze-string, and it has bugs in the replace() me
Boris Kolpackov wrote:
John Snelson <[EMAIL PROTECTED]> writes:
5) Problem:
RegularExpression is not thread safe or consistent with it's use of
MemoryManager. It's also not quite flexible enough to implement XSLT
2.0's analyze-string, and it has bugs in the replace() me
Boris Kolpackov wrote:
John Snelson <[EMAIL PROTECTED]> writes:
I'm not so sure about that. The existing DOMXPathResult is an
implementation of a W3C published DOM interface, and I think there's
value in keeping it that way. There's all sorts of improvements I'
Boris Kolpackov wrote:
John Snelson <[EMAIL PROTECTED]> writes:
I've also changed my mind (again) about the DOMXPathResult object. The
problem is this - DOMXPathResult::iterateNext() returns DOMNode, because
in XPath 1 you can only get single values of a list of nodes. XQilla
John Snelson wrote:
Boris Kolpackov wrote:
Having given it some thought, I think that merging the two would be the
best idea - it would be a breaking change for XQilla users, but it would
be a move to a more standard API.
Agree. If you can come up with a patch, I will review and commit it
patch against the SVN trunk for the XPath API changes
we've discussed.
John
--
John Snelson, Oracle Corporationhttp://snelson.org.uk/john
Berkeley DB XML:http://oracle.com/database/berkeley-db/xml
XQilla: http://xqilla.sourceforge
guys just trust that I've done what
I said I'll do, or does someone need to check up on me? :-)
John
Gareth Reakes wrote:
Have you got Oracle to sign a CCLA? For good measure you could sign an
ICLA as well.
Gareth
John Snelson wrote:
John Snelson wrote:
I've got permission
John Snelson wrote:
I've got permission now - hurrah! In the next couple of days when I find
some time I'll port the patches over to Xerces-C 3.0.
So as I said, Oracle have OKed me to contribute code to Xerces-C. To
pre-empt any delays, what steps should I take to make sure that you
Boris Kolpackov wrote:
Otherwise, I'm happy with the string pool syncing work-around.
Yes, I think this is the easiest fix for the time being (I've
already sent a patch to xqilla-users).
This seems like the best fix for the moment. I'll commit it soon.
John
--
John
DOMXPathExpression - I think that I can
remove the copying if we agree that DOMXPathExpression should not be
thread-safe.
Otherwise, I'm happy with the string pool syncing work-around.
John
Boris Kolpackov wrote:
Hi John,
John Snelson <[EMAIL PROTECTED]> writes:
I realise I'm proba
ed
sample code, XML and XSD that will reproduce the problem.
I realise I'm probably doing things that most people won't ever need to
do with Xerces-C. Never-the-less is what I'm trying to do valid, and if
so is the IllegalArgumentException a bug in Xerces-C?
John
DOMXPathNSResolver (const right now).
3. Allow NULL to be passed to createNSResolver() in which case
empty DOMXPathNSResolver will be created (can then be populated
with setNamespacePrefix).
Let me know what you think.
Boris
--
John Snelson, Oracle Corporationhttp://snelson.org.uk
Boris Kolpackov wrote:
Hi John, Gareth,
John Snelson <[EMAIL PROTECTED]> writes:
It was off some draft note. Some conversation and the note is here:
http://lists.w3.org/Archives/Public/www-dom/2003JulSep/0125.html
Now I look at that link I remember reading it before. That leaves me a
just thinking about that - I think that would be the best way to
go. I took a look at what would be needed a while back and I don't think
it's much. Have you got a list of the Xerces-C API changes in 3.0 anywhere?
John
--
John Snelson, Oracle Corporationhttp://snelson.org.uk/j
/Public/www-dom/2003JulSep/0125.html
Now I look at that link I remember reading it before. That leaves me a
little uncertain about what to do. Maybe we should add DOMXPathResult2
to Xerces-C based on this note - any opinions?
John
--
John Snelson, Oracle Corporationhttp://snelson.org.u
Hi Boris,
Boris Kolpackov wrote:
John Snelson <[EMAIL PROTECTED]> writes:
1) Problem:
XPath 2.0 is just different to XPath 1.0. We've therefore got our own
version of DOMXPathResult (XPath2Result) which makes more sense in this
context:
http://xqilla.sourceforge.net/do
the XMLGrammarPool it is created with is locked.
Solution:
We hack this at the moment, but it would be great if this could be fixed.
--
John Snelson, Oracle Corporationhttp://snelson.org.uk/john
Berkeley DB XML:http://o
Kolpackov wrote:
Hi John,
John Snelson <[EMAIL PROTECTED]> writes:
why doesn't the illegal syntax (*:car) give an error in Xerces-C
I am not sure about this. Perhaps Xerces-C++ implements more than
is required by the spec (it should be quite easy to support the
namespace wildcards).
Components: Validating Parser (XML Schema)
Affects Versions: 2.8.0, 3.0.0
Reporter: John Snelson
Fix For: 3.0.0, 2.9.0
Attachments: foo.xml, foo.xsd
Both XPath and XML Schema forbid the use of * to designate a wildcard namespace:
http://www.w3.org/TR
[
https://issues.apache.org/jira/browse/XERCESC-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Snelson updated XERCESC-1787:
--
Attachment: foo.xml
XML instance document
> Wildcard namespace prefixes in XPath are
[
https://issues.apache.org/jira/browse/XERCESC-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Snelson updated XERCESC-1787:
--
Attachment: foo.xsd
XML Schema file
> Wildcard namespace prefixes in XPath are not repor
[
https://issues.apache.org/jira/browse/XERCESC-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576148#action_12576148
]
John Snelson commented on XERCESC-1393:
---
I am coming up against this proble
Hi Dave,
Thanks for your analysis. So I guess I have two questions - why doesn't
the illegal syntax (*:car) give an error in Xerces-C, and why don't the
legal syntaxes (below) work?
David Bertoni wrote:
John Snelson wrote:
1)
Xerces-C 2.8: Valid
Xerces-C
ndled correctly, and
a separate problem with not checking unique constraints correctly.
Can anyone comment on what might be going on here?
John
--
John Snelson, Oracle Corporationhttp://snelson.org.uk/john
Berkeley DB XML:http://www.oracle.com/database/berkeley-db/xml
XQill
WE7
+44-20-7117-0809http://www.we7.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
John Snelson, Oracle Corporationhttp://snelson.org.uk/john
Ber
pache until I change parsers anyway.
Do any Mac maintainers know anything about the feasibility or extent of the
changes?
-- Scott
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
: Validating Parser (Schema) (Xerces 1.5 or up only)
Affects Versions: 2.7.0
Reporter: John Snelson
We are seeing a Unique Particle Attribution violation error occur on a schema
which I am sure shouldn't have this problem. The error is:
Parse error in document at line, 1, cha
75 matches
Mail list logo
