gestalt-users Mailing List for Gestalt XSLT 2.0 processor (Page 2)
Status: Alpha
Brought to you by:
colin-adams
You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(5) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(16) |
Aug
(16) |
Sep
(58) |
Oct
(2) |
Nov
|
Dec
(15) |
2007 |
Jan
(3) |
Feb
(2) |
Mar
|
Apr
|
May
(8) |
Jun
|
Jul
|
Aug
(1) |
Sep
(6) |
Oct
(1) |
Nov
(2) |
Dec
|
2008 |
Jan
(1) |
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
From: Colin P. A. <co...@co...> - 2007-02-04 09:37:57
|
Erik Wilde (dr...@be...) has written an XSLT 2.0 transformation for performing XInclude processing. Google for xipr.xsl. It is therefore now possible (with certain limitations) to perform XInclude processing within Gobo. To do so, first create a transformation called xinclude.xsl like this: <xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0"> <xsl:include href="xipr.xsl"/> <xsl:template match="/"> <xsl:apply-templates select="." mode="xipr"/> </xsl:template> </xsl:transform> Then from the command line: gexslt xinclude.xsl my.xml (or the equivalent from within an Eiffel program). The output will be a copy of my.xml with all XInclude actions performed. This could be useful with geant scripts, for instance, or as a goanna servlet, perhaps. Limitations: The accept and accept-language attributes are not supported (this is not possible from XSLT). Only shorthand and element() xpointers are supported (minimal conformance). Additional gobo limitations: Parse=text processing is currently only supported for UTF-8 (and therefore ASCII). ACTION: Franck Likewise, parse=xml is restricted to those encodings currently supported by the Gobo Eiffel XML parser (UTF-8, UTF-16, ISO8859-1 and US-ASCII if my memory serves me). If the xpointer attribute is present, then gexslt will throw an error due to the limitations of the Gobo PCRE regular expression library (it does not understand Unicode character classes/properties). I think it will not be possible to patch this, and so a new, Unicode-aware, regular expression engine is needed. ACTION: Any takers? It may be possible to get around this by patching xipr.xsl - simply remove the matches (@xpointer, ...) tests. This will mean that bad xpointers will slip through, causes spurious crashes, but it should work for good ones. Better would be to replace the matches (@xpointer, ...) function calls with other, more cumbersome, regular expressions, that have the same effect, or a specially written xsl:function to check the syntax without using regular expressions. -- Colin Adams Preston Lancashire |
From: Florent G. <dar...@ya...> - 2007-01-23 12:24:41
|
Colin Adams wrote: > I suggest you raise it on the bug tracker for now. Done: https://sourceforge.net/tracker/index.php?func=detail&aid=1642456&group_id=124274&atid=699086 Thanks, --drkm ___________________________________________________________________________ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com |
From: Colin A. <col...@ho...> - 2007-01-23 07:31:40
|
>From: Florent Georges <dar...@ya...> > $ gexslt style.xsl input.xml --trace=trace.out > > gexslt: system execution failed. > Please note the --trace argument. It is required to >reproduce the bug. trace.out contains: > > <trace xmlns="http://www.gobosoft.com/eiffel/gobo/gexslt/trace" >xmlns:xsl="http://www.w3.org/1999/XSL/Transform" > timing="false"> > <node path="/" line="0" >base_uri="file:/c%3A/Documents+and+Settings/.../tmp/test-hello-world.xml"> > <TODO-Unknown-tag-1323 gexslt-name=" Gobo CVS is currently frozen, pending a new release, and then we will be converting to subversion. As a result, I probably won't be able to fix this for a week or two. I suggest you raise it on the bug tracker for now. _________________________________________________________________ Find Love This New Year With match.com! http://msnuk.match.com |
From: Florent G. <dar...@ya...> - 2007-01-22 23:38:28
|
Hi Colin I just experimented a bug in Gexslt from the latest CVS. Here is the test case: $ cat style.xsl <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0"> <xsl:template match="/"> <html/> </xsl:template> </xsl:stylesheet> $ cat input.xml <t/> $ gexslt style.xsl input.xml --trace=trace.out gexslt: system execution failed. Following is the set of recorded exceptions: ------------------------------------------------------------------------------- Class / Object Routine Nature of exception Effect ------------------------------------------------------------------------------- GEXSLT root's creation Segmentation violation: <00000000016B003C> Operating system signal. Exit ------------------------------------------------------------------------------- GEXSLT root's creation <00000000016B003C> Routine failure. Exit ------------------------------------------------------------------------------- make: *** [debug] Error 1 Please note the --trace argument. It is required to reproduce the bug. trace.out contains: <trace xmlns="http://www.gobosoft.com/eiffel/gobo/gexslt/trace" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" timing="false"> <node path="/" line="0" base_uri="file:/c%3A/Documents+and+Settings/.../tmp/test-hello-world.xml"> <TODO-Unknown-tag-1323 gexslt-name=" Regards, --drkm ___________________________________________________________________________ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com |
From: Florent G. <dar...@ya...> - 2006-12-21 01:37:06
|
Colin Adams wrote: Hi > It was simply that I failed to re-initialize a variable to > Void, so the second if condition was "remembering" that it > should evaluate to true() - incorrectly. Ok, I see. > Fixed. I'll check this in before the night is out. Great! I'll try to check the original, real code works with the fix. Thanks, --drkm ___________________________________________________________________________ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com |
From: Florent G. <dar...@ya...> - 2006-12-21 01:36:34
|
Colin Adams wrote: > From: "Colin Adams" > > Or rather, I hadnt completed it. Ive fixed it now, but > > a couple of my regression tests failed, so I havent > > commited the fix yet. I will try and do so tonight. > Fix committed now. Great news! I'll try to check the fix against the original code ASAP. Thanks, --drkm ___________________________________________________________________________ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com |
From: Florent G. <dar...@ya...> - 2006-12-21 01:35:59
|
Colin Adams wrote: Hi > In fact, its an accident of history. > Originally, I had full support for namespace nodes. But > when I realized they were deprecated and optional, I > removed them - overzealously. finally, the spec. was > clarified so that support for the namespace axis is > required for XPath 1.0 compatibility mode. Mmh, I always thought namespace nodes were optional in XPath 2.0 but required in XSLT 2.0. But I was not able to find the right verse in [XSLT2]. At least §5.7.3 or xsl:namespace suggest namespace nodes are required in XSLT 2.0, but I didn't find that for sure. Just out of curiosity, I will ask that on XSL List. > Since you find it so easy to understand Eiffel (it is > designed for maximum clarity), why not take a look at > http:?se.inf.ethz.ch?teaching?ws2006?0001?english_index.html > (substitute slashes for ?)? Very interesting. But as always, the answer to the "why not?" is "only 24 hours in a day"... But I bookmarked the link; knowing a new language, even just a little bit, is always interesting. Regards, --drkm ___________________________________________________________________________ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com |
From: Colin A. <col...@ho...> - 2006-12-20 21:02:03
|
>From: "Colin Adams" <col...@ho...> >OK - I do see the problem. > >Debugging shows that the second if expression is not getting called, and it >doesn´t appear to be an optimisation problem either. > >This might be too hard to solve until I get home for the New Year. I spoke far too soon. It was simply that I failed to re-initialize a variable to Void, so the second if condition was "remembering" that it should evaluate to true() - incorrectly. Fixed. I'll check this in before the night is out. _________________________________________________________________ Think you're a film buff? Play the Movie Mogul quiz and win fantastic prizes! http://www.msnmoviemogul.com |
From: Colin A. <col...@ho...> - 2006-12-20 20:43:42
|
OK - I do see the problem. Debugging shows that the second if expression is not getting called, and it doesn´t appear to be an optimisation problem either. This might be too hard to solve until I get home for the New Year. _________________________________________________________________ It's Hotmail's 10th Birthday! Come and play Pass the Parcel http://www.msnpasstheparcel.com |
From: Colin A. <col...@ho...> - 2006-12-20 20:02:44
|
>From: Florent Georges <dar...@ya...> > Hi Colin, > > I just found a strange behaviour in Gexslt. It seems to >be related to the parameter handling. Here is the test >case. Note that using the string 'deep-equal' directly >instead of using a parameter make the test to succeed. As >well as using a variable instead of a parameter. So the >last element in the result is: > > <expect select="$expect deep-equal $result"/> > >however I think it would have to be: > > <expect select="deep-equal($expect, $result)"/> I don´t understand. 1) What is the problem? 2) How do I know if the test suceeds or not? _________________________________________________________________ It's Hotmail's 10th Birthday! Come and play Pass the Parcel http://www.msnpasstheparcel.com |
From: Colin A. <col...@ho...> - 2006-12-20 19:59:44
|
>From: "Colin Adams" <col...@ho...> > >From: Florent Georges <dar...@ya...> > > > > > > > Mmh, I maybe spook too early for namespace-uri-for-prefix(). > > >Actually it doesn't seems to be the problem, but xsl:namespace > > >does. If you replace xsl:namespace by xsl:attribute, all > > >runs fine: > > > >Ah. That seems far more likely, as I only completed the implementation of > >it > >last weekend! > >Or rather, I hadnt completed it. >Ive fixed it now, but a couple of my regression tests failed, so I havent >commited the fix yet. I will try and do so tonight. Fix committed now. _________________________________________________________________ It's Hotmail's 10th Birthday! Come and play Pass the Parcel http://www.msnpasstheparcel.com |
From: Colin A. <col...@ho...> - 2006-12-20 07:39:36
|
>From: Florent Georges <dar...@ya...> > I don't know Eiffel, but if I understand correctly, the You understand perfectly. >item type passed to XM_XPATH_ORPHAN.make is not correct. >It is taken in XM_XSLT_TEXT_CONSTRUCTOR from >item_type.primitive_type, where item_type is set in >XM_XSLT_COMPILED_NAMESPACE: > > item_type: XM_XPATH_ITEM_TYPE is > do > Result := any_item > end > > I wonder if the primitive_type of any_type is correct >here. Doesn't have it to be Namespace_node ? Yes. As you will have seen, I had a comment in the code querying that. In fact, its an accident of history. Originally, I had full support for namespace nodes. But when I realized they were deprecated and optional, I removed them - overzealously. finally, the spec. was clarified so that support for the namespace axis is required for XPath 1.0 compatibility mode. After some agonizing, I reluctantly decided to retain support for XPath 1.0 compatibility, and so I restored namespace axis support, and set about adding back stuff like Namespace_node - just sufficient to get it to compile again. This was an area I overlooked, seeing as I had never fully implemented it, there were no regression tests to fail. > But once again I don't know Eiffel, I just tried to read >the sources and figure what happen. Maybe that will help >you, maybe not. I had already fixed it (although there turned out to be a lot more than just that to fix). Since you find it so easy to understand Eiffel (it is designed for maximum clarity), why not take a look at http:?se.inf.ethz.ch?teaching?ws2006?0001?english_index.html (substitute slashes for ?)? _________________________________________________________________ Think you're a film buff? Play the Movie Mogul quiz and win fantastic prizes! http://www.msnmoviemogul.com |
From: Colin A. <col...@ho...> - 2006-12-20 07:26:09
|
>From: "Colin Adams" <col...@ho...> >From: Florent Georges <dar...@ya...> > > > > Mmh, I maybe spook too early for namespace-uri-for-prefix(). > >Actually it doesn't seems to be the problem, but xsl:namespace > >does. If you replace xsl:namespace by xsl:attribute, all > >runs fine: > >Ah. That seems far more likely, as I only completed the implementation of >it >last weekend! Or rather, I hadnt completed it. Ive fixed it now, but a couple of my regression tests failed, so I havent commited the fix yet. I will try and do so tonight. _________________________________________________________________ It's Hotmail's 10th Birthday! Come and play Pass the Parcel http://www.msnpasstheparcel.com |
From: Florent G. <dar...@ya...> - 2006-12-20 02:15:05
|
Colin Adams wrote: > From: Florent Georges > > A few months ago, I installed the following version: > > EiffelStudio 5 (5.7.62804 GPL Edition). I don't know if > > it is interesting to upgrade? Note I only need it for > > Gexslt. > I would feel happier if you upgraded, as there are quite a > lot of bug fixes listed since then. I'd hate to spend time > on a future bug report from you, only to find that it was > actually a compiler bug. Of course. I just installed the 5.7.64493. > > Mmh, I maybe spook too early for namespace-uri-for-prefix(). > > Actually it doesn't seems to be the problem, but > > xsl:namespace does. If you replace xsl:namespace by > > xsl:attribute, all runs fine: > Ah. That seems far more likely, as I only completed the > implementation of it last weekend! I don't know Eiffel, but if I understand correctly, the item type passed to XM_XPATH_ORPHAN.make is not correct. It is taken in XM_XSLT_TEXT_CONSTRUCTOR from item_type.primitive_type, where item_type is set in XM_XSLT_COMPILED_NAMESPACE: item_type: XM_XPATH_ITEM_TYPE is do Result := any_item end I wonder if the primitive_type of any_type is correct here. Doesn't have it to be Namespace_node ? But once again I don't know Eiffel, I just tried to read the sources and figure what happen. Maybe that will help you, maybe not. Regards, --drkm ___________________________________________________________________________ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com |
From: Colin A. <col...@ho...> - 2006-12-19 15:20:08
|
From: Florent Georges <dar...@ya...> > > > BTW, you may not know that EiffelStudio 5.7 is now out of > > beta - in which case you should probably upgrade > > A few months ago, I installed the following version: >EiffelStudio 5 (5.7.62804 GPL Edition). I don't know if it >is interesting to upgrade? Note I only need it for Gexslt. I would feel happier if you upgraded, as there are quite a lot of bug fixes listed since then. I'd hate to spend time on a future bug report from you, only to find that it was actually a compiler bug. > > Mmh, I maybe spook too early for namespace-uri-for-prefix(). >Actually it doesn't seems to be the problem, but xsl:namespace >does. If you replace xsl:namespace by xsl:attribute, all >runs fine: Ah. That seems far more likely, as I only completed the implementation of it last weekend! _________________________________________________________________ Think you're a film buff? Play the Movie Mogul quiz and win fantastic prizes! http://www.msnmoviemogul.com |
From: Florent G. <dar...@ya...> - 2006-12-19 14:50:30
|
Colin Adams wrote: Hi Colin, > From: Florent Georges > > I've worked a little bit on XSLT Unit, and I found a > > bug (I think) related to namespace-uri-for-prefix(). I > > updated my copy of Gexslt today. Here is the test case, > > with the > BTW, you may not know that EiffelStudio 5.7 is now out of > beta - in which case you should probably upgrade A few months ago, I installed the following version: EiffelStudio 5 (5.7.62804 GPL Edition). I don't know if it is interesting to upgrade? Note I only need it for Gexslt. > > as="namespace()*", but namespace() is not a valid KindTest. > Hm. Maybe I should check the spec. - just because I don't > support the namespace axis, may not necessarily mean the > kinfd test is invalid. No, it is a well-known limitation of XPath 2.0, IMHO. The KindTest production rule is defined as: [54] KindTest ::= DocumentTest | ElementTest | AttributeTest | SchemaElementTest | SchemaAttributeTest | PITest | CommentTest | TextTest | AnyKindTest which means, more or less, with all possible variations: [54] KindTest ::= "document-node(...)" | "element(...)" | "attribute(...)" | "schema-element(...)" | "schema-attribute(...)" | "processing-instruction(...)" | "comment()" | "text()" | "node()" So you have a KindTest for each node type (even two for elements and attributes), but for namespace nodes. BTW, you don't support the namespace *axis*, but you support namespace *nodes*, if I'm right. For example xsl:namespace works as expected, and produces a namespace node. > OK. I will look into it. > I assume it also fails with a production build? Yes. Mmh, I maybe spook too early for namespace-uri-for-prefix(). Actually it doesn't seems to be the problem, but xsl:namespace does. If you replace xsl:namespace by xsl:attribute, all runs fine: (drkm)[113] ~/xslt/tests$ cat copy-namespaces.xsl <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:my="my:copy-namespaces.xsl" exclude-result-prefixes="my" version="2.0"> <xsl:output omit-xml-declaration="yes"/> <xsl:template match="root"> <root> <xsl:sequence select="my:copy-namespaces(.)"/> </root> </xsl:template> <!-- Not usefull version that creates attributes of the form prefix="the://namespace/uri". --> <xsl:function name="my:copy-namespaces" as="node()*"> <xsl:param name="context" as="element()"/> <xsl:for-each select="in-scope-prefixes($context)"> <xsl:attribute name="{ . }" select=" namespace-uri-for-prefix(., $context)"/> </xsl:for-each> </xsl:function> </xsl:stylesheet> (drkm)[114] ~/xslt/tests$ cat copy-namespaces.xml <root xmlns:ns="my:namespace"/> (drkm)[115] ~/xslt/tests$ gexslt copy-namespaces.xsl \ copy-namespaces.xml <root ns="my:namespace" xml="http://www.w3.org/XML/1998/namespace"/> (drkm)[116] ~/xslt/tests$ Regards, --drkm ___________________________________________________________________________ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com |
From: Colin A. <col...@ho...> - 2006-12-19 07:23:00
|
>From: Florent Georges <dar...@ya...> > Hello Colin, > > I've worked a little bit on XSLT Unit, and I found a bug >(I think) related to namespace-uri-for-prefix(). I updated >my copy of Gexslt today. Here is the test case, with the BTW, you may not know that EiffelStudio 5.7 is now out of beta - in which case you should probably upgrade (not that it is relevant to this problem). >debug output: > <!-- > as="namespace()*", but namespace() is not a valid KindTest. Hm. Maybe I should check the spec. - just because I don't support the namespace axis, may not necessarily mean the kinfd test is invalid. > >gexslt: system execution failed. >Following is the set of recorded exceptions: > >------------------------------------------------------------------------------- >Class / Object Routine Nature of exception > Effect >------------------------------------------------------------------------------- >XM_XPATH_ORPHAN make @2 valid_node_kind: > ><000000000367A91C> Precondition violated. > Fail >------------------------------------------------------------------------------- >XM_XSLT_COMPILED_NAMESPACE > evaluate_item @16 ><0000000003601A8C> (From XM_XSLT_TEXT_CONSTRUCTOR) > Routine failure. > Fail >------------------------------------------------------------------------------- >XM_XSLT_COMPILED_NAMESPACE > create_iterator @4 ><0000000003601A8C> (From XM_XSLT_TEXT_CONSTRUCTOR) > Routine failure. > Fail OK. I will look into it. I assume it also fails with a production build? _________________________________________________________________ Find Singles In Your Area Now With Match.com! msnuk.match.com |
From: Florent G. <dar...@ya...> - 2006-12-18 22:59:23
|
Hi Colin, I just found a strange behaviour in Gexslt. It seems to be related to the parameter handling. Here is the test case. Note that using the string 'deep-equal' directly instead of using a parameter make the test to succeed. As well as using a variable instead of a parameter. So the last element in the result is: <expect select="$expect deep-equal $result"/> however I think it would have to be: <expect select="deep-equal($expect, $result)"/> (drkm)[75] ~/xslt/tests$ cat operator-equal.xml <test:suite xmlns:test="http://www.fgeorges.org/xslt/unit-test"> <test:tests id="hello-world-all"> <test:title>hello-world()</test:title> <test:test> <test:title>hello-world(), arity 0</test:title> <test:expect test="$test:result eq 'Hello, world!'"/> </test:test> <test:test> <test:title>hello-world(), arity 1</test:title> <test:expect select="'Hello, Jeni!'" pred="eq"/> </test:test> </test:tests> <test:tests id="false"> <test:title>False negative</test:title> <test:context select="$elem"/> <test:test> <test:expect as="element()+"> <elem2 id="id"/> </test:expect> </test:test> </test:tests> </test:suite> (drkm)[76] ~/xslt/tests$ cat operator-equal.xsl <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:test="http://www.fgeorges.org/xslt/unit-test" version="2.0"> <xsl:output indent="yes"/> <xsl:param name="expect.pred.default" select="'deep-equal'"/> <xsl:template match="/"> <root> <xsl:apply-templates/> </root> </xsl:template> <xsl:template match="node()"> <xsl:apply-templates/> </xsl:template> <xsl:template match="test:expect"> <xsl:variable name="pred-operators" select="'eq', 'is'"/> <xsl:variable name="pred" select=" if ( empty(@pred) ) then $expect.pred.default else @pred"/> <xsl:variable name="pred-call" select=" if ( $pred = $pred-operators ) then concat('$expect ', $pred, ' $result') else concat($pred, '($expect, $result)')"/> <expect select="{ $pred-call }"/> </xsl:template> </xsl:stylesheet> (drkm)[77] ~/xslt/tests$ gexslt operator-equal.xsl operator-equal.xml <?xml version="1.0" encoding="UTF-8"?> <root xmlns:test="http://www.fgeorges.org/xslt/unit-test"> <expect select="deep-equal($expect, $result)"/> <expect select="$expect eq $result"/> <expect select="$expect deep-equal $result"/> </root> Unfortunately, I wasn't able to reduce the test case furthemore. I hope it will help. Regards, --drkm ___________________________________________________________________________ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com |
From: Florent G. <dar...@ya...> - 2006-12-18 21:16:13
|
Hello Colin, I've worked a little bit on XSLT Unit, and I found a bug (I think) related to namespace-uri-for-prefix(). I updated my copy of Gexslt today. Here is the test case, with the debug output: (drkm)[55] ~/xslt/tests$ cat copy-namespaces.xml <root xmlns:ns="my:namespace"/> (drkm)[56] ~/xslt/tests$ cat copy-namespaces.xsl <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:my="my:copy-namespaces.xsl" exclude-result-prefixes="my" version="2.0"> <xsl:template match="root"> <root> <xsl:sequence select="my:copy-namespaces(.)"/> </root> </xsl:template> <!-- as="namespace()*", but namespace() is not a valid KindTest. Do the same as <xsl:copy-of select="$context/namespace::*"/>. --> <xsl:function name="my:copy-namespaces" as="node()*"> <xsl:param name="context" as="element()"/> <xsl:for-each select="in-scope-prefixes($context)"> <xsl:namespace name="{ . }" select=" namespace-uri-for-prefix(., $context)"/> </xsl:for-each> </xsl:function> </xsl:stylesheet> (drkm)[57] ~/xslt/tests$ gexslt copy-namespaces.xsl copy-namespaces.xml gexslt: system execution failed. Following is the set of recorded exceptions: ------------------------------------------------------------------------------- Class / Object Routine Nature of exception Effect ------------------------------------------------------------------------------- XM_XPATH_ORPHAN make @2 valid_node_kind: <000000000367A91C> Precondition violated. Fail ------------------------------------------------------------------------------- XM_XSLT_COMPILED_NAMESPACE evaluate_item @16 <0000000003601A8C> (From XM_XSLT_TEXT_CONSTRUCTOR) Routine failure. Fail ------------------------------------------------------------------------------- XM_XSLT_COMPILED_NAMESPACE create_iterator @4 <0000000003601A8C> (From XM_XSLT_TEXT_CONSTRUCTOR) Routine failure. Fail ------------------------------------------------------------------------------- XM_XSLT_COMPILED_FOR_EACH map @2 <0000000003606B1C> Routine failure. Fail ------------------------------------------------------------------------------- XM_XPATH_MAPPING_ITERATOR advance @35 <00000000036788FC> Routine failure. Fail ------------------------------------------------------------------------------- XM_XPATH_MAPPING_ITERATOR forth @4 <00000000036788FC> Routine failure. Fail ------------------------------------------------------------------------------- XM_XPATH_MAPPING_ITERATOR start @3 <00000000036788FC> (From XM_XPATH_SEQUENCE_ITERATOR) Routine failure. Fail ------------------------------------------------------------------------------- XM_XPATH_NODE_MAPPING_ITERATOR advance @18 <0000000003678954> Routine failure. Fail ------------------------------------------------------------------------------- XM_XPATH_NODE_MAPPING_ITERATOR forth @4 <0000000003678954> Routine failure. Fail ------------------------------------------------------------------------------- XM_XPATH_NODE_MAPPING_ITERATOR start @3 <0000000003678954> (From XM_XPATH_SEQUENCE_ITERATOR) Routine failure. Fail ------------------------------------------------------------------------------- XM_XSLT_USER_FUNCTION_CALL generate_events @18 <000000000359AEFC> (From XM_XPATH_COMPUTED_EXPRESSION) Routine failure. Fail ------------------------------------------------------------------------------- XM_XSLT_FIXED_ELEMENT generate_tail_call @26 <00000000035F5E0C> (From XM_XSLT_ELEMENT_CONSTRUCTOR) Routine failure. Fail ------------------------------------------------------------------------------- XM_XSLT_COMPILED_TEMPLATE expand @6 <00000000035E7D94> Routine failure. Fail ------------------------------------------------------------------------------- XM_XSLT_COMPILED_TEMPLATE generate_tail_call @7 <00000000035E7D94> Routine failure. Fail ------------------------------------------------------------------------------- XM_XSLT_TRANSFORMER apply_templates_2 @23 <0000000003638484> (From XM_XSLT_TEMPLATE_ROUTINES) Routine failure. Fail ------------------------------------------------------------------------------- XM_XSLT_TRANSFORMER apply_templates @33 <0000000003638484> (From XM_XSLT_TEMPLATE_ROUTINES) Routine failure. Fail ------------------------------------------------------------------------------- XM_XSLT_TRANSFORMER perform_default_action @10 <0000000003638484> (From XM_XSLT_TEMPLATE_ROUTINES) Routine failure. Fail ------------------------------------------------------------------------------- XM_XSLT_TRANSFORMER apply_templates_2 @11 <0000000003638484> (From XM_XSLT_TEMPLATE_ROUTINES) Routine failure. Fail ------------------------------------------------------------------------------- XM_XSLT_TRANSFORMER apply_templates @33 <0000000003638484> (From XM_XSLT_TEMPLATE_ROUTINES) Routine failure. Fail ------------------------------------------------------------------------------- XM_XSLT_TRANSFORMER perform_transformation @8 <0000000003638484> Routine failure. Fail ------------------------------------------------------------------------------- XM_XSLT_TRANSFORMER transform_document @21 <0000000003638484> Routine failure. Fail ------------------------------------------------------------------------------- XM_XSLT_TRANSFORMER transform @66 <0000000003638484> Routine failure. Fail ------------------------------------------------------------------------------- GEXSLT perform_transformation @23 <00000000033C003C> Routine failure. Fail ------------------------------------------------------------------------------- GEXSLT execute @44 <00000000033C003C> Routine failure. Fail ------------------------------------------------------------------------------- GEXSLT root's creation <00000000033C003C> Routine failure. Exit ------------------------------------------------------------------------------- Do you want I open an issue in the SF bug tracker ? Regards, --drkm ___________________________________________________________________________ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com |
From: Florent G. <dar...@ya...> - 2006-10-12 13:09:00
|
Colin Adams wrote: Hi > The fix for this is now committed. Sorry for the delay. Yes, your fix solves the problem. Of course, there were other bugs behind ;-). I'll try to post a description ASAP. > Please check and update the tracker. I'm not able to connect to SF.net now, so I can't upload the issue status. I guess SF.net have some trouble o maintenance now. I'll try again later. Thanks, Colin. Regards, --drkm ___________________________________________________________________________ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Demandez à ceux qui savent sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com |
From: Colin A. <col...@ho...> - 2006-10-09 10:21:34
|
The fix for this is now committed. Please check and update the tracker. >From: Florent Georges <dar...@ya...> >Reply-To: ges...@li... >To: Gestalt ML <ges...@li...> >Subject: [Gestalt-users] xsl:result-document cannot open a file >Date: Thu, 28 Sep 2006 22:30:55 +0200 (CEST) > > Hi > > I tried to use xsl:result-document, and I give a trange >error: > > Fatal error: >http://www.gobosoft.com/eiffel/gobo/gexslt/extension#OUTPUT_RESOLVER_ERROR: >Unable to open file://localhost/c%3A/some path/gexslt-result-doc.xml > > My stylesheet is: > > <xsl:transform > xmlns:xsl="http://www.w3.org/1999/XSL/Transform" > version="2.0"> > > <xsl:template name="main"> > <xsl:result-document href="gexslt-result-doc.xml"> > <yo/> > </xsl:result-document> > </xsl:template> > > </xsl:transform> > > I tried the following URIs: > > - gexslt-result-doc.xml > - C:/some path/gexslt-result-doc.xml > - file://localhost/c%3A/some path/gexslt-result-doc.xml > - file://localhost/c%3A/some+path/gexslt-result-doc.xml > - file://localhost/c%3A/some%20path/gexslt-result-doc.xml > >with lowcase and upcase "C:", all gave the same error. If >you confirm it is a bug, I'll open a ticket on the tracker. > > Regards, > >--drkm > > > > > > > > > > > > > > > > > > > > > > > > > > >___________________________________________________________________________ >Découvrez un nouveau moyen de poser toutes vos questions quelque soit le >sujet ! >Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et >vos expériences. >http://fr.answers.yahoo.com > > >------------------------------------------------------------------------- >Take Surveys. Earn Cash. Influence the Future of IT >Join SourceForge.net's Techsay panel and you'll get the chance to share >your >opinions on IT & business topics through brief surveys -- and earn cash >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >_______________________________________________ >Gestalt-users mailing list >Ges...@li... >https://lists.sourceforge.net/lists/listinfo/gestalt-users _________________________________________________________________ The new Windows Live Toolbar helps you guard against viruses http://toolbar.live.com/?mkt=en-gb |
From: Colin A. <col...@ho...> - 2006-09-29 09:47:46
|
The problem is in the relative URI resolution under Windows. I don't know whether the problem is actually in class GEXSLT or class UT_URI. It dependes upon whether or not the second colon should be escaped in the URI: file:///D:/gexslt or not. When I coded GEXSLT, I assumed it didn't, as the colon is not special after the initial colon has been seen. But UT_URI requires that all excluded characters have been escaped, and that includes colon. But I am coming round to that viewpoint, as the string: "fred:jim" if treated as a relative URI, then the colon must be escaped, as otherwise it looks like an absolute URI of scheme fred. I'm cross-posting this to the gobo-develop list to see if Franck agrees with my diagnosis. >From: "Colin Adams" <col...@ho...> >Reply-To: ges...@li... >To: ges...@li... >Subject: Re: [Gestalt-users] xsl:result-document cannot open a file >Date: Fri, 29 Sep 2006 10:24:17 +0100 > >As I suspected, there is no problem on Linux. >I shall now try it on Windows. > > > >From: Florent Georges <dar...@ya...> > >Reply-To: ges...@li... > >To: ges...@li... > >Subject: Re: [Gestalt-users] xsl:result-document cannot open a file > >Date: Fri, 29 Sep 2006 10:52:16 +0200 (CEST) > > > >Colin Adams wrote: > > > > Hi > > > > > It seems to me that this is the same bug as you reported > > > earlier in the week. > > > > Mmh, you're right, I forgot that :-( > > > > > So just update that tracker with the information below. > > > > Just done. > >_________________________________________________________________ >Download the new Windows Live Toolbar, including Desktop search! >http://toolbar.live.com/?mkt=en-gb > > >------------------------------------------------------------------------- >Take Surveys. Earn Cash. Influence the Future of IT >Join SourceForge.net's Techsay panel and you'll get the chance to share >your >opinions on IT & business topics through brief surveys -- and earn cash >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >_______________________________________________ >Gestalt-users mailing list >Ges...@li... >https://lists.sourceforge.net/lists/listinfo/gestalt-users _________________________________________________________________ Windows Live Messenger has arrived. Click here to download it for free! http://imagine-msn.com/messenger/launch80/?locale=en-gb |
From: Colin A. <col...@ho...> - 2006-09-29 09:24:23
|
As I suspected, there is no problem on Linux. I shall now try it on Windows. >From: Florent Georges <dar...@ya...> >Reply-To: ges...@li... >To: ges...@li... >Subject: Re: [Gestalt-users] xsl:result-document cannot open a file >Date: Fri, 29 Sep 2006 10:52:16 +0200 (CEST) > >Colin Adams wrote: > > Hi > > > It seems to me that this is the same bug as you reported > > earlier in the week. > > Mmh, you're right, I forgot that :-( > > > So just update that tracker with the information below. > > Just done. _________________________________________________________________ Download the new Windows Live Toolbar, including Desktop search! http://toolbar.live.com/?mkt=en-gb |
From: Florent G. <dar...@ya...> - 2006-09-29 08:52:25
|
Colin Adams wrote: Hi > It seems to me that this is the same bug as you reported > earlier in the week. Mmh, you're right, I forgot that :-( > So just update that tracker with the information below. Just done. Regards, --drkm ___________________________________________________________________________ Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. http://fr.answers.yahoo.com |
From: Colin A. <col...@ho...> - 2006-09-29 06:55:19
|
It seems to me that this is the same bug as you reported earlier in the week. So just update that tracker with the information below. >From: Florent Georges <dar...@ya...> >Reply-To: ges...@li... >To: Gestalt ML <ges...@li...> >Subject: [Gestalt-users] xsl:result-document cannot open a file >Date: Thu, 28 Sep 2006 22:30:55 +0200 (CEST) > > Hi > > I tried to use xsl:result-document, and I give a trange >error: > > Fatal error: >http://www.gobosoft.com/eiffel/gobo/gexslt/extension#OUTPUT_RESOLVER_ERROR: >Unable to open file://localhost/c%3A/some path/gexslt-result-doc.xml > > My stylesheet is: > > <xsl:transform > xmlns:xsl="http://www.w3.org/1999/XSL/Transform" > version="2.0"> > > <xsl:template name="main"> > <xsl:result-document href="gexslt-result-doc.xml"> > <yo/> > </xsl:result-document> > </xsl:template> > > </xsl:transform> > > I tried the following URIs: > > - gexslt-result-doc.xml > - C:/some path/gexslt-result-doc.xml > - file://localhost/c%3A/some path/gexslt-result-doc.xml > - file://localhost/c%3A/some+path/gexslt-result-doc.xml > - file://localhost/c%3A/some%20path/gexslt-result-doc.xml > >with lowcase and upcase "C:", all gave the same error. If >you confirm it is a bug, I'll open a ticket on the tracker. > > Regards, > >--drkm > > > > > > > > > > > > > > > > > > > > > > > > > > >___________________________________________________________________________ >Découvrez un nouveau moyen de poser toutes vos questions quelque soit le >sujet ! >Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et >vos expériences. >http://fr.answers.yahoo.com > > >------------------------------------------------------------------------- >Take Surveys. Earn Cash. Influence the Future of IT >Join SourceForge.net's Techsay panel and you'll get the chance to share >your >opinions on IT & business topics through brief surveys -- and earn cash >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >_______________________________________________ >Gestalt-users mailing list >Ges...@li... >https://lists.sourceforge.net/lists/listinfo/gestalt-users _________________________________________________________________ The new Windows Live Toolbar helps you guard against viruses http://toolbar.live.com/?mkt=en-gb |