You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by Paparayudu Pasumarthi <Pa...@aricent.com> on 2008/08/20 05:35:44 UTC
xerces porting on vxworks
Hi,
If anybody knows the procedure to port the xerces on vxworks, please tell me the procedure.
It would be great if you provide your valuable inputs.
Thanks,
Regards
Rayudu Pasumarthi
-----Original Message-----
From: David Bertoni [mailto:dbertoni@apache.org]
Sent: Wednesday, August 20, 2008 2:42 AM
To: c-dev@xerces.apache.org
Subject: Re: SAX retrieval of filename and line number within callbacks?
Barry, Gregory P. wrote:
> Hi,
>
> Is there a way to get the current filename and line number from within
> the start element callback (or any of the callbacks for that matter)
> i.e. is there a global value or can this be retrieved from an attribute
> method. I looked through some of the SAX examples but could not find if
> filename and line number are avail from the start element callback.
Yes. You will need to override the setDocumentLocator() member function
in ContentHandler or DocumentHandler. The parser will call that
function with a Locator instance, which you need to save. When you want
information about the entity, you can call the member functions of the
Locator class using the instance the parser supplied.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility forloss or damage arising from the use of the information transmitted by this email including damage from virus."
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
RE: xerces porting on vxworks
Posted by ma...@ni.com.
Hi Rayudu,
As it happens, I have just tried to port xerces to vxworks. But it proved
not an easy job. First of all, vxworks kernel has little or no wide
character support, so you need to implement the transcoding functions.
Secondly, the memory footprint of xerces on vxworks is a kind of large(in
my case, it is about 2.8MB), which may be too large if your target has
small memory.
Best Regards!
Mao Li (李茂) | Tel:86.21.50509810 ext.3167
SAST Group,
National Instruments
"Jesse Pelton" <js...@PKC.com>
08/20/2008 08:57 PM
Please respond to
c-dev@xerces.apache.org
To
<c-...@xerces.apache.org>
cc
Subject
RE: xerces porting on vxworks
If you're referring to Bob Vaughn's instructions from 2001,
(http://mail-archives.apache.org/mod_mbox/xerces-c-dev/200104.mbox/%3C7C
78B8615661D311B15500A0C9AB28C1055087@earth.telestream.net%3E), bear in
mind that Xerces, compilers, and presumably VXWorks have evolved a good
deal in the last seven years. There hasn't been a lot of VXWorks
traffic on this list, so you may have some work to do on you own. (But
maybe someone with more recent experience will chime in and save you
some effort. Some people seem to have versions as recent as 2.7.0
working; see, for example,
http://www.nabble.com/Problem-with-XercesDOMParser-td16805706.html.)
Some people on the comp.os.vxworks newsgroup recommend considering other
parsers like expat, libxml, and purpose-built parsers:
http://groups.google.com/group/comp.os.vxworks/browse_thread/thread/1ccc
9d60720e40a8.
If you haven't already tried a Google search for "xerces vxworks", I
highly recommend it.
-----Original Message-----
From: Paparayudu Pasumarthi [mailto:Paparayudu.Pasumarthi@aricent.com]
Sent: Wednesday, August 20, 2008 1:38 AM
To: c-dev@xerces.apache.org
Subject: xerces porting on vxworks
Hi,
Its very urgent,
I have followed the steps which are available in the mail archives.
But, its not successful.
Anybody can help on this porting.
Regards
Rayudu Pasumarthi
Software Engineer - Products
A R I C E N T
# 082 4th Floor, Gamma Block,
Sigma Soft Tech Park,
Whitefield Main Road,
Varthur Post,
Bangalore -560066
India
Office Extn: +91 080 41067587
Fax: +91 080 41069500
Mobile: +91 9901351456
-----Original Message-----
From: Paparayudu Pasumarthi
Sent: Wednesday, August 20, 2008 9:06 AM
To: c-dev@xerces.apache.org
Subject: xerces porting on vxworks
Hi,
If anybody knows the procedure to port the xerces on vxworks, please
tell me the procedure.
It would be great if you provide your valuable inputs.
Thanks,
Regards
Rayudu Pasumarthi
-----Original Message-----
From: David Bertoni [mailto:dbertoni@apache.org]
Sent: Wednesday, August 20, 2008 2:42 AM
To: c-dev@xerces.apache.org
Subject: Re: SAX retrieval of filename and line number within callbacks?
Barry, Gregory P. wrote:
> Hi,
>
> Is there a way to get the current filename and line number from within
> the start element callback (or any of the callbacks for that matter)
> i.e. is there a global value or can this be retrieved from an
attribute
> method. I looked through some of the SAX examples but could not find
if
> filename and line number are avail from the start element callback.
Yes. You will need to override the setDocumentLocator() member function
in ContentHandler or DocumentHandler. The parser will call that
function with a Locator instance, which you need to save. When you want
information about the entity, you can call the member functions of the
Locator class using the instance the parser supplied.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
"DISCLAIMER: This message is proprietary to Aricent and is intended
solely for the use of the individual to whom it is addressed. It may
contain privileged or confidential information and should not be
circulated or used for any purpose other than for what it is intended.
If you have received this message in error,please notify the originator
immediately. If you are not the intended recipient, you are notified
that you are strictly prohibited from using, copying, altering, or
disclosing the contents of this message. Aricent accepts no
responsibility forloss or damage arising from the use of the information
transmitted by this email including damage from virus."
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
"DISCLAIMER: This message is proprietary to Aricent and is intended
solely for the use of the individual to whom it is addressed. It may
contain privileged or confidential information and should not be
circulated or used for any purpose other than for what it is intended.
If you have received this message in error,please notify the originator
immediately. If you are not the intended recipient, you are notified
that you are strictly prohibited from using, copying, altering, or
disclosing the contents of this message. Aricent accepts no
responsibility forloss or damage arising from the use of the information
transmitted by this email including damage from virus."
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
RE: xerces porting on vxworks
Posted by Jesse Pelton <js...@PKC.com>.
If you're referring to Bob Vaughn's instructions from 2001,
(http://mail-archives.apache.org/mod_mbox/xerces-c-dev/200104.mbox/%3C7C
78B8615661D311B15500A0C9AB28C1055087@earth.telestream.net%3E), bear in
mind that Xerces, compilers, and presumably VXWorks have evolved a good
deal in the last seven years. There hasn't been a lot of VXWorks
traffic on this list, so you may have some work to do on you own. (But
maybe someone with more recent experience will chime in and save you
some effort. Some people seem to have versions as recent as 2.7.0
working; see, for example,
http://www.nabble.com/Problem-with-XercesDOMParser-td16805706.html.)
Some people on the comp.os.vxworks newsgroup recommend considering other
parsers like expat, libxml, and purpose-built parsers:
http://groups.google.com/group/comp.os.vxworks/browse_thread/thread/1ccc
9d60720e40a8.
If you haven't already tried a Google search for "xerces vxworks", I
highly recommend it.
-----Original Message-----
From: Paparayudu Pasumarthi [mailto:Paparayudu.Pasumarthi@aricent.com]
Sent: Wednesday, August 20, 2008 1:38 AM
To: c-dev@xerces.apache.org
Subject: xerces porting on vxworks
Hi,
Its very urgent,
I have followed the steps which are available in the mail archives.
But, its not successful.
Anybody can help on this porting.
Regards
Rayudu Pasumarthi
Software Engineer - Products
A R I C E N T
# 082 4th Floor, Gamma Block,
Sigma Soft Tech Park,
Whitefield Main Road,
Varthur Post,
Bangalore -560066
India
Office Extn: +91 080 41067587
Fax: +91 080 41069500
Mobile: +91 9901351456
-----Original Message-----
From: Paparayudu Pasumarthi
Sent: Wednesday, August 20, 2008 9:06 AM
To: c-dev@xerces.apache.org
Subject: xerces porting on vxworks
Hi,
If anybody knows the procedure to port the xerces on vxworks, please
tell me the procedure.
It would be great if you provide your valuable inputs.
Thanks,
Regards
Rayudu Pasumarthi
-----Original Message-----
From: David Bertoni [mailto:dbertoni@apache.org]
Sent: Wednesday, August 20, 2008 2:42 AM
To: c-dev@xerces.apache.org
Subject: Re: SAX retrieval of filename and line number within callbacks?
Barry, Gregory P. wrote:
> Hi,
>
> Is there a way to get the current filename and line number from within
> the start element callback (or any of the callbacks for that matter)
> i.e. is there a global value or can this be retrieved from an
attribute
> method. I looked through some of the SAX examples but could not find
if
> filename and line number are avail from the start element callback.
Yes. You will need to override the setDocumentLocator() member function
in ContentHandler or DocumentHandler. The parser will call that
function with a Locator instance, which you need to save. When you want
information about the entity, you can call the member functions of the
Locator class using the instance the parser supplied.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
"DISCLAIMER: This message is proprietary to Aricent and is intended
solely for the use of the individual to whom it is addressed. It may
contain privileged or confidential information and should not be
circulated or used for any purpose other than for what it is intended.
If you have received this message in error,please notify the originator
immediately. If you are not the intended recipient, you are notified
that you are strictly prohibited from using, copying, altering, or
disclosing the contents of this message. Aricent accepts no
responsibility forloss or damage arising from the use of the information
transmitted by this email including damage from virus."
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
"DISCLAIMER: This message is proprietary to Aricent and is intended
solely for the use of the individual to whom it is addressed. It may
contain privileged or confidential information and should not be
circulated or used for any purpose other than for what it is intended.
If you have received this message in error,please notify the originator
immediately. If you are not the intended recipient, you are notified
that you are strictly prohibited from using, copying, altering, or
disclosing the contents of this message. Aricent accepts no
responsibility forloss or damage arising from the use of the information
transmitted by this email including damage from virus."
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
xerces porting on vxworks
Posted by Paparayudu Pasumarthi <Pa...@aricent.com>.
Hi,
Its very urgent,
I have followed the steps which are available in the mail archives.
But, its not successful.
Anybody can help on this porting.
Regards
Rayudu Pasumarthi
Software Engineer - Products
A R I C E N T
# 082 4th Floor, Gamma Block,
Sigma Soft Tech Park,
Whitefield Main Road,
Varthur Post,
Bangalore -560066
India
Office Extn: +91 080 41067587
Fax: +91 080 41069500
Mobile: +91 9901351456
-----Original Message-----
From: Paparayudu Pasumarthi
Sent: Wednesday, August 20, 2008 9:06 AM
To: c-dev@xerces.apache.org
Subject: xerces porting on vxworks
Hi,
If anybody knows the procedure to port the xerces on vxworks, please tell me the procedure.
It would be great if you provide your valuable inputs.
Thanks,
Regards
Rayudu Pasumarthi
-----Original Message-----
From: David Bertoni [mailto:dbertoni@apache.org]
Sent: Wednesday, August 20, 2008 2:42 AM
To: c-dev@xerces.apache.org
Subject: Re: SAX retrieval of filename and line number within callbacks?
Barry, Gregory P. wrote:
> Hi,
>
> Is there a way to get the current filename and line number from within
> the start element callback (or any of the callbacks for that matter)
> i.e. is there a global value or can this be retrieved from an attribute
> method. I looked through some of the SAX examples but could not find if
> filename and line number are avail from the start element callback.
Yes. You will need to override the setDocumentLocator() member function
in ContentHandler or DocumentHandler. The parser will call that
function with a Locator instance, which you need to save. When you want
information about the entity, you can call the member functions of the
Locator class using the instance the parser supplied.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility forloss or damage arising from the use of the information transmitted by this email including damage from virus."
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility forloss or damage arising from the use of the information transmitted by this email including damage from virus."
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org