.
http://www.apache.org/dev/project-creation-tasks.html
It seems has a good list of thinks that we have to do. Jason, did the
infrastructure guys understand we were moving to a new PMC when they
asked for the vote results?
Cheers,
Gareth
Jason E. Stewart (JIRA) wrote:
Send CVS Migration request email
Send CVS Migration request email to [EMAIL PROTECTED]
-
Key: XERCESC-1366
URL: http://issues.apache.org/jira/browse/XERCESC-1366
Project: Xerces-C++
Type: Task
Reporter: Jason E. Stewart
Priority
--- Begin Message ---
--On Saturday, February 26, 2005 12:11 AM +0530 "Jason E. Stewart"
<[EMAIL PROTECTED]> wrote:
> Hey All,
>
> Just a ping ...
>
> I never received an answer to this. I am not on the list anymore, so
> please Cc: me in any reply.
Please file a JIRA issue under the Infrastruct
As part of planning for the next major release of xerces-c, to take
place sometime this year, I'd like to get comment on the following.
Our current plan is to drop support for Mac OS prior to Mac OS X 10.1.
This means there will be no support for Mac OS 8 or 9 systems, running
either natively o
20
PMTo: [email protected]: RE: request
help with XERCES 2.5 OVMS port - SAMPLES programs accvio accessing parent in
isKidOK; ported 2.0 works fine on OVMS
Hi,
thank-you for the information... but (sadly for
me)...
the
Jira is a request to port 2.5 to OVM
[email protected]
Subject: RE: request help with XERCES 2.5 OVMS port - SAMPLES programs
accvio accessing parent in isKidOK; ported 2.0 works fine on OVMS
At 14.20 14/02/2005 -0500, Johnson, Sarah (Basestar) wrote:
>Hi,
>thank-you for the information... but (sadly for me)...
>the Jira is a
At 14.20 14/02/2005 -0500, Johnson, Sarah (Basestar) wrote:
Hi,
thank-you for the information... but (sadly for me)...
the Jira is a request to port 2.5 to OVMS... and i'm the one that was
assigned (by HP) to do it...
as far as i know, no one else has attempted, or entered any (similar)
Hi,
thank-you for the information... but (sadly for
me)...
the
Jira is a request to port 2.5 to OVMS... and i'm the one that was assigned
(by HP) to do it...
as far
as i know, no one else has attempted, or entered any (similar) OVMS bugs... i
spent almost a whole day reading the arc
Maybe he's
already encountered and resolved this issue.
From: Johnson, Sarah (Basestar)
[mailto:[EMAIL PROTECTED] Sent: Monday, February 14, 2005 1:55
PMTo: [email protected]: request help
with XERCES 2.5 OVMS port - SAMPLES programs accvio accessing parent in
Hi,
i'm attempting to
port XERCES 2.5 to OVMS... i have a clean build, but all the sample programs
accvio in the same place... the HP compiler folks tell me the field being
accessed is compiler generated (i have no C++, XML or XERCES experience), but
they don't know what source code (const
Scott Cantor wrote:
I'm willing to take a first-pass at a new build infrastructure and
re-factoring. Following that, it's going to require testing and
(perhaps) re-porting of various platformas/architectures/compilers to
the new system. But, as I tried to explain above, this task should be
muc
> I'm willing to take a first-pass at a new build infrastructure and
> re-factoring. Following that, it's going to require testing and
> (perhaps) re-porting of various platformas/architectures/compilers to
> the new system. But, as I tried to explain above, this task should be
> much simpler (
On Feb 10, 2005, at 5:32 AM, Gareth Reakes wrote:
Neil Graham wrote:
Moving to the future is always good. I am a bit confused though
about what "old baggage" we need to shed, and just what shedding
implies. The deprecated DOM, for instance, is now built into a
separate library; folks that don'
Hey,
Neil Graham wrote:
Moving to the future is always good. I am a bit confused though about
what "old baggage" we need to shed, and just what shedding implies. The
deprecated DOM, for instance, is now built into a separate library; folks
that don't need it have no reason to deploy it. Does
Hi James,
This looks like an excellent--and ambitious--roadmap to me!
James Berry <[EMAIL PROTECTED]> wrote on 02/08/2005 09:56:00 AM:
> I agree that we should move to the future and shed old baggage.
Moving to the future is always good. I am a bit confused though about
what "old baggage" we
> 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
zed or non-normalized value depending on the datatype-normalization
feature.
Khaled
"Scott Cantor"
<[EMAIL PROTECTED]>
02/08/2005 11:45 AM
Please respond to
xerces-c-dev
To
cc
Subject
RE: Request for feedback
on some proposed xercesc changes (including breaking
> 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
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
> 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
nt: Tuesday, February 08, 2005 9:56 AM
> To: [email protected]
> Cc: Gareth Reakes
> Subject: The Road to 3.0 (was Request for feedback on some
> proposed xercesc changes)
>
> I agree that we should move to the future and shed old baggage.
>
> I propose that we c
AM
Please respond to
xerces-c-dev
To
cc
Subject
RE: Request for feedback
on some proposed xercesc changes (including breaking source code
compatibility)
> I feel we really should move to the latest version
of the spec, even if
> we don't fully implement it. It
> 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
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
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
Hi David,
At 12.18 04/02/2005 -0500, David Cargill wrote:
Hi Alberto,
Adding /Wp64 sounds fine.
I am not sure about having the next release be 3.0. I think the risk of
someone having PSVIDefs in their code is a small risk (given that we have
already removed the functionality). I agree it would b
cc
PM
Subject
Re: Request for feedback on some
Please respond to proposed xercesc changes
AM
Subject
Re: Request for feedback on some
Please respond to proposed xercesc changes
AM
Subject
Re: Request for feedback on some
Please respond to proposed xercesc changes
xerces-c-dev(including breaking
On 3 Feb 2005, at 14:10, Jesse Pelton wrote:
Makes sense to me, except for one detail: I think names specified in
standards should specifically be exempted from the proposed Mixed Case
guideline. Such names should match the casing used in the standard.
To meet this guideline without such an exempt
Message-
> From: David Cargill [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 03, 2005 5:59 AM
> To: [email protected]
> Subject: Request for feedback on some proposed xercesc
> changes (including breaking source code compatibility)
>
>
>
>
>
Hi David,
At 05.59 03/02/2005 -0500, David Cargill wrote:
Hi All,
In reviewing some recent appends and Jira bugs I would like to get some
feedback before making the following changes:
(1) Change compiler options for Linux and MSVC++ to generate more warning
messages. By regularly monitoring the re
Hey,
All sound good to me.
Gareth
On 3 Feb 2005, at 10:59, David Cargill wrote:
Hi All,
In reviewing some recent appends and Jira bugs I would like to get some
feedback before making the following changes:
(1) Change compiler options for Linux and MSVC++ to generate more
warning
message
Hi All,
In reviewing some recent appends and Jira bugs I would like to get some
feedback before making the following changes:
(1) Change compiler options for Linux and MSVC++ to generate more warning
messages. By regularly monitoring the regular builds of
xercesc we can try and have war
Hi,
I would like to be pushy about some annoying issues that have gotten
notably worse since v2.1 regarding the coding styles, conventions, and
practices, used in Xerces-C development.
I would like to request that developers of Xerces-C cease using
ALL_CAPS_NAMES for anything other than for
ure Request: additional XMLString::transcode () variant
> ---
>
> Key: XERCESC-497
> URL: http://nagoya.apache.org/jira/browse/XERCESC-497
> Project: Xerces-C++
> Type: New Feature
> Components:
[ http://nagoya.apache.org/jira/browse/XERCESC-497?page=history ]
Alberto Massari updated XERCESC-497:
Priority: Major
> Feature Request: additional XMLString::transcode () vari
On Fri, 2004-10-01 at 09:04, Dan White wrote:
> The idea is to take advantade of the SAX and its ability to process a
> stream of non-specific length and combine that with the data organization
> of DOM.
Are you saying that you need to handle an input stream containing
multiple XML documents? I ne
> The idea is to take advantade of the SAX and its ability to
> process a stream of non-specific length and combine that with
> the data organization of DOM.
I'm not sure I understand what you mean by this. Since the same
underlying scanner technology runs the SAX parsers and the DOM parsers and
The idea is to take advantade of the SAX and its ability to process a
stream of non-specific length and combine that with the data organization
of DOM.
So, I would like to be able to parse an input of any length --AND-- have
the result end up in a DOM tree for easy manipulation. I would like to d
At 11.37 30/09/2004 -0400, Dan White wrote:
OK, in reading data from a socket, you either do a "read_n" with a big
enough buffer to hold any meggase you might get or you do repeated smaller
reads until you arrive at some agreed-upon separation of message traffic.
I am currently using a DOM input pa
Hi,
I have a DOM to SAX, but not a SAX to DOM. Should not be too hard
to make something using AbstractDOMParser. Would have to take a bit more
of a look to be sure though.
Gareth
Dan White wrote:
Bump.
Anyone have a clue on this ?
On Sep 26, 2004, at 1:09 AM, Dan White wrote:
Is there a re
At 08.03 30/09/2004 -0400, Dan White wrote:
Bump.
Anyone have a clue on this ?
I don't have quite understood what is your problem: what is the connection
between "pulling a complete XML statement off the data stream", "a DOM
parser with a large input buffer" and "building a DOM out of a SAX parse
Bump.
Anyone have a clue on this ?
On Sep 26, 2004, at 1:09 AM, Dan White wrote:
Is there a reasonably simple way to build a DOM Tree with SAX events ?
I am working on a client-server that communicates by XML over a
socket. Some of the other developers are having trouble pulling a
complete XML s
Is there a reasonably simple way to build a DOM Tree with SAX events ?
I am working on a client-server that communicates by XML over a socket.
Some of the other developers are having trouble pulling a complete XML
statement off of the data stream.
I implemented a DOM Parser with a very large in
Hi,
this gets discussed between the committers at the planning for every
release :) It is a surprising amount of work. And by that, I don't even
mean implementing the features - just changing to the interfaces and
throwing not implemented exceptions for the appropriate methods. My
time over th
m: Liu, Ryan Yu Yan (Ryan)
> Sent: 2004年7月21日 13:09
> To: '[EMAIL PROTECTED]'
> Subject: Help Request: How to write --host option for configure
>
> Hi,
>
> Now I am building Xerces C++ with MontaVista Linux on RedHat Linux Platform.
> You know
Hi,
Now I am building Xerces C++ with MontaVista Linux on RedHat Linux Platform.
You know this is cross compile. When we use runConfigure script, we should use extra
configuration option -C--host=###.
That is to say: runConfigure -plinux -C--host=.
But I don't know how to write . Wou
My exception when parsing has something to do with the scope of the
parser. Not sure why since it should be global, but I'll keep
investigating.
Brian mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail:
E. Stewart" [EMAIL PROTECTED]
<[EMAIL PROTECTED]Subject: Re: [request]: migrate
Xerces-C, Xerces-J to Jira
[EMAIL PROTECTED]
04/05/2004 03:47 Subject: Re: [request]: migrate
Xerces-C, Xerces-J to Jira
L PROTECTED], [EMAIL
PROTECTED],
[EMAIL PROTECTED]
04/04/2004 05:30 Subject: Re: [request]: migrate
Xerces-C, Xerces-J to Jira
Hi infrastructure folks,
Recently, there were discussions on the Xerces-C [1] and Xerces-J [2] lists
to migrate from Bugzilla to Jira. The consensus was that this was a good
idea; we had 3 or 4 +1's from each community, with no other votes. So it
would be appreciated if someone could look i
gzilla/show_bug.cgi?id=12078
Request to add the features:
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
t by detecting whether the src
directory exists in the distribution...
-jdb
>
> Tinny
>
> - Original Message -
> From: "James Berry" <[EMAIL PROTECTED]>
> To: "Xerces C Dev" <[EMAIL PROTECTED]>
> Sent: Sunday, February 23, 2003 11:47 AM
> S
where the
directory "src" does not exist), we may need a "configure" in multiple
places...
Tinny
- Original Message -
From: "James Berry" <[EMAIL PROTECTED]>
To: "Xerces C Dev" <[EMAIL PROTECTED]>
Sent: Sunday, February 23, 2003 11:47
Hi,
I agree that something needs to be done. I have set our sys admin
on the task of replying with some constructive ideas :)
Gareth
--
Gareth Reakes, Head of Product Development +44-1865-203192
DecisionSoft Limitedhttp://www.decisionsoft.com
XML Development
After spending the evening last night in traipsing through the Xerces build
and configuration system, I have a renewed sense of purpose over what I feel
is a problem that should be addressed.
To put it (perhaps rather too) bluntly, the Xerces build and configuration
system is a tangled mess, hard
gzilla/show_bug.cgi?id=12078
Request to add the features:
--- Additional Comments From [EMAIL PROTECTED] 2003-01-29 20:07 ---
Points 1 and 2 are covered. Do you require point 3?
-
To unsubscribe, e-mail: [EMAIL PROTECTE
gzilla/show_bug.cgi?id=14960
Request to open interface
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|VERIFIED|
gzilla/show_bug.cgi?id=14960
Request to open interface
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|VE
gzilla/show_bug.cgi?id=14960
Request to open interface
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
: Gareth Reakes
To: [EMAIL PROTECTED]
Sent: 11/29/02 9:32 AM
Subject: Re: Request to open interface
Hey,
> I need to get access to all existing simple types.
> (btw. The full access to all complex types can be requested by
> RefHashTableOf* getComplexTypeRegistry() const;
> m
> Whats the bug number? Ill take a look.
12188, 12238
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hey,
> I need to get access to all existing simple types.
> (btw. The full access to all complex types can be requested by
> RefHashTableOf* getComplexTypeRegistry() const;
> method of the SchemaGrammar
> )
OK, Ill add it in.
> --
> ODMTypeInfo
>
> Will it appe
Hi Gareth,
DatatypeValidator* getDatatypeValidator(const XMLCh* const dvType) const
assumes that you know the datatype name.
I need to get access to all existing simple types.
(btw. The full access to all complex types can be requested by
RefHashTableOf* getComplexTypeRegistry() const;
met
Hi Peter,
I'm playing around quite a lot in this code at the moment for
ODMTypeInfo so I can add the code you suggest. Is the access given by
getDatatypeValidator not sufficient? What is the use case you have for
requiring this? I'm wondering as I am adding in a few bits and pieces and
gzilla/show_bug.cgi?id=14960
Request to open interface
Summary: Request to open interface
Product: Xerces-C++
Version: Nightly build (please specify the date)
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Pr
gzilla/show_bug.cgi?id=9844
Feature Request: additional XMLString::transcode () variant
--- Additional Comments From [EMAIL PROTECTED] 2002-06-13 18:36 ---
A...
maxChars says how big the destination buffer is, the buffer you supply.
The problem is that you don't know how big
gzilla/show_bug.cgi?id=9844
Feature Request: additional XMLString::transcode () variant
--- Additional Comments From [EMAIL PROTECTED] 2002-06-13 18:10 ---
Sorry, don't mean to be dense, but doesn't maxChars simply indicate 'I want you
to transcode only this many characters?
gzilla/show_bug.cgi?id=9844
Feature Request: additional XMLString::transcode () variant
--- Additional Comments From [EMAIL PROTECTED] 2002-06-13 16:32 ---
Nope. That method again can only handle null-terminated input strings, like all other
XMLString::transcode () variants (maxChar
gzilla/show_bug.cgi?id=9844
Feature Request: additional XMLString::transcode () variant
--- Additional Comments From [EMAIL PROTECTED] 2002-06-13 16:00 ---
You mean like this one:
static bool transcode
(
const XMLCh* consttoTranscode
, char* const
gzilla/show_bug.cgi?id=9844
Feature Request: additional XMLString::transcode () variant
Summary: Feature Request: additional XMLString::transcode ()
variant
Product: Xerces-C++
Version: 1.7.0
Platform: All
OS/Version: All
Hey Tinny and IBM team,
Getting Xerces-Perl to work on different architectures is a bit of a
pain, because Perl only stores configuration information for the
platforms C compiler and not the C++ compiler.
However, if someone needing Xerces-Perl has built Xerces-C from
source, I can steal all th
Hey Tinny and IBM team,
The last month or so has been a real pain in my butt for
Xerces-Perl.
The public API changed frequently, and that was mostly because of the
addition of cool new features which we all wanted to see. However it
was totally undocumented, so there was little or no way for me
gzilla/show_bug.cgi?id=3813
BinHTTPURLInputStream has weak HTTP request capabilities
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RE
gzilla/show_bug.cgi?id=3813
BinHTTPURLInputStream has weak HTTP request capabilities
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|Enhancement |
gzilla/show_bug.cgi?id=3813
BinHTTPURLInputStream has weak HTTP request capabilities
Summary: BinHTTPURLInputStream has weak HTTP request capabilities
Product: Xerces-C++
Version: 1.5.1
Platform: PC
OS/Version: Windows NT/2K
Statu
UPS! Just found the PDF file in DOC!
I'll read that first!
Thanks!
--
Fra: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Dato: Mon, 30 Jul 2001 13:39:41 +0200
Til: <[EMAIL PROTECTED]>
Emne: Installation on MacOSX 10.0.4?
Any guidelines to this?
with kind regards
Søren Rehné
---
Just applied. Would you please verify?
Thanks!
Tinny
Miroslaw Dobrzanski-Neumann wrote:
> On Sun, Jul 01, 2001 at 06:50:02AM -0700, James Berry wrote:
> > Carl,
> >
> > You've got some great suggestions...how about submitting some great patches
> > to support them? ;)
>
> A week ago I have su
On Sun, Jul 01, 2001 at 06:50:02AM -0700, James Berry wrote:
> Carl,
>
> You've got some great suggestions...how about submitting some great patches
> to support them? ;)
A week ago I have submitted a patch for dce support for aix and solaris. Could
someone apply it to the cvs source tree.
rega
James Wrote:
>Carl,
>You've got some great suggestions...how about submitting some great
patches
>to support them? ;)
>-jdb
>>On 6/30/01 7:29 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>wrote:
>> Hi, Folks.
>>
>> I'd like to
Carl,
You've got some great suggestions...how about submitting some great patches
to support them? ;)
-jdb
On 6/30/01 7:29 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> Hi, Folks.
>
> I'd like to request that support be added for more current versio
Hi, Folks.
I'd like to request that support be added for more current versions
of the platforms that Xerces-C provides.
For example, Solaris has more market share in the UNIX marketplace
than any other UNIX vendor. Yet the supported Solaris platform is
for a version of the OS that has
To: Xerces team
Source: dom/DocumentTypeImpl.hpp
Can you move the method virtual void setInternalSubset(const DOMString
&value);
to the protected area ?
Peter A. Volchek
Software Engineer
Metis International, Inc.
[EMAIL PROTECTED]
-
On Wed, May 09 2001 at 12:25:02P +1000, Krishna Gadde wrote:
> Hi All,
> I am using xerces-c to parse my xml file.using
> this i am not able to read PCDATA present between the tags.
> I tried with the following method to retrieve the data.
> DOM_Node.getNodeValue();
> Can you please suggest the
Read the DOM spec. Elements have no node value; you must examine their
children.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi All,
I am
using xerces-c to parse my xml file.using this i am not able to read PCDATA
present between the tags.
I tried with the following method to retrieve the
data.
DOM_Node.getNodeValue();
Can you please suggest the method which will be
used to read the PCDATA.
Regards
talya"
cc:
Subject: Xerces for AIX 4.3 help
request
04/25/200
> I need to link with a xerces library on AIX 4.3.4. I downloaded the
> Xalan-C_1_1-aix.tar.gz file from the web site and tried to link with
> libxerces-c1_4.a. It didn't seem to have any effect. I tried to look at
the
> contents of that file using 'ar -t' and got the following error message:
>
>
90 matches
Mail list logo
