Jump to content

schatham

Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About schatham

  • Rank
    Newbie
  1. Outside of some housekeeping & calling other named templates, the code was pretty much the same as I was running. I think I uncovered the issue though. I am using jSimpleX, a visual transformation tool, which tells me a few things about the environment: java.runtime.name=Java(TM) SE Runtime Environmentsun.boot.library.path=C:\Program Files\Java\jre1.6.0_07\binjava.vm.version=10.0-b23java.vm.vendor=Sun Microsystems Inc.java.vendor.url=http://java.sun.com/path.separator=;java.vm.name=Java HotSpot(TM) Client VMfile.encoding.pkg=sun.iosun.java.launcher=SUN_STANDARDuser.country=USsun.os.patch.l
  2. Using your example, I get the same result as you. My xsl code has more going on inside it, but the basic differences between the two is that you are doing a template match, and I am calling this named template from elsewhere in the code (from inside another named template). I even went so far as to treat $tempsample as a number:<xsl:variable name="tempsample" select="number($sample)"/> before using it in the assignment of a value to that variable. <xsl:variable name="tempsum" select="sum(document('')/xsl:stylesheet/lu:temperatures/lu:reading[position() < $tempsample])"/>
  3. I've tried that - it is still returning zero for the value.
  4. I've got a list of values that will be inside an xsl stylesheet document. <lu:temperatures> <lu:reading>87</lu:reading> <lu:reading>44</lu:reading> <lu:reading>71</lu:reading> <lu:reading>99</lu:reading> <lu:reading>100</lu:reading> <lu:reading>99</lu:reading> <lu:reading>57</lu:reading> <lu:reading>63</lu:reading> <lu:reading>104</lu:reading> <lu:reading>84</lu:reading> <lu:reading>84</lu:reading> <lu:reading>91</lu:read
  5. I am working in xslt 1.0, and cannot use extensions & am limited as to what namespaces can be used (currently only http://www.w3.org/1999/XSL/Transform can be used). Another limitation I am working with is the 3rd party application I am using will not properly process includes or imports into the XSL. In other words - the xslt that I need to use must be pretty much self-inclusive, in that whatever is called or referenced must be in the xslt itself & nowhere else. I had decided to try to do a conversion to Julian date & mimic how Excel might do the conversion. I've got the date
  6. We discovered that the problem wasn't in xsl - we were doing the includes correctly. The issue turned out to be "where" the includes were coming from. In our case, the xsl that called the include was in a database, and it was trying to call out to a web folder. Neither one had permissions to see the other. I had also tried it in jsimplex (a java app that was a simple xslt editor), and the issue there was when it tried to process the include, it was trying to access it from a folder relative to where I had that installed (which didn't exist). Although it might not be 100% on-topic, I can r
  7. It's a product from SAP relating to manufacturing. My general question was whether there was a way to "see" what the xsl code was with all the includes in it. As it is, what I'd see should I display the xsl would be the main xsl, with one line that says <xsl:include href="......."/>.What I would want to see would be the main xsl, with the code behind the include also in line with it. I believe the other issue with the well-formed markup error message is relating to how that product extracts the xsl code from the database, and permissions & name resolution at that time...However, m
  8. Working with SAP MII using a fairly straightforward xslt transformation. I have one xsl file that uses an include to bring in another xsl file to add something to the transformation. The error I get when I try to do this is: "The markup in the document following the root element must be well-formed."XML: <?xml version="1.0" encoding="UTF-8"?><Rowset> <Row> <ItemNo>00000000001884304</ItemNo> <ItemDesc>Test Item Description</ItemDesc> </Row> </Rowset> The first xsl: <xsl:stylesheet version="1.0" xmlns:xsl="http://
×
×
  • Create New...