 |
 |
 |
It seems to be Xalan Java 2.4.1
version.JAXP=1.1
version.DOM=2.0
version.SAX=2.0
version.xalan2x=Xalan Java 2.4.1
Citando Michael Kay <mhk@xxxxxxxxx>:
> Questions about calling Java from XSLT are meaningless unless we know what
> XSLT processor you are using. The mechanisms vary from one XSLT processor to
> another.
>
> Michael Kay
>
> > -----Original Message-----
> > From: xptm@xxxxxxx [mailto:xptm@xxxxxxx]
> > Sent: 01 July 2004 14:10
> > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> > Subject: [xsl] Java namespace
> >
> > First, let me tell i'm not a expertise in these areas, so
> > bear with me...
> >
> > When i declare a namespace pointing to a Java class, is that
> > Java class treated
> > as a Static class? Or does the XSL processor somehow
> > instatiates a object of
> > that class?
> >
> > I'm asking this cause i have this situation:
> >
> > <?xml version="1.0" encoding="ISO8859-1" ?>
> > <xsl:stylesheet version="2.0"
> > xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> > xmlns:gti = "SQLHelper" >
> >
> > (...)
> > <xsl:element name="ResultSet">
> > <xsl:attribute name="sql"><xsl:value-of
> > select="gti:AcertaSqlReservado($sql)"/></xsl:attribute>
> > </xsl:element>
> >
> > This XSLT is called by a Java program
> >
> > public class Tester{
> > public static void main(String[] args) {
> > try {
> > BufferedReader br = new BufferedReader(new InputStreamReader(new
> > FileInputStream(xin+".xml")));
> > PrintWriter out = new PrintWriter(new
> > FileOutputStream(xout+".xml"));
> > try {
> > TransformerFactory xformFactory =
> > TransformerFactory.newInstance();
> > Source xsl = new StreamSource("Testes12.xsl");
> > Transformer stylesheet = xformFactory.newTransformer(xsl);
> > Source request = new StreamSource(br);
> > Result response = new StreamResult(out);
> > //stylesheet.setParameter("gui", "awt");
> > stylesheet.transform(request, response);
> > }
> > catch (TransformerException e) {
> > System.err.println(e);
> > }
> > }
> > catch (FileNotFoundException e) {
> > System.err.println(e);
> > }
> > }
> > }
> >
> > This works OK, but if i change the XSL to
> >
> > <?xml version="1.0" encoding="ISO8859-1" ?>
> > <xsl:stylesheet version="2.0"
> > xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> > xmlns:gti = "Tester" ---> the same Java class
> > that call the XSLT
> >
> > i got a TransformerException.
> >
> > But i don't understand why.
> >
> > Thanks all.
> >
> >
> >
> >
> >
> >
> > O SAPO já está livre de vírus com a Panda Software, fique você também!
> > Clique em: http://antivirus.sapo.pt
> >
> > --+------------------------------------------------------------------
> > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
> > To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
> > or e-mail: <mailto:xsl-list-unsubscribe@xxxxxxxxxxxxxxxxxxxxxx>
> > --+--
> >
> >
>
>
> --+------------------------------------------------------------------
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
> To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
> or e-mail: <mailto:xsl-list-unsubscribe@xxxxxxxxxxxxxxxxxxxxxx>
> --+--
>
>
O SAPO já está livre de vírus com a Panda Software, fique você também!
Clique em: http://antivirus.sapo.pt
|
 | 

|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |