[jira] Commented: (XERCESC-1910) The RegularExpression 'matches' function no longer returns the start and end position of a match

2010-02-11 Thread Boris Kolpackov (JIRA)

[ 
https://issues.apache.org/jira/browse/XERCESC-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12832466#action_12832466
 ] 

Boris Kolpackov commented on XERCESC-1910:
--

Steve, do I understand you correctly in that you are saying that certain 
functionality (that you used to rely on) has been removed between the two 
version as opposed to that there is a bug that affects the current version?

 The RegularExpression 'matches' function no longer returns the start and end 
 position of a match
 

 Key: XERCESC-1910
 URL: https://issues.apache.org/jira/browse/XERCESC-1910
 Project: Xerces-C++
  Issue Type: Bug
  Components: Utilities
Affects Versions: 3.0.1
 Environment: Windows
Reporter: Steve Roberts

 We have recently upgraded from version 2.2.0 to version 3.0.1. Between these 
 versions a change was made to the RegularExpression::matchUnion function, so 
 that it now uses a local version of the context structure. The result of this 
 is that the 'fMatch' member of the context can be changed from its original 
 instance. Therefore, back in the RegularExpression::matches function, just 
 before it returns, it sets the start and end position of the match:
 context.fMatch-setStartPos(0, (int)matchStart);
 context.fMatch-setEndPos(0, matchEnd);
 However, the 'fMatch' object no longer matches the one that was passed 
 through to function (due to what happened in 'matchUnion') and therefore 
 these values don't get returned to the calling function.
 Therefore, I think that in the 'matches' function is should actually be 
 setting the start and end position of the 'pMatch' property that is passed 
 into the function, rather than the 'context.fMatch'.
 The code we are using to call the regular expression is this:
   XERCES_CPP_NAMESPACE::RegularExpression re(expression.c_str());
   if( re.matches( text, match ) )
   { ...
 where expression = ([\-\(]?\d{1,3}([, 
 ]\d{3})+\.\d+[\)]?|[\-\(]?\d+\.\d+[\)]?).*
 and text = 13.13

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org



[jira] Closed: (XERCESC-1908) Xerces-c SAX application crashed on Solaris 10 x64

2010-02-11 Thread Boris Kolpackov (JIRA)

 [ 
https://issues.apache.org/jira/browse/XERCESC-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Boris Kolpackov closed XERCESC-1908.


Resolution: Invalid

I am assuming this is a toolchain problem and closing this issue. If there is 
new information pointing to Xerces-C++, please reopen it.

 Xerces-c SAX application crashed on Solaris 10 x64
 --

 Key: XERCESC-1908
 URL: https://issues.apache.org/jira/browse/XERCESC-1908
 Project: Xerces-C++
  Issue Type: Bug
  Components: SAX/SAX2
Affects Versions: 2.7.0, 2.8.0, 3.0.0, 3.0.1
 Environment: $uname -a
 SunOS xsol-qa1 5.10 Generic_137138-09 i86pc i386 i86pc
 $CC -V
 CC: Sun C++ 5.7 2005/01/07
Reporter: Bill Fu
 Attachments: config.tar.gz, sample test result.jpg, 
 testsax_64so.tar.gz


 This issue just happens on Solaris 10 x64. There is no problem on other 
 platforms, such as Solaris 10 x86 (32-bit), AIX (both 32 and 64), HP-UX (both 
 PA-RISC and IA64), Linux x86 etc.
 I wrote a xerces-c sax application on Solaris 10 x64. The class MXmlHandler 
 was the xml handler what was inherited from DefaultHandeler.
 The following is the compiler and linker flags.
 Compiler flags: -mt -xarch=amd64 -g -I/usr/app/xercesc/2.8/include 
 Linker flags: -mt -xarch=amd64 -L/usr/app/xercesc/2.8/lib -lxerces-c
 At the begining of the method
   void startElement(  const   XMLCh* consturi,
   const   XMLCh* constlocalname,
   const   XMLCh* constqname,
   const   Attributes attributes);
 the value of the parameter qname was wrong. For example the qname should be 
 a string like schemaName, but it was a recognised string. This is the 
 behavior in RELEASE libraries. In the DEBUG mode, the application crashed in 
 xerces-c libraries.
 The following is traceback.
 =[1] xercesc_2_8::XMLAttr::getValue(this = 0x18), line 486 in XMLAttr.hpp
   [2] xercesc_2_8::VecAttrListImpl::getValue(this = 0x4cc3e8, index = 1U), 
 line 86 in VecAttrListImpl.cpp
   [3] 0xfd7ffeab6546(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd7ffeab6545
   [4] xercesc_2_8::SAXParser::startElement(this = 0x4cc3a8, elemDecl = CLASS, 
 elemURLId = 1U, elemPrefix = 0xfd7ffe1bb3b0, attrList = CLASS, attrCount 
 = 2U, isEmpty = false, isRoot = true), line 971 in SAXParser.cpp
   [5] xercesc_2_8::IGXMLScanner::scanStartTag(this = 0x4cd6b8, gotData = 
 true), line 2101 in IGXMLScanner.cpp
   [6] xercesc_2_8::IGXMLScanner::scanContent(this = 0x4cd6b8), line 899 in 
 IGXMLScanner.cpp
   [7] xercesc_2_8::IGXMLScanner::scanDocument(this = 0x4cd6b8, src = CLASS), 
 line 215 in IGXMLScanner.cpp
   [8] xercesc_2_8::XMLScanner::scanDocument(this = 0x4cd6b8, systemId = 
 0x4d4530), line 460 in XMLScanner.cpp
   [9] xercesc_2_8::XMLScanner::scanDocument(this = 0x4cd6b8, systemId = 
 0x4c7f68 ../dats/adr3xml.dat), line 468 in XMLScanner.cpp
   [10] xercesc_2_8::SAXParser::parse(this = 0x4cc3a8, systemId = 0x4c7f68 
 ../dats/adr3xml.dat), line 587 in SAXParser.cpp

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org



Re: Xerces C++ 2.7.0 code and installation instructions

2010-02-11 Thread Alberto Massari
Archives can be found at 
http://archive.apache.org/dist/xml/xerces-c/Xerces-C_2_7_0/


Alberto

On 2/8/2010 8:04 AM, Atul Parti wrote:

Hi All,

I am looking for a site which can give me old source / binary for
Xerces 2.7.0.
Also guide us how to compile it and install it.
I am able to find 2.8.0 as well as 3.1.0.
For my case 3.1.0 does not worked with my code.
So need previous.

Regards
Atul



-
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org



[jira] Updated: (XERCESC-1911) spelling fixes for xerces

2010-02-11 Thread timeless (JIRA)

 [ 
https://issues.apache.org/jira/browse/XERCESC-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

timeless updated XERCESC-1911:
--

Attachment: 12456044

patch is against https://svn.apache.org/repos/asf/xerces/c/trunk/src/xercesc

 spelling fixes for xerces
 -

 Key: XERCESC-1911
 URL: https://issues.apache.org/jira/browse/XERCESC-1911
 Project: Xerces-C++
  Issue Type: Bug
Reporter: timeless
Priority: Trivial
 Attachments: 12456044


 I was running a spelling fix process against a Symbian repository and 
 discovered that a portion of the changes was to Xerces, so I'm trying to 
 deliver the spelling fixes here.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org