Hi,
I tried create Xerces-C RPM package on my SuSE 9.1 box, and get error:
*Installed (but unpackaged) file(s) found* for libxerces-depdom.so.26.0
This problem can be solved by adding one line to SPEC file:
%files
%defattr(755,root,root)
%{prefix}/bin/*
%{prefix}/lib/libxerces-c.so*
%{prefix}/lib
At 09.16 05/04/2005 +0200, Lumir Vanek wrote:
Hi,
I tried create Xerces-C RPM package on my SuSE 9.1 box, and get error:
*Installed (but unpackaged) file(s) found* for libxerces-depdom.so.26.0
This problem can be solved by adding one line to SPEC file:
%files
%defattr(755,root,root)
%{prefix}/bin
[ http://issues.apache.org/jira/browse/XERCESC-1395?page=history ]
Gareth Reakes resolved XERCESC-1395:
Resolution: Invalid
resolved via discussion on mailing list.
> error "Ending delimiter missing on substitution" building on Solaris
> --
[ http://issues.apache.org/jira/browse/XERCESC-1396?page=history ]
Gareth Reakes resolved XERCESC-1396:
Resolution: Fixed
I have applied your patch. xml-xerces/c/obj/Makefile.in is not in CVS. Is this
the file you meant to patch? If not reopen
RefHashTable resize may be inefficient
--
Key: XERCESC-1398
URL: http://issues.apache.org/jira/browse/XERCESC-1398
Project: Xerces-C++
Type: Improvement
Components: Utilities
Versions: 2.6.0
Reporter: Gareth Reakes
[
http://issues.apache.org/jira/browse/XERCESC-1393?page=comments#action_62161 ]
Gareth Reakes commented on XERCESC-1393:
I completley agree. Xerces C/J should behave in the same way.
> Identity constraint is not enforced on xs:anySimpleType
>
[
http://issues.apache.org/jira/browse/XERCESC-1392?page=comments#action_62162 ]
Gareth Reakes commented on XERCESC-1392:
Hi, does this mean you think there is a bug in the default scanner? Unfortnatly
we cant use things like const_cast or the
[ http://issues.apache.org/jira/browse/XERCESC-1358?page=history ]
Gareth Reakes resolved XERCESC-1358:
Resolution: Fixed
No problem David. Will open different bug to track modulus.
> RefHashTableOf::rehash() is not exception-safe
> ---
Hi all,
I have applied the patch from Axel which makes the make output *much*
nicer. The changes seem standard
--- xml-xerces/c/src/xercesc/framework/psvi/Makefile.in 2004-09-08
18:53:11.0 +0200
+++ xml-xerces-modified/c/src/xercesc/framework/psvi/Makefile.in
2005-04-03 13:01:45.623939
[ http://issues.apache.org/jira/browse/XERCESC-1397?page=history ]
Gareth Reakes resolved XERCESC-1397:
Resolution: Fixed
Thanks for that. I have applied and will post to the list so everyone can check
the syntax works on other platforms.
> ni
Am Dienstag, 5. April 2005 11:21 schrieb Gareth Reakes:
> Hi all,
>
> I have applied the patch from Axel which makes the make output
> *much* nicer. The changes seem standard
Hi,
I'm thinking about re-structuring and simplifying the Makefiles (e.g.
putting all configure-related and *very*
[
http://issues.apache.org/jira/browse/XERCESC-1392?page=comments#action_62173 ]
Fred Dushin commented on XERCESC-1392:
--
> Hi, does this mean you think there is a bug in the default scanner?
> Unfortnatly we cant use things like const_cast or the
Hi,
I know this isn't really a developer question but there isn't a user list so I
figured this one might do
I have a very simple problem but I can't see the solution anywhere
My Xml file has a node with a character of Ascii 1 (the test file is below)
Xerces will fail to parse this
I have tried
[ http://issues.apache.org/jira/browse/XERCESC-1392?page=history ]
Fred Dushin updated XERCESC-1392:
-
Attachment: SAX2Count.SunOSv9BusError.tar
This uncompressed TAR file consists of the SAX2Count sample program, modified
to:
* Use the Well-formedness
Hey all,
As part of moving to a TLP I am going to start a blog with FAQs for
Xerces-C/J/P, as well as other information coming from the PMC. I am
starting with the FAQ for us. Are there any topics people feel should be
covered (links to mail archive would be helpful here). Also, please feel
fr
Hey all,
We have had a bug reported for 64 bit solaris and the well formed
scanner:
http://issues.apache.org/jira/browse/XERCESC-1392?page=history
Does anyone out there have access to this platform and a bit of time to
debug the problem?
Cheers,
Gareth
--
Gareth Reakes, Managing Director
If you set XML version to 1.1 these characters are legal, though you must
still escape them.
Tony Dodd
>-Original Message-
>From: Vincent Finn [mailto:[EMAIL PROTECTED]
>Sent: 05 April 2005 15:46
>To: xerces-c-dev@xml.apache.org
>Subject: control characters in the Xml
>
>Hi,
>
>I know t
[
http://issues.apache.org/jira/browse/XERCESC-1392?page=comments#action_62178 ]
Gareth Reakes commented on XERCESC-1392:
Hi, we don't use more modern casts for portability reasons. Could you attach
the code and xml you use so we can recreate t
Neither of my versions support 1.1 so I'll upgrade
Thanks, Vin
> -Original Message-
> From: Tony Dodd [mailto:[EMAIL PROTECTED]
> Sent: 05 April 2005 16:27
> To: xerces-c-dev@xml.apache.org
> Subject: RE: control characters in the Xml
>
>
> If you set XML version to 1.1 these ch
I'm attempting to build Xerces 2.6.0 on zOS (platform os390). I commend IBM
on their work. It's awesome building with gmake under USS. It's been a
decade since I've spoken SMP/E :) I don't recall getting this far with
earlier Xerces revisions either. I doubt I'm getting any smarter, after all
One clarification re IEW error messages. Notice the symbols refer to
xercesc_2_2. Our application code, running on non-zOS platforms, is
tightly coupled to Xerces 2.2. It was simply easier to set the Xerces minor
version number to 2, during the Xerces build, for testing purposes.
Apologies for
I am experiencing a crash when running validation in
multiple current threads that share the same
GrammarPool.
I pre-load the grammar pool with XSD grammars and then
create multiple threads validating document using the
shared grammar pool. It crashed 70% of the time,
apprantly due to a racing co
22 matches
Mail list logo