IIUC xspCurrentNode stems from the DOM-based pipelines of Cocoon 1. Cocoon 2 uses SAX pipelines that the notion of a current node does not apply anymore.
You are apparently trying to port a C1 XSP to C2. What is it supposed to do? Cheers, Alfred. -----Original Message----- From: Ninh Quyen [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 16. August 2006 16:59 To: users@cocoon.apache.org Subject: Re: Cocoon 2.1.9 and xsp taglibs problems Thanks for your answer Alfred, the Cocoon 2.1 docs don't tell about the changes of the taglibs and built-in objects or more precisely the "xspCurrentNode", which I would like to access. Any other suggestions Ninh. This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please notify the sender urgently and then immediately delete the message and any copies of it from your system. Please also immediately destroy any hardcopies of the message. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. The sender's company reserves the right to monitor all e-mail communications through their networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of the sender's company. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
