| Wabiloo |
| Member |
|
| UK |
|
|
| None Specified |
|
| Thursday, November 5, 2009 |
| Wednesday, August 25, 2010 3:00:08 PM |
13
[0.07% of all post / 0.00 posts per day] |
|
vlad wrote:Yes, there is currently such a limitation. Based on your input we will be implementing in future support for multiple msxsl:script definitions including support for multiple files. Due date is currently not available though.
Hi!
Any update on this?
Many thanks!
|
Hi!
I'm using AltovaXML for increasingly complex situations, and am now trying to write extension functions to add things that are not available as standard in XSLT 2.0.
There is unfortunately precious little information about this in the AltovaXML documentation. I have found it easy to pass basic datatypes (as explained in the section 'Datatypes: XPath/XQuery to Java' in the .chm file), but haven't found anything about passing nodesets or sequences between Java and XPath?
Is that possible? If so, what Java datatype should I use? Any chance of an example piece of code for that?
|
Hi,
Is there a way with AltovaXML to parse a string into an XML nodeset?
Saxon has saxon:parse() for that, and seems to be doing exactly what I need. Anything like that in AltovaXML?
|
Hi,
Is there a way with AltovaXML to access documents protected by HTTP authentication within an XSLT script?
I'm really after a method allowing me to specify a username and password to use when trying to access a specified URL.
Many thanks,
Fabre Lambeau
|
I will answer my own question...
I noticed that 2010 rel.2 is out, and that the release notes indicate that the problem has been fixed. A quick download, installation and test seems to confirm it.
Good job, Altova team, and many thanks!
|
I was wondering if any feedback was available, either whether a fix had been devised (and when that would be released), or whether a workaround is possible.
I'm building an XSLT2 application using AltovaXML and this problem is causing me some significant trouble...
Many thanks
|
|
For information, I tried replacing the call to document() with a call to the XPath 2.0 doc() function, but this doesn't help. Altova still crashes.
|
[This is a bug report. Every time I try to use the Support Form, it tells me that "an error occurred", so I decided to post it here...]
Hi!
I've noticed a very strange (and annoying) behaviour when trying to download documents for processing within an XSLT2 script executed with AltovaXML.
If the URL to access contains percent-encoded characters (in accordance with RFC 3986), AND I test for availability of that document with doc-available() AND then load the document with document(), THEN the AltovaXML.exe simply crashes.
Interestingly,
- If I remove the percent-encoded character, it all works (but I don't have the ability to do so in production, as it's the hand of my users)
- If I don't test first with doc-available(), it all works
- If I leave the doc-available() in, but don't use document(), no crash (but obviously no document either)
I'm using AltovaXML 2010, at the command line, under Windows Vista. The problem is reproducible, on my 3 (Vista) computers.
Here is a standalone XSLT2 sheet which is sufficient to demonstrate the problem. The percent-encoded character is '%40', which corresponds to '@'
Code:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
exclude-result-prefixes="xs"
version="2.0">
<xsl:output method="xml" indent="yes"/>
<xsl:template match="/">
<xsl:variable name="bla">http://www.google.com/calendar/feeds/fabre%40inspiredsignage.com/private-842d8214b88d326f20c6aa5aced0e4cb/full?alt=atom</xsl:variable>
<xsl:choose>
<xsl:when test="doc-available($bla)">
<success>
<xsl:sequence select="document($bla)"/>
</success>
</xsl:when>
<xsl:otherwise>
<error>Feed not available</error>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
</xsl:stylesheet>
|
That's interesting...
In the same document, section 10.3, I read "If a stylesheet function has been defined with a particular expanded-QName, then a call on function-available will return true when called with an argument that is a lexical QName that expands to this same expanded-QName."
I'd also argue that if it's returning false in an xsl:use-when, why is it returning true in an xsl:value-of?
|
Hi!
I'm using AltovaXML (command line tool), and have run into weird behaviour.
I'm trying to make my stylesheet portable (for use with Altova and Saxon) and therefore use the function-available() function in xsl:use-when quite a bit.
I have however noticed that when I do that, Altova skips the elements that test for the availability of my own extension functions. For example the following does not output anything:
Code:<xsl:text use-when="function-available('myfunctions:currentCulture')>bla</xsl:text>
I know that that function does work with Altova however!
Indeed, if I test availability into the output, with
Code:<xsl:message select="function-available('myfunctions:currentCulture')/>
then Altova outputs 'true'.
If I use the function (without testing with use-when), then Altova does find and use the function properly, so it clearly has access to it. For example:
Code:<xsl:value-of select="myfunctions:currentCulture()"/>
Why then does it skip the elements if I use the expression in a use-when?
Note: the functions are defined in another XSL file which is imported in my main XSL file
Edited: It seems that the problem is with not recognising/finding user-written stylesheet functions (defined with <xsl:function>). System functions and .Net extension functions are recognised allright
|
|
