You can get the list info from the e-mail headers on every list e-mail: List-Unsubscribe: <mailto:[EMAIL PROTECTED]> List-Subscribe: <mailto:[EMAIL PROTECTED]> List-Help: <mailto:[EMAIL PROTECTED]> List-Post: <mailto:[email protected]> List-Id: "Turbine Developers List" <turbine-dev.jakarta.apache.org>
So, e-mail [EMAIL PROTECTED] to be removed. David -----Original Message----- From: John Valk [mailto:[EMAIL PROTECTED] Sent: Monday January 31, 2005 2:29 PM To: 'Turbine Developers List' Subject: RE: [Fulcrum] Contribution of new Fulcrum services .... Please REMOVE me from this distribution list. Thank you -----Original Message----- From: Siegfried Goeschl [mailto:[EMAIL PROTECTED] Sent: Tuesday, 1 February 2005 2:13 am To: Eric Pugh; Turbine Developers List Subject: Re: [Fulcrum] Contribution of new Fulcrum services .... Hi Eric, here is the interface >>> public interface Dom4JXSLTService { /** * Transform the DOM4J node using a XSL. * * @param context hierarchical context for XSLT lookup * @param xslName name of the XSLT file to be used * @param in root node of the transformation * @param props name/value pairs passed to the XSLT processor * @return transformed document */ public Document transform ( String[] context, String xslName, Node in, Hashtable props ) throws Exception; /** * Determines if a transformation is avaiable. * * @param context Hierarchical context for XSLT lookup * @param xslName Name of the XSLT file to be used */ public boolean isTransformationAvailable( String[] context, String xslName ); } <<< The differences : +) It uses a context to lookup the template and runs up the directory tree if the locator is used and not just a default.xsl +) It allows passing a Hashtable to XALAN to pass user-defined paramters +) It depends on the Fulcrum ResourceManager Component to lookup the XSL +) It currently does not support org.w3c.dom.Node but this can be added Conclusion It is a more general implementation but it adds additional dependencies due to the intended usage profile +) I use Dom4J in favour to the W3C classes +) I depend on ResourceManager component since it provides me with transparent encryption/decrytion (not commited yet) Cheers, Siegfried Goschl Eric Pugh wrote: >Can we merge the DOM4J and the existing one together? Seems like it >could just be a setting controlling which way is used? How does the >existing one not do what the DOM4J version does? Or, alternatively, >lets deprecate the existing one in favor of the dom4j one if it is >better. > >-----Original Message----- >From: Siegfried Goeschl [mailto:[EMAIL PROTECTED] >Sent: Monday, January 31, 2005 9:14 AM >To: Turbine Developers List >Subject: [Fulcrum] Contribution of new Fulcrum services .... > > >Hi folks, > >I imported > >+) Fulcrum ResourceManager Component >+) Fulcrum Groovy Component > >as Sandbox Components and updated the website. > >Tomorrow I will update the GUMP file .... > >I also have a DOM4JXSLT component for contribution which overlaps with >the existing XSLT component. Would this be a useful contribution? > >Cheers, > >Siegfried Goeschl > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
