RE: [saxon] saxon:assign

[Michael Kay <mhk@mh...>]

Some thoughts:

(a) Have you tried running the same stylesheet outside Studio?

(b) What version of Saxon are you using?

(c) How have you declared the Saxon namespace?

(d) Have you specified extension-element-prefixes="saxon"?

Incidentally, it's really best to try and write your code without
saxon:assign if you possibly can - and it's almost invariably possible.

Michael Kay
http://www.saxonica.com/
 

> -----Original Message-----
> From: saxon-help-admin@... 
> [mailto:saxon-help-admin@...] On Behalf Of 
> Tom Patterson
> Sent: 07 October 2004 20:59
> To: saxon-help@...
> Subject: [saxon] saxon:assign
> 
> I am having some problems using the saxon:assign element.
> At the top of the xslt, I have:
> 
>  
>  
>  
> 
> I am trying to use the saxon processor (7) included in
> Stylus Studio, but everytime it gets to one of those
> elements, I get a java.lang.RuntimeException: Unknown
> extension element. I also tried to just run the processor
> from the command line, but I got the same error message. I
> tried askign for help at the Stylus Studio discussion
> board, but they said to go here with saxon questons. Any
> ideas? Thanks.
> 
> Tom
> 
> 
> 		
> _______________________________
> Do you Yahoo!?
> Declare Yourself - Register online to vote today!
> http://vote.yahoo.com
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on 
> ITManagersJournal
> Use IT products in your business? Tell us what you think of 
> them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to 
> find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> saxon-help mailing list
> saxon-help@...
> https://lists.sourceforge.net/lists/listinfo/saxon-help
> 

[saxon] saxon:assign

[Tom Patterson <tcpatter@ya...>]

I am having some problems using the saxon:assign element.
At the top of the xslt, I have:

 
 
 

I am trying to use the saxon processor (7) included in
Stylus Studio, but everytime it gets to one of those
elements, I get a java.lang.RuntimeException: Unknown
extension element. I also tried to just run the processor
from the command line, but I got the same error message. I
tried askign for help at the Stylus Studio discussion
board, but they said to go here with saxon questons. Any
ideas? Thanks.

Tom


		
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com

RE: [saxon] DOMResult structure

[Milan Trninic <mtrninic@ga...>]

Thanks Michael,
 
I'll analyze this further since I had some problems but not really sure
what causes them. 
Essentially, if I use the document, I get the following error:
 
Error at element constructor <resultRoot> on line 1048575 
org.w3c.dom.DOMException: HIERARCHY_REQUEST_ERR: An attempt was made to
insert a node
where it is not permitted. 

This may be just some syntax omission on my side - I'll look at it more.

 

Milan

-----Original Message-----
From: saxon-help-admin@...
[mailto:saxon-help-admin@...] On Behalf Of Michael Kay
Sent: Wednesday, October 06, 2004 16:09
To: saxon-help@...
Subject: RE: [saxon] DOMResult structure


No, you should be able to create a Document, wrap it in a DOMResult, and
supply that as the result for the transformation. There's an example of
this in the TraxExamples application.
 
Michael Kay
http://www.saxonica.com/


  _____  

From: saxon-help-admin@...
[mailto:saxon-help-admin@...] On Behalf Of Milan
Trninic
Sent: 06 October 2004 23:17
To: saxon-help@...
Subject: [saxon] DOMResult structure


Hi,
 
Is it true that if I want to get the transformation result in a
non-saxon DOM tree, I have to supply the element, like so:
 
Document doc = //obtain document//
Element element = doc.getDocumentElement();
DOMResult result = new DOMResult(element);
 
and not the document itself, like so:
 
DOMResult result = new DOMResult(doc);
 
I want to avoid the extra root element in the result because the
transformation itself creates the result exactly as it should be.
 
Thanks
 
Milan

RE: [saxon] is namespace axis supported?

[Milan Trninic <mtrninic@ga...>]

Michael - thanks for the quick answer.
I was using xerces and saxon 7.9 and 8.1.
Here is some more info, note that this was done with saxon 8.1
Also note that I was using the exampleDOMtoDOMAlien method from saxon
examples. The method is slightly modified because I was trying some
other things - not related to this particular issue. The method is also
listed below.
 
1. Failure:
 
Instance:
 
<Root xmlns=" <http://www.galdosinc.com/fps>;
http://www.galdosinc.com/fps">;
     <Property>
     </Property>
</Root> 
 
Style:
 
<?xml version="1.0" encoding="UTF-8"?>
<xsl:transform  xmlns:xsl=" <http://www.w3.org/1999/XSL/Transform>;
http://www.w3.org/1999/XSL/Transform"; 
     version="1.0">
 <xsl:template match="/">
  <xsl:element name="resultRoot" >
   <xsl:for-each select="//namespace::*[local-name() != '' ]">
    <xsl:copy/>
   </xsl:for-each>
  </xsl:element>
 </xsl:template>
</xsl:transform>
 
It throws the ClassCastException in NodeWrapper in the method:
 
    public int compareOrder(NodeInfo other) {
        // TODO: use the DOM Level-3 compareDocumentPosition() method if
available
        return Navigator.compareOrder(this, (SiblingCountingNode)other);
    }
 
2. Works well:
If I use the following instance, without the child Property, there is no
error:
<Root xmlns=" <http://www.galdosinc.com/fps>;
http://www.galdosinc.com/fps">;
</Root>
 
 
The method:
 
  public void exampleDOMtoDOMAlien(String sourceID, String xslID)
          throws TransformerException,
TransformerConfigurationException,
                 SAXException, IOException,
