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: [email protected]
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:[EMAIL PROTECTED]
Sent: Wednesday, August 20, 2008 2:42 AM
To: [email protected]
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


"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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


"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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to