I am using XPath functions(like substring). And it is
working for me.
But I am just thinking, whether it is faster to read and write data to the
nodeset rather than
to string. If string manipulations are faster, then I can go a head with
them only.
Thank You
Raj.
> -----Original Message-----
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, September 25, 2001 12:22 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Returning XalanNode from Extension Function. (Xalan C++)
>
>
> I'm still not sure I understand what you're trying to do, but there's no
> way that creating a node set will be cheaper than just returning a string.
> If you're just doing string manipulation, can't you use the built-in XPath
> string manipulation functions?
>
> Dave
>
>
>
>
>
> "Avula, Raj"
>
> <RAvula@firstam. To:
> "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> com> cc: (bcc: David N
> Bertoni/CAM/Lotus)
> Subject: RE: Returning
> XalanNode from Extension Function. (Xalan C++)
> 09/25/2001 02:45
>
> PM
>
> Please respond
>
> to xalan-dev
>
>
>
>
>
>
>
>
>
>
> Hi Dave,
>
> Thanks for the reply. Basically I have some codes(data) in
> the
> input
> xml.
> I have to convert them to different codes in the output. I have all the
> mapping
> information from input code to output code in C++ Structures. I am using
> extension
> to send the input codes ( I can as well use context node) in the form of
> delimited string
> and sending back the output codes in the form of delimited string to the
> xsl
> file.
>
> But I want to pass the output codes back to xsl some form
> like
> DOM_Node.
> Because, I think that the operations on Node will be much faster than with
> delimited
> string(Is that Right?). Can you please let me know, How can I pass the
> data
> back to xsl
> from the extension function in the form of DOM_Node or XalanNode or
> XNodeSet
> etc..
>
> Thanks,
> Raj.
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> [SMTP:[EMAIL PROTECTED]]
> > Sent: Tuesday, September 25, 2001 11:09 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Returning XalanNode from Extension Function. (Xalan
> C++)
> >
> >
> > You cannot modify any part of the source tree, so no, you cannot modify
> > the
> > context node.
> >
> > You'll need to explain more about what you're trying to do before anyone
> > can help you with your question. Since XalanNode is an abstract base
> > class, there is no way to instantiate a XalanNode. If you want to
> return
> > a
> > node set from an extension function, you can certainly do that, but you
> > should only do that if you really need to create nodes. You'll also
> need
> > to know what kind of nodes you need to create.
> >
> > Dave
> >
> >
> >
> >
> >
> > "Avula, Raj"
> >
> > <RAvula@firstam. To:
> > "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> > com> cc: (bcc: David N
> > Bertoni/CAM/Lotus)
> > Subject: Returning
> > XalanNode from Extension Function. (Xalan C++)
> > 09/25/2001 12:59
> >
> > PM
> >
> > Please respond
> >
> > to xalan-dev
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi,
> > I want to return some data from the extension funciton in
> the
> > form
> > of XalanNode rather than in the form of string.
> > Does any body has sample code, on how to do this.
> > Can I modify the context node in the execute method of external
> funciton,
> > so
> > that I can read the changes back in xsl?
> >
> > Currently, I am passing the data in the form of string fom xsl file to
> > external funciton and getting the data back in the form
> > of string(delimited). I am assuming that doing this with XalanNode will
> be
> > more faster than with strings. Am I right?
> >
> > Please let me know how can I create and return XalanNode from execute
> > function.
> >
> > Thank You.
> >
> > Raj.
> >
> > "MMS <firstam.com>" made the following
> > annotations on 09/25/01 10:00:15
> >
> --------------------------------------------------------------------------
> > ----
> >
> > "THIS E-MAIL MESSAGE AND ANY FILES TRANSMITTED HEREWITH, ARE INTENDED
> > SOLELY FOR THE USE OF THE INDIVIDUAL(S) ADDRESSED AND MAY CONTAIN
> > CONFIDENTIAL, PROPRIETARY OR PRIVILEGED INFORMATION. IF YOU ARE NOT THE
> > ADDRESSEE INDICATED IN THIS MESSAGE (OR RESPONSIBLE FOR DELIVERY OF THIS
> > MESSAGE TO SUCH PERSON) YOU MAY NOT REVIEW, USE, DISCLOSE OR DISTRIBUTE
> > THIS MESSAGE OR ANY FILES TRANSMITTED HEREWITH. IF YOU RECEIVE THIS
> > MESSAGE IN ERROR, PLEASE CONTACT THE SENDER BY REPLY E-MAIL AND DELETE
> > THIS
> > MESSAGE AND ALL COPIES OF IT FROM YOUR SYSTEM."
> >
> >
> ==========================================================================
> > ====
> >
> >
> >
> >
> >
> >
>
> "MMS <firstam.com>" made the following
> annotations on 09/25/01 11:46:44
> --------------------------------------------------------------------------
> ----
>
> "THIS E-MAIL MESSAGE AND ANY FILES TRANSMITTED HEREWITH, ARE INTENDED
> SOLELY FOR THE USE OF THE INDIVIDUAL(S) ADDRESSED AND MAY CONTAIN
> CONFIDENTIAL, PROPRIETARY OR PRIVILEGED INFORMATION. IF YOU ARE NOT THE
> ADDRESSEE INDICATED IN THIS MESSAGE (OR RESPONSIBLE FOR DELIVERY OF THIS
> MESSAGE TO SUCH PERSON) YOU MAY NOT REVIEW, USE, DISCLOSE OR DISTRIBUTE
> THIS MESSAGE OR ANY FILES TRANSMITTED HEREWITH. IF YOU RECEIVE THIS
> MESSAGE IN ERROR, PLEASE CONTACT THE SENDER BY REPLY E-MAIL AND DELETE
> THIS
> MESSAGE AND ALL COPIES OF IT FROM YOUR SYSTEM."
>
> ==========================================================================
> ====
>
>
>
>
>
>
"MMS <firstam.com>" made the following
annotations on 09/25/01 13:30:47
------------------------------------------------------------------------------
"THIS E-MAIL MESSAGE AND ANY FILES TRANSMITTED HEREWITH, ARE INTENDED SOLELY FOR THE
USE OF THE INDIVIDUAL(S) ADDRESSED AND MAY CONTAIN CONFIDENTIAL, PROPRIETARY OR
PRIVILEGED INFORMATION. IF YOU ARE NOT THE ADDRESSEE INDICATED IN THIS MESSAGE (OR
RESPONSIBLE FOR DELIVERY OF THIS MESSAGE TO SUCH PERSON) YOU MAY NOT REVIEW, USE,
DISCLOSE OR DISTRIBUTE THIS MESSAGE OR ANY FILES TRANSMITTED HEREWITH. IF YOU RECEIVE
THIS MESSAGE IN ERROR, PLEASE CONTACT THE SENDER BY REPLY E-MAIL AND DELETE THIS
MESSAGE AND ALL COPIES OF IT FROM YOUR SYSTEM."
==============================================================================