ParserConfigurationException,
                 MalformedURLException 
 {
   //System.setProperty("javax.xml.parsers.DocumentBuilderFactory",
factory);
   TransformerFactory tfactory = TransformerFactory.newInstance();
   //tfactory.setAttribute(FeatureKeys.TREE_MODEL, new
Integer(Builder.STANDARD_TREE));
 
   Templates templates;
 
   {
    DocumentBuilderFactory dfactory =
DocumentBuilderFactory.newInstance();
    dfactory.setNamespaceAware(true);
    DocumentBuilder docBuilder = dfactory.newDocumentBuilder();
 
    System.err.println("Using DocumentBuilderFactory " +
dfactory.getClass());
    System.err.println("Using DocumentBuilder " +
docBuilder.getClass());
 
    Node doc = docBuilder.parse(new InputSource(new
File(xslID).toURL().toString()));
    System.err.println("Stylesheet document built OK");
    DOMSource dsource = new DOMSource(doc);
 
    // If we don't do this, the transformer won't know how to
    // resolve relative URLs in the stylesheet.
    dsource.setSystemId(new File(xslID).toURL().toString());
 
    templates = tfactory.newTemplates(dsource);
   }
 
   Transformer transformer = templates.newTransformer();
   DocumentBuilderFactory dfactory =
DocumentBuilderFactory.newInstance();
   DocumentBuilder docBuilder = dfactory.newDocumentBuilder();
 
   Document doc = docBuilder.parse(new InputSource(new
File(sourceID).toURL().toString()));
   Node bar = doc.getDocumentElement();
   System.err.println("Source document built OK");
 
    // added by MHK
   DOMSource ds = new DOMSource(doc);
   ds.setSystemId(new File(sourceID).toURL().toString());
    // end of addition
 
    // create a skeleton output document, to which
    // the transformation results will be added
 
   Document out = docBuilder.newDocument();
   Element a = out.getDocumentElement();
   Element extra = out.createElement("svg");
   out.appendChild(extra);
   
   DOMResult result = new DOMResult(extra);
   transformer.transform(ds, result);
   out.replaceChild(extra.getFirstChild(), extra);
   System.err.println("Transformation done OK");
 
   // Serialize the output so we can see the transformation actually
worked
   Transformer serializer = tfactory.newTransformer();
   serializer.transform(new DOMSource(out), new
StreamResult(System.out));
 
   return;
 }



-----Original Message-----
From: saxon-help-admin@...
[mailto:saxon-help-admin@...] On Behalf Of Michael Kay
Sent: Wednesday, October 06, 2004 16:06
To: saxon-help@...
Subject: RE: [saxon] is namespace axis supported?


The namespace axis should work with all kinds of Source. Which version
of Saxon are you using, and which DOM implementation?
 
If there's a failure with a DOMSource then I'm not entirely surprised,
because DOM allows all sorts of inconsistency to arise in the tree that
can't be properly represented in the XPath data model, and there are
lots of differences between different implementatons. But I'd like to
know the details.
 
Michael Kay
http://www.saxonica.com/


  _____  

From: saxon-help-admin@...
[mailto:saxon-help-admin@...] On Behalf Of Milan
Trninic
Sent: 06 October 2004 23:14
To: saxon-help@...
Subject: [saxon] is namespace axis supported?


Hi,
 
I couldn't figure out whether Saxon (non-commercial) supports the
namespace axis. The documentation (XPath syntax section) doesn't list it
among the supported axis. However, it seems to be working ok if I use
StreamSource, but not if I use DOMSource (reports an error in the latter
case).
 
The expression I used is simple
 
<xsl:for-each select="//namespace::*">
....
 
Cheers
 
Milan

RE: [saxon] problem running one of the examples:books-sql

[Michael Kay <mhk@mh...>]

I think your reference to XQuery here is a red herring - the example uses
XSLT and the Saxon SQL extension.
 
Saxon's error message here is very unhelpful, but it occurs when the
stylesheet has decided (at compile time) to take the xsl:fallback route
because it cannot locate the implementation of the SQL extension
instructions. Generally this is a classpath problem.
 
See what happens when you use the same classpath and do
 
javap -classpath XXXX net.sf.saxon.sql.SQLQuery
 
This will tell you whether the classpath is correct or not.
 
Michael Kay
http://www.saxonica.com/


  _____  

From: saxon-help-admin@...
[mailto:saxon-help-admin@...] On Behalf Of Srikumar.Kareti
Sent: 06 October 2004 17:43
To: saxon-help@...
Subject: [saxon] problem running one of the examples:books-sql


Guys, I need help!
 
I downloaded SaxonB version 8. I tried running the example which uses
XQuery.
I did not make any changes to the code, I just wanted to run it and see if
it tries
to make a connection to the non-existing database. I got a compile error.
 
Am I missing something.
 
Here is my run.
--->
C:\Tools\SaxonB\samples>C:\j2sdk1.4.2_05\bin\java -classpath
"c:\Tools\SaxonB\sa
xon8.jar;c:\Tools\SaxonB\saxon8-jdom.jar;c:\Tools\SaxonB\saxon8-sql.jar;C:\P
rogr
am Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msbase.jar;C:\Program
Fil
es\Microsoft SQL Server 2000 Driver for JDBC\lib\msutils.jar;C:\Program
Files\Mi
crosoft SQL Server 2000 Driver for JDBC\lib\mssqlserver.jar;"
net.sf.saxon.Trans
form data\books.xml styles\books-sql.xsl
Error at xsl:variable on line 28 of
file:/C:/Tools/SaxonB/samples/styles/books-s
ql.xsl:
  XP0006: An empty sequence is not allowed as the value of variable
$connection
Failed to compile stylesheet. 1 error detected.
--->
 
Thanks, SriKumar.