Re: [xsl] Root element is not complete in result tree

Subject: Re: [xsl] Root element is not complete in result tree
From: "Mailing Lists Mail daktapaal@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 19 Aug 2016 16:11:33 -0000
Am i using the right version?


On Friday, August 19, 2016, Mailing Lists Mail daktapaal@xxxxxxxxx <
xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> Saxon version is saxonEE9-7-0-7J
>
> Using trial version
>
> On Friday, August 19, 2016, Michael Kay mike@xxxxxxxxxxxx
> <javascript:_e(%7B%7D,'cvml','mike@xxxxxxxxxxxx');> <
> xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx
> <javascript:_e(%7B%7D,'cvml','xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx');>>
> wrote:
>
>> Then that looks very similar to one of the bugs I listed
>>
>> https://saxonica.plan.io/issues/2830
>>
>> which is described as "fixed in maintenance release 9.7.0.7"
>>
>> So please check that you are using the latest maintenance release.
>>
>> Michael Kay
>> Saxonica
>>
>>
>> On 19 Aug 2016, at 15:34, Mailing Lists Mail daktapaal@xxxxxxxxx <
>> xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>>
>> I am reworking my xslts and i have seen that i am using
>> <xsl:for-each group select = "AnimalKingdomGroup/copy-of(.)" group-by =
>> "groupName"/>
>>
>> When i remove the template that does this , the end tags are copied fine.
>>
>> I am thinking there should be something about the grouping . what is the
>> best way to do this ? If i don't put copy of, then i know its an error that
>> i am accessing the tree twice in same context.
>>
>> But copy-of is also bad because animalKingdomGroup will be massive and i
>> know that ..
>>
>> Any advices here ?
>>
>> Thanks.
>> Dt
>>
>> On Aug 18, 2016 11:57 AM, "Michael Kay mike@xxxxxxxxxxxx" <
>> xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>>
>>> Your stylesheet may be exhibiting the same bug as listed on our web
>>> site, or it might be a different bug with similar symptoms. Give us the
>>> details, and we'll be happy to check it out. It could turn out be something
>>> completely different, like a failure to close the output stream. When we
>>> know what it is, we can start looking for a workaround.
>>>
>>> We are always looking for more test cases, so please feel free to submit
>>> the problem case in a form that we can run.
>>>
>>>
>>> On 18 Aug 2016, at 15:25, Vasu Chakkera vasucv@xxxxxxxxx <
>>> xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>>>
>>> So, i can assume that the stylesheet that works once under will always
>>> work...
>>>
>>>
>>> Not always. Some problems are due to multi-threading, or to other
>>> effects like hashing that effectively randomise the order of execution, so
>>> don't always repeat the same way. But you'll spot that fairly quickly if
>>> you are disciplined about running repeatable and automated tests of your
>>> code.
>>>
>>> Michael Kay
>>> Saxonica
>>> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
>>> EasyUnsubscribe (by email)
>>>
>> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
>> EasyUnsubscribe <http://-list/293509> (by email)
>>
>>
>> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
>> EasyUnsubscribe <http://-list/1311928> (by email)
>>
> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
> EasyUnsubscribe <-list/1311928> (by
> email
> <javascript:_e(%7B%7D,'cvml','%5Cx3dremove');>)

Current Thread