gestalt-users Mailing List for Gestalt XSLT 2.0 processor (Page 5)
Status: Alpha
Brought to you by:
colin-adams
Menu
▾
▴
gestalt-users — Using Gestalt
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...> - 2006-09-08 11:45:00
|
>>>>> "Florent" == Florent Georges <dar...@ya...> writes:
Florent> Colin Paul Adams wrote: Hi Colin.
Florent> Thanks for your help.
>> >>>>> "Florent" == Florent Georges writes:
Florent> http://www.fgeorges.org/tmp/hello-world.xsl
Florent> http://www.fgeorges.org/tmp/test-hello-world.xts.xsl
>> I trust you meant stylesheet + input?
Florent> Nop. The first is the input, the second is the
Florent> stylesheet.
The reason I thought otherwise was because I got a load of compile
errors.
This turns out to be:
1) gestalt cannot currently handle chunked http encoding (I have
reported this to the author of the library, who will fix it), so I
had to download your scripts and use gexslt.
2) The hello.xsl imports others.
3) with a hard-coded path of /home/src/
So i will edit this, and debug.
A self-contained download would be more useful in future.
--
Colin Adams
Preston Lancashire
|
|
From: Colin A. <col...@ho...> - 2006-09-07 08:43:53
|
I'll look into this tomorrow. >From: Florent Georges <dar...@ya...> >Reply-To: ges...@li... >To: ges...@li... >Subject: Re: [Gestalt-users] Gexslt crash with xsl:import: URI format? >Date: Thu, 7 Sep 2006 10:39:34 +0200 (CEST) > >Colin Paul Adams wrote: > > Hi Colin. > > Thanks for your help. > > > >>>>> "Florent" == Florent Georges writes: > > > Florent> http://www.fgeorges.org/tmp/hello-world.xsl > > Florent> http://www.fgeorges.org/tmp/test-hello-world.xts.xsl > > > I trust you meant stylesheet + input? > > Nop. The first is the input, the second is the >stylesheet. In two words, hello-world.xsl is a stylesheet >module. A test suite has been wrtitten to test this module, >and generated test-hello-world.xts.xsl. Then to execute the >test suite, the tested stylesheet is transformed with the >generated stylesheet. > > > If not, then I gets dozens of compile errors. > > I recompiled Gexslt with a fresh check-out (a few hours >ago) and I get now: > ># gexslt test-hello-world.xts.xsl hello-world.xsl > ><?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" >href="http://www.fgeorges.org/xslt-unit/report-to-html.xsl"?> ><report xmlns:xsl="http://www.w3.org/1999/XSL/Transform" >tested="hello-world.xsl" >tested-absolute=".../xslt-unit/test/hello-world.xsl" >date="2006-08-30T22:36:58.187+02:00"> > <variable name="elem" as="element()"> > <elem id="id"/> > </variable>Tests: hello-world(), arity 0 > <tests id="hello-world-0"> > <title>hello-world(), arity 0</title> > <expect-selected>Hello, world!</expect-selected> >gexslt: system execution failed. >Following is the set of recorded exceptions: > >------------------------------------------------------------------------------- >Class / Object Routine Nature of exception > Effect >------------------------------------------------------------------------------- >GEXSLT root's creation Segmentation violation: ><0000000002324704> Operating system signal. > Exit >------------------------------------------------------------------------------- >GEXSLT root's creation ><0000000002324704> Routine failure. > Exit >------------------------------------------------------------------------------- > > I don't know how I could find more information. > > Hope that helps. > > 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 > > >------------------------------------------------------------------------- >Using Tomcat but need to do more? Need to support web services, security? >Get stuff done quickly with pre-integrated technology to make your job >easier >Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >_______________________________________________ >Gestalt-users mailing list >Ges...@li... >https://lists.sourceforge.net/lists/listinfo/gestalt-users _________________________________________________________________ Be the first to hear what's new at MSN - sign up to our free newsletters! http://www.msn.co.uk/newsletters |
|
From: Florent G. <dar...@ya...> - 2006-09-07 08:39:46
|
Colin Paul Adams wrote: Hi Colin. Thanks for your help. > >>>>> "Florent" == Florent Georges writes: > Florent> http://www.fgeorges.org/tmp/hello-world.xsl > Florent> http://www.fgeorges.org/tmp/test-hello-world.xts.xsl > I trust you meant stylesheet + input? Nop. The first is the input, the second is the stylesheet. In two words, hello-world.xsl is a stylesheet module. A test suite has been wrtitten to test this module, and generated test-hello-world.xts.xsl. Then to execute the test suite, the tested stylesheet is transformed with the generated stylesheet. > If not, then I gets dozens of compile errors. I recompiled Gexslt with a fresh check-out (a few hours ago) and I get now: # gexslt test-hello-world.xts.xsl hello-world.xsl <?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="http://www.fgeorges.org/xslt-unit/report-to-html.xsl"?> <report xmlns:xsl="http://www.w3.org/1999/XSL/Transform" tested="hello-world.xsl" tested-absolute=".../xslt-unit/test/hello-world.xsl" date="2006-08-30T22:36:58.187+02:00"> <variable name="elem" as="element()"> <elem id="id"/> </variable>Tests: hello-world(), arity 0 <tests id="hello-world-0"> <title>hello-world(), arity 0</title> <expect-selected>Hello, world!</expect-selected> gexslt: system execution failed. Following is the set of recorded exceptions: ------------------------------------------------------------------------------- Class / Object Routine Nature of exception Effect ------------------------------------------------------------------------------- GEXSLT root's creation Segmentation violation: <0000000002324704> Operating system signal. Exit ------------------------------------------------------------------------------- GEXSLT root's creation <0000000002324704> Routine failure. Exit ------------------------------------------------------------------------------- I don't know how I could find more information. Hope that helps. 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 P. A. <co...@co...> - 2006-09-01 15:53:59
|
>>>>> "Florent" == Florent Georges <dar...@ya...> writes:
>> so that it looks like:
>> -- attributes_prepared: attributes_prepared
Florent> Done.
>> Then compile afresh (geant compile_ise_debug - that should take
>> only a few seconds, as it will be an incremental compile), and
>> run the test again, posting the new stack trace here.
Florent> Running the new build on the reduced sample I sent
Florent> today (with the three little files), I get the following
Florent> error:
Florent> gexslt: system execution failed. Following is the set of
Florent> recorded exceptions:
Florent> -------------------------------------------------------------------------------
Florent> Class / Object Routine Nature of exception Effect
Florent> -------------------------------------------------------------------------------
Florent> XM_XSLT_FUNCTION prepare_attributes @6 not_excluded:
Florent> <000000000349B80C> Precondition violated. Fail
Florent> So in the same file I commented out the following line
Florent> in function_fingerprint:
Florent> if not attributes_prepared then prepare_attributes
Florent> end
Which is the wrong try.
In general in Eiffel, if a routine has a precondition, you must first
check that you can meet the pre-condition before you may call the
routine.
So the obvious try would be:
if not attributes_prepared and not is_excluded then
prepare_attributes
end
It looks like that would have been sufficient to fix your problem.
But I didn't do this.
The is_excluded was my way of implementing [xsl:]use-when conditional
compilation - if the use-when clause returns false, then I marked the
element and is_excluded. So whole parts of the tree are logically
excluded.
Hence the pre-conditions.
But it's slightly error prone. Rather than wait for another such error
to be uncovered, or to write a proof checker, I now (as of today)
physically remove the excluded elements prior to begining the compile
process. (MHK does it with a filter, but that is conceptually harder -
I prefer the straight-forward approach)
This seems to fix your problem.
Florent> Then the transformation (on the simplified sample) run
Florent> at the end, and produced no output
I get that too.
Florent> nodes, that is correct). Then I came back to the
Florent> original files, and there I got the following stacktrace
Florent> (and biginning of output):
Florent> I let you deduce the conclusion ;-). I put the two
Florent> files (input + stylesheet) there:
Florent> http://www.fgeorges.org/tmp/hello-world.xsl
Florent> http://www.fgeorges.org/tmp/test-hello-world.xts.xsl
I trust you meant stylesheet + input?
If not, then I gets dozens of compile errors. If you did, then I get
no errors, and a load of output looking like this:
<?xml version="1.0" encoding="UTF-8"?>
<elem1 xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:hw="http://www.fgeorges.org/hello-world"/><elem2 xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:hw="http://www.fgeorges.org/hello-world" id="id"/>
type="text/xsl" href="http://www.fgeorges.org/xslt-unit/report-to-html.xsl"
<elem1 xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:hw="http://www.fgeorges.org/hello-world"/><elem2 xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:hw="http://www.fgeorges.org/hello-world" id="id"/>
Tests:
hello-world(), arity 0
hello-world(), arity 0
Tests:
hello-world(), arity 1
hello-world(), arity 1
Tests:
hello-world()
hello-world()
Tests:
'elem' template rule
'elem' template rule
Tests:
False negative
False negative
test:
[success]
[FAILED !]
test:
[success]
[FAILED !]
test:
hello-world(), arity 0
[success]
[FAILED !]
hello-world(), arity 0
test:
hello-world(), arity 1
[success]
[FAILED !]
hello-world(), arity 1
test:
'elem' #1
[success]
[FAILED !]
'elem' #1
test:
'elem' #2
[success]
[FAILED !]
'elem' #2
test:
[success]
[FAILED !]
Since this is not well-formd XML, I was dubious, but as Saxon 8.7.1
produces identical output, I assume the problem is fixed.
I should have this checked in to CVS before Tuesday.
remember, the procedure to update is:
cd %GOBO%
cvs update (however you do this in windows)
geant install
Then re-compile gexslt with:
cd %GOBO\src\gexslt
geant compile
then copy gexslt.exe to %GOBO\bin
If by any chance I haven't checked in by then, you can try the fix I
showed you above (and repeat if any further instances arise).
--
Colin Adams
Preston Lancashire
|
|
From: Florent G. <dar...@ya...> - 2006-08-30 22:58:28
|
Colin Adams wrote:
Hi
> I have just looked at routine `arity' (using view CVS
> repository) and it doesn't seem that the pre-condition is
> necessary. Can you comment it out, and try again using the
> debugging-version of gexslt (as this certainly isn't the
> cause of your problem)?
Of course.
> To do that, find xm_xslt_function.e in
> %GOBO%/library/xml/xslt/style, search for:
> arity:
> and then add two hyphens (--) to the begining of the line:
> attributes_prepared: attributes_prepared
> so that it looks like:
> -- attributes_prepared: attributes_prepared
Done.
> Then compile afresh (geant compile_ise_debug - that should
> take only a few seconds, as it will be an incremental
> compile), and run the test again, posting the new stack
> trace here.
Running the new build on the reduced sample I sent today
(with the three little files), I get the following error:
gexslt: system execution failed.
Following is the set of recorded exceptions:
-------------------------------------------------------------------------------
Class / Object Routine Nature of exception
Effect
-------------------------------------------------------------------------------
XM_XSLT_FUNCTION prepare_attributes @6 not_excluded:
<000000000349B80C> Precondition violated.
Fail
-------------------------------------------------------------------------------
XM_XSLT_FUNCTION function_fingerprint @5
<000000000349B80C> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_FUNCTION validate @11
<000000000351B36C> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_FUNCTION validate_subtree @9
<000000000351B36C> (From XM_XSLT_STYLE_ELEMENT)
Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_STYLESHEET preprocess @21
<00000000033FEF4C> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_STYLESHEET_COMPILER
create_style_sheet_executable @16
<0000000003332984> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_STYLESHEET_COMPILER
prepare @6
<0000000003332984> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_TRANSFORMER_FACTORY
create_new_transformer @8
<0000000003329104> Routine failure.
Fail
-------------------------------------------------------------------------------
GEXSLT process_uris @38
<000000000331003C> Routine failure.
Fail
-------------------------------------------------------------------------------
GEXSLT execute @42
<000000000331003C> Routine failure.
Fail
-------------------------------------------------------------------------------
GEXSLT root's creation
<000000000331003C> Routine failure.
Exit
-------------------------------------------------------------------------------
So in the same file I commented out the following line in
function_fingerprint:
if not attributes_prepared then prepare_attributes end
Then the transformation (on the simplified sample) run at
the end, and produced no output (only the whitespace nodes,
that is correct). Then I came back to the original files,
and there I got the following stacktrace (and biginning of
output):
$ gexslt test/test-hello-world.xts.xsl test/hello-world.xsl
<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl"
href="htt
p://www.fgeorges.org/xslt-unit/report-to-html.xsl"?>
<report xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
tested="hello-world.xsl
"
tested-absolute="file:/c:/Documents%20and%20Settings/Florent%20Georges/My%20Do
cuments/xslt/xslt-unit/test/hello-world.xsl"
date="2006-08-30T22:36:58.187+02:00
">
<variable name="elem" as="element()">
<elem id="id"/>
</variable>Tests: hello-world(), arity 0
<tests id="hello-world-0">
<title>hello-world(), arity 0</title>
<expect-selected>Hello, world!</expect-selected>
gexslt: system execution failed.
Following is the set of recorded exceptions:
-------------------------------------------------------------------------------
Class / Object Routine Nature of exception
Effect
-------------------------------------------------------------------------------
XM_XSLT_USER_FUNCTION_CALL
create_node_iterator @1
node_sequence:
<0000000003325B4C> Precondition violated.
Fail
-------------------------------------------------------------------------------
XM_XSLT_COMPILED_FOR_EACH
map_nodes @2
<0000000003325A14> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XPATH_NODE_MAPPING_ITERATOR
advance @26
<0000000003533F34> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XPATH_NODE_MAPPING_ITERATOR
forth @4
<0000000003533F34> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XPATH_NODE_MAPPING_ITERATOR
start @3
<0000000003533F34> (From XM_XPATH_SEQUENCE_ITERATOR)
Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XPATH_PROGRESSIVE_ITERATOR
forth @9
<0000000003533FEC> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XPATH_PROGRESSIVE_ITERATOR
start @3
<0000000003533FEC> (From XM_XPATH_SEQUENCE_ITERATOR)
Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XPATH_SINGLETON_ATOMIZER
evaluate_item @8
<000000000332676C> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XPATH_VALUE_COMPARISON
calculate_effective_boolean_value @11
<000000000332663C> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XPATH_IF_EXPRESSION
evaluate_item @5
<000000000332650C> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XPATH_IF_EXPRESSION
eagerly_evaluate @49
<000000000332650C> (From XM_XPATH_EXPRESSION)
Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XPATH_IF_EXPRESSION
lazily_evaluate @13
<000000000332650C> (From XM_XPATH_COMPUTED_EXPRESSION)
Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XPATH_LET_EXPRESSION
process @7
<000000000332638C> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_BLOCK process_leaving_tail @13
<0000000003325064> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_BLOCK process @7
<0000000003325064> (From XM_XSLT_INSTRUCTION)
Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XPATH_LET_EXPRESSION
process @17
<0000000003325314> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_COMPILED_TEMPLATE
expand @6
<000000000335A9BC> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_COMPILED_CALL
process @10
<000000000335A884> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_COMPILED_CALL
process_leaving_tail @5
<000000000335A884> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_BLOCK process_leaving_tail @11
<0000000003359E6C> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_BLOCK process @7
<0000000003359E6C> (From XM_XSLT_INSTRUCTION)
Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_FIXED_ELEMENT
process_leaving_tail @22
<0000000003359D24> (From XM_XSLT_ELEMENT_CONSTRUCTOR)
Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_BLOCK process_leaving_tail @11
<000000000335916C> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_COMPILED_TEMPLATE
expand @4
<000000000335913C> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_COMPILED_CALL
process @10
<0000000003359004> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_COMPILED_CALL
process_leaving_tail @5
<0000000003359004> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_BLOCK process_leaving_tail @11
<00000000033576D4> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_BLOCK process @7
<00000000033576D4> (From XM_XSLT_INSTRUCTION)
Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_FIXED_ELEMENT
process_leaving_tail @22
<000000000335758C> (From XM_XSLT_ELEMENT_CONSTRUCTOR)
Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_BLOCK process_leaving_tail @11
<0000000003356A54> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_COMPILED_TEMPLATE
expand @4
<0000000003356A24> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_COMPILED_TEMPLATE
process_leaving_tail @5
<0000000003356A24> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_TRANSFORMER apply_templates @28
<0000000003470674> (From XM_XSLT_TEMPLATE_ROUTINES)
Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_TRANSFORMER perform_transformation @7
<0000000003470674> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_TRANSFORMER transform_document @19
<0000000003470674> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_TRANSFORMER transform @66
<0000000003470674> Routine failure.
Fail
-------------------------------------------------------------------------------
GEXSLT perform_transformation @32
<0000000003F9795C> Routine failure.
Fail
-------------------------------------------------------------------------------
GEXSLT execute @44
<0000000003F9795C> Routine failure.
Fail
-------------------------------------------------------------------------------
GEXSLT root's creation
<0000000003F9795C> Routine failure.
Exit
-------------------------------------------------------------------------------
I let you deduce the conclusion ;-). I put the two files
(input + stylesheet) there:
http://www.fgeorges.org/tmp/hello-world.xsl
http://www.fgeorges.org/tmp/test-hello-world.xts.xsl
> Your first lesson in Eiffel :-)
Ayup.
> Note that the keyword "require" on the line above
> introduces the pre-conditions for the routine.
Yes, I guessed that. The only thing I know about Eiffel,
I must admit, is that it has native support for the
programing by contract.
As I said, unfortunately, I'll not be able to follow any
discussion until the 5th of September at least (maybe a
little tomorrow). But I'll check the Gestalt mailing list
on the 5th.
Enjoy ;-)
Regards,
--drkm
p5.vert.ukl.yahoo.com uncompressed/chunked Wed Aug 30 12:13:41 GMT 2006
___________________________________________________________________________
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-08-30 19:38:33
|
I have just looked at routine `arity' (using view CVS repository) and it doesn't seem that the pre-condition is necessary. Can you comment it out, and try again using the debugging-version of gexslt (as this certainly isn't the cause of your problem)? To do that, find xm_xslt_function.e in %GOBO%/library/xml/xslt/style, search for: arity: and then add two hyphens (--) to the begining of the line: attributes_prepared: attributes_prepared so that it looks like: -- attributes_prepared: attributes_prepared Then compile afresh (geant compile_ise_debug - that should take only a few seconds, as it will be an incremental compile), and run the test again, posting the new stack trace here. Your first lesson in Eiffel :-) Note that the keyword "require" on the line above introduces the pre-conditions for the routine. >From: Florent Georges <dar...@ya...> >Reply-To: ges...@li... >To: ges...@li... >Subject: Re: [Gestalt-users] Gexslt crash with xsl:import: URI format? >Date: Wed, 30 Aug 2006 11:47:42 +0200 (CEST) > >Colin Adams wrote: > > > First a couple of notes about file: URIs: > > > [...] > > > But I doubt if any of these is the cause of your problem. > > I do too, since in the minimal example the URIs are: > > <xsl:import href="function-available-2.xsl"/> > <xsl:import href="hello-world.xsl"/> > > I guess these are correctly managed ;-) > > > I shan't be able to attempt debugging until I get home on > > friday. What would be helpful would be if you could do > > the following: > > > 1) cd %GOBO%\src\gexslt > > 2) geant compile_debug_ise > > 3) .\gexslt <your command line arguments> > > It build at the first try :-) > > > This will run much slower, but will produce a complete > > stack trace - I may be able to tell from the stack trace > > alone what the problem is. > > Here is the stacktrace: > >gexslt: system execution failed. >Following is the set of recorded exceptions: > >------------------------------------------------------------------------------- >Class / Object Routine Nature of exception > Effect >------------------------------------------------------------------------------- >XM_XSLT_FUNCTION arity @3 attributes_prepared: ><000000000349B80C> Precondition violated. > Fail >------------------------------------------------------------------------------- >XM_XSLT_FUNCTION validate @11 ><000000000351AEEC> Routine failure. > Fail >------------------------------------------------------------------------------- >XM_XSLT_FUNCTION validate_subtree @9 ><000000000351AEEC> (From XM_XSLT_STYLE_ELEMENT) > Routine failure. > Fail >------------------------------------------------------------------------------- >XM_XSLT_STYLESHEET preprocess @21 ><00000000033FEF4C> Routine failure. > Fail >------------------------------------------------------------------------------- >XM_XSLT_STYLESHEET_COMPILER > create_style_sheet_executable @16 ><0000000003332984> Routine failure. > Fail >------------------------------------------------------------------------------- >XM_XSLT_STYLESHEET_COMPILER > prepare @6 ><0000000003332984> Routine failure. > Fail >------------------------------------------------------------------------------- >XM_XSLT_TRANSFORMER_FACTORY > create_new_transformer @8 ><0000000003329104> Routine failure. > Fail >------------------------------------------------------------------------------- >GEXSLT process_uris @38 ><000000000331003C> Routine failure. > Fail >------------------------------------------------------------------------------- >GEXSLT execute @42 ><000000000331003C> Routine failure. > Fail >------------------------------------------------------------------------------- >GEXSLT root's creation ><000000000331003C> Routine failure. > Exit >------------------------------------------------------------------------------- > > You said you'll can not look at this before Friday. I'll >be not at home from tomorrow to Tuesday. So I'll not be able >to give you quick feedback if needed (and Tuesday I'll have >to clean my mailbox ;-o). > > Regards, > >--drkm > > > > > > > > > > > > > > > > > > > > > > > > > p2.vert.ukl.yahoo.com uncompressed/chunked Wed Aug 30 07:13:40 GMT 2006 > > >___________________________________________________________________________ >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 > > >------------------------------------------------------------------------- >Using Tomcat but need to do more? Need to support web services, security? >Get stuff done quickly with pre-integrated technology to make your job >easier >Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >_______________________________________________ >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-08-30 10:12:21
|
Well, this is clearly a bug that has to be fixed - it may or may not be the bug you experience with the finalized (Eiffel talk for fully optimized, with no assertion checking) version, but I shall fix that bug on Friday, and then we can see after that. >From: Florent Georges <dar...@ya...> >Reply-To: ges...@li... >To: ges...@li... >Subject: Re: [Gestalt-users] Gexslt crash with xsl:import: URI format? >Date: Wed, 30 Aug 2006 11:47:42 +0200 (CEST) > >Colin Adams wrote: > > > First a couple of notes about file: URIs: > > > [...] > > > But I doubt if any of these is the cause of your problem. > > I do too, since in the minimal example the URIs are: > > <xsl:import href="function-available-2.xsl"/> > <xsl:import href="hello-world.xsl"/> > > I guess these are correctly managed ;-) > > > I shan't be able to attempt debugging until I get home on > > friday. What would be helpful would be if you could do > > the following: > > > 1) cd %GOBO%\src\gexslt > > 2) geant compile_debug_ise > > 3) .\gexslt <your command line arguments> > > It build at the first try :-) > > > This will run much slower, but will produce a complete > > stack trace - I may be able to tell from the stack trace > > alone what the problem is. > > Here is the stacktrace: > >gexslt: system execution failed. >Following is the set of recorded exceptions: > >------------------------------------------------------------------------------- >Class / Object Routine Nature of exception > Effect >------------------------------------------------------------------------------- >XM_XSLT_FUNCTION arity @3 attributes_prepared: ><000000000349B80C> Precondition violated. > Fail >------------------------------------------------------------------------------- >XM_XSLT_FUNCTION validate @11 ><000000000351AEEC> Routine failure. > Fail >------------------------------------------------------------------------------- >XM_XSLT_FUNCTION validate_subtree @9 ><000000000351AEEC> (From XM_XSLT_STYLE_ELEMENT) > Routine failure. > Fail >------------------------------------------------------------------------------- >XM_XSLT_STYLESHEET preprocess @21 ><00000000033FEF4C> Routine failure. > Fail >------------------------------------------------------------------------------- >XM_XSLT_STYLESHEET_COMPILER > create_style_sheet_executable @16 ><0000000003332984> Routine failure. > Fail >------------------------------------------------------------------------------- >XM_XSLT_STYLESHEET_COMPILER > prepare @6 ><0000000003332984> Routine failure. > Fail >------------------------------------------------------------------------------- >XM_XSLT_TRANSFORMER_FACTORY > create_new_transformer @8 ><0000000003329104> Routine failure. > Fail >------------------------------------------------------------------------------- >GEXSLT process_uris @38 ><000000000331003C> Routine failure. > Fail >------------------------------------------------------------------------------- >GEXSLT execute @42 ><000000000331003C> Routine failure. > Fail >------------------------------------------------------------------------------- >GEXSLT root's creation ><000000000331003C> Routine failure. > Exit >------------------------------------------------------------------------------- > > You said you'll can not look at this before Friday. I'll >be not at home from tomorrow to Tuesday. So I'll not be able >to give you quick feedback if needed (and Tuesday I'll have >to clean my mailbox ;-o). > > Regards, > >--drkm > > > > > > > > > > > > > > > > > > > > > > > > > p2.vert.ukl.yahoo.com uncompressed/chunked Wed Aug 30 07:13:40 GMT 2006 > > >___________________________________________________________________________ >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 > > >------------------------------------------------------------------------- >Using Tomcat but need to do more? Need to support web services, security? >Get stuff done quickly with pre-integrated technology to make your job >easier >Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >_______________________________________________ >Gestalt-users mailing list >Ges...@li... >https://lists.sourceforge.net/lists/listinfo/gestalt-users _________________________________________________________________ Be the first to hear what's new at MSN - sign up to our free newsletters! http://www.msn.co.uk/newsletters |
|
From: Florent G. <dar...@ya...> - 2006-08-30 09:57:04
|
Colin Adams wrote: > If you're feeling really brave, you might try compiling > gestalt itself. That requires the latest eposix beta - I > don't know if it will work with 5.7 or not. I don't know if I'm brave, but since I now succeeded to compile Gexslt, I feel able to do everything ;-) But not before the next week, in the best case :-( Regards, --drkm p3.vert.ukl.yahoo.com uncompressed/chunked Wed Aug 30 06:13:41 GMT 2006 ___________________________________________________________________________ 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: Florent G. <dar...@ya...> - 2006-08-30 09:47:50
|
Colin Adams wrote:
> First a couple of notes about file: URIs:
> [...]
> But I doubt if any of these is the cause of your problem.
I do too, since in the minimal example the URIs are:
<xsl:import href="function-available-2.xsl"/>
<xsl:import href="hello-world.xsl"/>
I guess these are correctly managed ;-)
> I shan't be able to attempt debugging until I get home on
> friday. What would be helpful would be if you could do
> the following:
> 1) cd %GOBO%\src\gexslt
> 2) geant compile_debug_ise
> 3) .\gexslt <your command line arguments>
It build at the first try :-)
> This will run much slower, but will produce a complete
> stack trace - I may be able to tell from the stack trace
> alone what the problem is.
Here is the stacktrace:
gexslt: system execution failed.
Following is the set of recorded exceptions:
-------------------------------------------------------------------------------
Class / Object Routine Nature of exception
Effect
-------------------------------------------------------------------------------
XM_XSLT_FUNCTION arity @3 attributes_prepared:
<000000000349B80C> Precondition violated.
Fail
-------------------------------------------------------------------------------
XM_XSLT_FUNCTION validate @11
<000000000351AEEC> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_FUNCTION validate_subtree @9
<000000000351AEEC> (From XM_XSLT_STYLE_ELEMENT)
Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_STYLESHEET preprocess @21
<00000000033FEF4C> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_STYLESHEET_COMPILER
create_style_sheet_executable @16
<0000000003332984> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_STYLESHEET_COMPILER
prepare @6
<0000000003332984> Routine failure.
Fail
-------------------------------------------------------------------------------
XM_XSLT_TRANSFORMER_FACTORY
create_new_transformer @8
<0000000003329104> Routine failure.
Fail
-------------------------------------------------------------------------------
GEXSLT process_uris @38
<000000000331003C> Routine failure.
Fail
-------------------------------------------------------------------------------
GEXSLT execute @42
<000000000331003C> Routine failure.
Fail
-------------------------------------------------------------------------------
GEXSLT root's creation
<000000000331003C> Routine failure.
Exit
-------------------------------------------------------------------------------
You said you'll can not look at this before Friday. I'll
be not at home from tomorrow to Tuesday. So I'll not be able
to give you quick feedback if needed (and Tuesday I'll have
to clean my mailbox ;-o).
Regards,
--drkm
p2.vert.ukl.yahoo.com uncompressed/chunked Wed Aug 30 07:13:40 GMT 2006
___________________________________________________________________________
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-08-30 07:25:04
|
Hello Florent,
First a couple of notes about file: URIs:
1) There is a design fault in the Eiffel class UT_URI that incorrectly
de-canonicalizes file:/// to file://localhost/. The author of this class has
agreed (finally!) that it is a bug, and I shall correct it sometime, when i
remember (unless he does it first).
2) As far as I can tell from the spec, it is not necessary to escape the
colon after the colon for the initial scheme has been seen. Do you know what
other URi processors do in this situation on Windows?
3) Spaces should be replaced with %20, not +
But I doubt if any of these is the cause of your problem.
I shan't be able to attempt debugging until I get home on friday. What would
be helpful would be if you could do the following:
1) cd %GOBO%\src\gexslt
2) geant compile_debug_ise
3) .\gexslt <your command line arguments>
This will run much slower, but will produce a complete stack trace - I may
be able to tell from the stack trace alone what the problem is.
>From: Florent Georges <dar...@ya...>
>Florent Georges wrote:
>
> Colin,
>
> > The hidden "/.../" part in the URI above is correct
> > (refers to an existing file), but with spaces replaced by
> > the character "+".
>
> I was wrong thinking the error was because the @href.
>Sorry. I was able to reproduce the problem, only with a
>main XSLT that imports two other XSLT (one with a @use-when
>on function-available('saxon:type-annotation')):
>
> > cat function-available.xsl
> <xsl:transform
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> version="2.0">
>
> <xsl:import href="function-available-2.xsl"/>
> <xsl:import href="hello-world.xsl"/>
>
> </xsl:transform>
>
> > cat function-available-2.xsl
> <xsl:transform
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> xmlns:my="function-available.xsl"
> version="2.0">
>
> <xsl:function name="my:type-annotation-catch"
> xmlns:saxon="http://saxon.sf.net/"
>
>use-when="function-available('saxon:type-annotation')">
> </xsl:function>
>
> </xsl:transform>
>
> > cat hello-world.xsl
> <xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> xmlns:xs="http://www.w3.org/2001/XMLSchema"
> xmlns:hw="http://www.fgeorges.org/hello-world"
> version="2.0">
>
> <xsl:function name="hw:hello-world" as="xs:string">
> <xsl:sequence select="'Hello, world!'"/>
> </xsl:function>
>
> </xsl:transform>
>
> > gexslt function-available.xsl function-available.xsl
>
>gexslt: system execution failed.
>Following is the set of recorded exceptions:
>
>-------------------------------------------------------------------------------
>Class / Object Routine Nature of exception
> Effect
>-------------------------------------------------------------------------------
>GEXSLT root's creation Segmentation violation:
><000000000169003C> Operating system signal.
> Exit
>-------------------------------------------------------------------------------
>GEXSLT root's creation
><000000000169003C> Routine failure.
> Exit
>-------------------------------------------------------------------------------
>
> Regards,
>
>--drkm
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> p5.vert.ukl.yahoo.com uncompressed/chunked Tue Aug 29 12:13:40 GMT 2006
>
>
>___________________________________________________________________________
>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
>
>
>-------------------------------------------------------------------------
>Using Tomcat but need to do more? Need to support web services, security?
>Get stuff done quickly with pre-integrated technology to make your job
>easier
>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>_______________________________________________
>Gestalt-users mailing list
>Ges...@li...
>https://lists.sourceforge.net/lists/listinfo/gestalt-users
_________________________________________________________________
Be the first to hear what's new at MSN - sign up to our free newsletters!
http://www.msn.co.uk/newsletters
|
|
From: Colin A. <col...@ho...> - 2006-08-30 06:50:32
|
Your welcome. Glad you managed to compile in the end. I'm not brave enough myself to try 5.7 at the moment. If you're feeling really brave, you might try compiling gestalt itself. That requires the latest eposix beta - I don't know if it will work with 5.7 or not. >From: Florent Georges <dar...@ya...> >Reply-To: ges...@li... >To: ges...@li... >Subject: Re: [Gestalt-users] Exception while transformation: >"Segmentationviolation" >Date: Wed, 30 Aug 2006 00:55:40 +0200 (CEST) > >Colin Paul Adams wrote: > > Hi Colin, > > > I advise you to join the gobo-develop mailing list if you > > have any problems doing this. > > Yes, I did. And after several trys and the usefull help >of Eric, I finally succeed to build Gobo from a clean copy >of the CVS, checked out two or three hours ago. > > And the error is gone! > > Many thanks Colin. > > Regards, > >--drkm > > > > > > > > > > > > > > > > > > > > > > p5.vert.ukl.yahoo.com uncompressed/chunked Tue Aug 29 12:13:40 GMT 2006 > > >___________________________________________________________________________ >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 > > >------------------------------------------------------------------------- >Using Tomcat but need to do more? Need to support web services, security? >Get stuff done quickly with pre-integrated technology to make your job >easier >Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >_______________________________________________ >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: Florent G. <dar...@ya...> - 2006-08-30 00:31:12
|
Florent Georges wrote:
Colin,
> The hidden "/.../" part in the URI above is correct
> (refers to an existing file), but with spaces replaced by
> the character "+".
I was wrong thinking the error was because the @href.
Sorry. I was able to reproduce the problem, only with a
main XSLT that imports two other XSLT (one with a @use-when
on function-available('saxon:type-annotation')):
> cat function-available.xsl
<xsl:transform
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="2.0">
<xsl:import href="function-available-2.xsl"/>
<xsl:import href="hello-world.xsl"/>
</xsl:transform>
> cat function-available-2.xsl
<xsl:transform
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:my="function-available.xsl"
version="2.0">
<xsl:function name="my:type-annotation-catch"
xmlns:saxon="http://saxon.sf.net/"
use-when="function-available('saxon:type-annotation')">
</xsl:function>
</xsl:transform>
> cat hello-world.xsl
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:hw="http://www.fgeorges.org/hello-world"
version="2.0">
<xsl:function name="hw:hello-world" as="xs:string">
<xsl:sequence select="'Hello, world!'"/>
</xsl:function>
</xsl:transform>
> gexslt function-available.xsl function-available.xsl
gexslt: system execution failed.
Following is the set of recorded exceptions:
-------------------------------------------------------------------------------
Class / Object Routine Nature of exception
Effect
-------------------------------------------------------------------------------
GEXSLT root's creation Segmentation violation:
<000000000169003C> Operating system signal.
Exit
-------------------------------------------------------------------------------
GEXSLT root's creation
<000000000169003C> Routine failure.
Exit
-------------------------------------------------------------------------------
Regards,
--drkm
p5.vert.ukl.yahoo.com uncompressed/chunked Tue Aug 29 12:13:40 GMT 2006
___________________________________________________________________________
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: Florent G. <dar...@ya...> - 2006-08-29 23:41:26
|
Hi Colin
With your help and the help of Eric, I finally build a
fresh Gexslt and can pass the first step of my
trasnformations. But I found the following stylesheet:
<xsl:transform
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="2.0">
<xsl:import
href="file://localhost/c%3A/.../test-suite-utils.xsl"/>
<xsl:template match="/"/>
</xsl:transform>
produced an eror (when applied to any input tree, of
course):
gexslt: system execution failed.
Following is the set of recorded exceptions:
-------------------------------------------------------------------------------
Class / Object Routine Nature of exception
Effect
-------------------------------------------------------------------------------
GEXSLT root's creation Segmentation violation:
<000000000169003C> Operating system signal.
Exit
-------------------------------------------------------------------------------
GEXSLT root's creation
<000000000169003C> Routine failure.
Exit
-------------------------------------------------------------------------------
--trace produces an empty file. Note that the URI in
@href was generated by Gexslt (the stylesheet is generated
from an other stylesheet) from:
<x_:import href="{ resolve-uri('test-suite-utils.xsl',
base-uri(doc(''))) }"/>
The hidden "/.../" part in the URI above is correct
(refers to an existing file), but with spaces replaced by
the character "+".
Hope that helps.
Regards,
--drkm
p4.vert.ukl.yahoo.com uncompressed/chunked Tue Aug 29 12:13:43 GMT 2006
___________________________________________________________________________
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: Florent G. <dar...@ya...> - 2006-08-29 22:55:48
|
Colin Paul Adams wrote: Hi Colin, > I advise you to join the gobo-develop mailing list if you > have any problems doing this. Yes, I did. And after several trys and the usefull help of Eric, I finally succeed to build Gobo from a clean copy of the CVS, checked out two or three hours ago. And the error is gone! Many thanks Colin. Regards, --drkm p5.vert.ukl.yahoo.com uncompressed/chunked Tue Aug 29 12:13:40 GMT 2006 ___________________________________________________________________________ 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 P. A. <co...@co...> - 2006-08-27 13:21:17
|
>>>>> "Florent" == Florent Georges <dar...@ya...> writes:
Florent> Colin Paul Adams wrote:
>> I have managed to fix this locally. I will check it into Gobo
>> CVS within the nect 24 hours.
Florent> Wow! Thanks Colin. Feel like I'll try to compile
Florent> gexslt from CVS for the rest of my Sunday ;-). I'd like
Florent> to release a 0.1 version of XSLT Unit, but I'd really
Florent> like to can use it with gexslt first.
I advise you to join the gobo-develop mailing list if you have any
problems doing this.
--
Colin Adams
Preston Lancashire
|
|
From: Florent G. <dar...@ya...> - 2006-08-27 13:15:46
|
Colin Paul Adams wrote: > I have managed to fix this locally. I will check it into > Gobo CVS within the nect 24 hours. Wow! Thanks Colin. Feel like I'll try to compile gexslt from CVS for the rest of my Sunday ;-). I'd like to release a 0.1 version of XSLT Unit, but I'd really like to can use it with gexslt first. Regards, --drkm p5.vert.ukl.yahoo.com uncompressed/chunked Sun Aug 27 12:13:40 GMT 2006 ___________________________________________________________________________ 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 P. A. <co...@co...> - 2006-08-27 13:02:22
|
I have managed to fix this locally. I will check it into Gobo CVS within the nect 24 hours. -- Colin Adams Preston Lancashire |
|
From: Florent G. <dar...@ya...> - 2006-08-27 11:24:10
|
Colin Paul Adams wrote: Hi Colin > But I suspect you are not using http access at your end (I > think you are using gexslt rather than gestalt), Yes, you're right on both points. > so there must be another problem. Can you please attach an > archive (zip will do) by private email with all the > necessary files to run the transformation locally? Mmh, I think the stylesheet and the input document were all you needed. Maybe giving you my build of gexslt can help you, at least to reproduce the problem? I send you all that in private. Thanks, --drkm p4.vert.ukl.yahoo.com uncompressed/chunked Sun Aug 27 11:13:41 GMT 2006 ___________________________________________________________________________ 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 P. A. <co...@co...> - 2006-08-27 03:47:28
|
When I try this using my local copy running in debug mode, I find an error in the HTTP handling code. I have reported this to the maintainer of the library. But I suspect you are not using http access at your end (I think you are using gexslt rather than gestalt), so there must be another problem. Can you please attach an archive (zip will do) by private email with all the necessary files to run the transformation locally? Thanks. -- Colin Adams Preston Lancashire |
|
From: Florent G. <dar...@ya...> - 2006-08-26 23:18:21
|
Hi
I get an exception with gexslt 3.4. I have reduced the
input document to:
<test:suite
xmlns:test="http://www.fgeorges.org/xslt/unit-test"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
script="hello-world.xsl">
<test:variable name="elem" as="element()">
<elem id="id"/>
</test:variable>
<test:tests id="false">
<test:title>False negative</test:title>
<test:context select="$elem"/>
<test:test>
<test:expect select="$elem"/>
<xsl:apply-templates select="$elem"/>
</test:test>
</test:tests>
</test:suite>
Unfortunately, I wasn't able to locate the error in the
stylesheet. The stylesheet is attached and available at
http://www.fgeorges.org/tmp/test-suite-gen.xsl and the above
input at http://www.fgeorges.org/tmp/gexslt-exception.xts.
In input, the test:context and test:expect seem to be the
cause of the exception. If you remove both, the
transformation complete. If you keep one or the other, the
transformation abort in the middle and gexslt says something
like:
gexslt: system execution failed.
Following is the set of recorded exceptions:
-------------------------------------------------------------------------------
Class / Object Routine Nature of exception
Effect
-------------------------------------------------------------------------------
GEXSLT root's creation Segmentation violation:
<00000000015B0048> Operating system signal.
Exit
-------------------------------------------------------------------------------
GEXSLT root's creation
<00000000015B0048> Routine failure.
Exit
-------------------------------------------------------------------------------
If you invoque gexslt with --trace=trace.out, you get the
same exception, and 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="[...]/gexslt-exception.xts">
<TODO-Unknown-tag-1323 gexslt-name="
I don't know if you have enough information. At least,
you have both the complete stylesheet and a complete minimal
input to reproduce the problem.
Hope that helps.
Regards,
--drkm
p5.vert.ukl.yahoo.com uncompressed/chunked Fri Aug 25 11:13:42 GMT 2006
___________________________________________________________________________
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 P. A. <co...@co...> - 2006-07-23 20:00:43
|
>>>>> "Colin" == Colin Paul Adams <co...@co...> writes:
Colin> I have now implemented a 2-argument form of the function
Colin> (the full 7-argument form will have to wait for next
Colin> weekend).
it's now completed, tested, documented and committed to CVS.
--
Colin Adams
Preston Lancashire
|
|
From: Florent G. <dar...@ya...> - 2006-07-17 17:13:50
|
Colin Adams wrote: > That's not possible for a number of reasons. Ok. > If you want to do this, then you can write a transformation to > generate your required stylesheet and serialize it to a > destination named by a URI. Yes, sure. > > Also, maybe a gexslt:transform-error() function could be > > interesting to return the error given the result of the > > transformation. It is more > > clear than testing that the N-th item is a QName, isn't it? If the > > transformation is successfull, this function returns the empty > > sequence. > And if it isn't successful? It can only return the same > sequence as now. > So you can write this as an xsl:function if you wish. Yes, sure. It thought about having an abstraction behind the return type on failing. But your question is pertinent: to abstract a return type, writing a function that return the same sequence is not really usefull. Maybe a predicate is-successfull(), but the gain is little. 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-07-17 16:45:09
|
>From: Florent Georges <dar...@ya...> > I wonder if it would be interesting to permit an element() or a >document-node() instead of the URI to identify the XSLT script. This >would allow to really construct the script dynamically, then pass it to >the transform function. That's not possible for a number of reasons. If you want to do this, then you can write a transformation to generate your required stylesheet and serialize it to a destination named by a URI. A named pipe perhaps. > Also, maybe a gexslt:transform-error() function could be interesting >to return the error given the result of the transformation. It is more >clear than testing that the N-th item is a QName, isn't it? If the >transformation is successfull, this function returns the empty >sequence. And if it isn't successful? It can only return the same sequence as now. So you can write this as an xsl:function if you wish. _________________________________________________________________ Windows Live Messenger has arrived. Click here to download it for free! http://imagine-msn.com/messenger/launch80/?locale=en-gb |
|
From: Florent G. <dar...@ya...> - 2006-07-17 16:12:57
|
Colin Paul Adams wrote: Hi Colin, > I have now implemented a 2-argument form of the function (the full > 7-argument form will have to wait for next weekend). Great news. I hope I'll can give it a try soon. I wonder if it would be interesting to permit an element() or a document-node() instead of the URI to identify the XSLT script. This would allow to really construct the script dynamically, then pass it to the transform function. Also, maybe a gexslt:transform-error() function could be interesting to return the error given the result of the transformation. It is more clear than testing that the N-th item is a QName, isn't it? If the transformation is successfull, this function returns the empty sequence. 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 P. A. <co...@co...> - 2006-07-17 07:19:04
|
>>>>> "Florent" == Florent Georges <dar...@ya...> writes:
Florent> So if I understand right, the idea is that caching is
Florent> on by default, and to allow in the future more control on
Florent> caching through flags.
Your understanding is correct.
I have now implemented a 2-argument form of the function (the full
7-argument form will have to wait for next weekend).
The following output:
transformAt line 33 in file://localhost/home/colin/gobo/src/gexslt/transformation.xsl#test2:
Fatal error: http://www.w3.org/2005/xqt-errors#FOER0000: error generated by test of gexslt:transformation
Found an error
is produced by this transformation:
<xsl:transform
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="2.0"
xmlns:gexslt="http://www.gobosoft.com/eiffel/gobo/gexslt/extension"
xmlns:test="http://colina.demon.co.uk/xslt/tests/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
exclude-result-prefixes="gexslt"
>
<test:transformations>
<test1>
<!-- prints local name of document element -->
<xsl:transform xml:id="test1"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="2.0"
>
<xsl:template match='/'>
<output>
<xsl:value-of select="*[1]/local-name()"/>
</output>
</xsl:template>
</xsl:transform>
</test1>
<test2>
<!-- raises an error -->
<xsl:transform xml:id="test2"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:gexslt="http://www.gobosoft.com/eiffel/gobo/gexslt/extension"
version="2.0"
>
<xsl:template match='/'>
<output>
<xsl:value-of select="error(gexslt:TEST_GENERATED_ERROR, 'error generated by test of gexslt:transformation', ())"/>
</output>
</xsl:template>
</xsl:transform>
</test2>
</test:transformations>
<xsl:output method="text"/>
<xsl:template name="initial" >
<xsl:variable name="transformation_result" select="gexslt:transformation('#test1', doc(''))"/>
<xsl:value-of select="$transformation_result/output/text()"/>
<xsl:variable name="transformation_result_2" select="gexslt:transformation('#test2', doc(''))"/>
<xsl:if test="count ($transformation_result_2) gt 1 and $transformation_result_2[1] instance of xs:QName">
Found an error
</xsl:if>
</xsl:template>
</xsl:transform>
Note there have been some changes to the spec.
In particular, on an error, the output is now: (QName, description, error-objects...)
If no error, only the principal result document is output. This is
because, for xsl:result-document, I cannot capture the output with my
current architecture, as, int the case of file output at least, the
output is streamed directly to the file.
I might think about that one.
--
Colin Adams
Preston Lancashire
|
