Re: [xsl] calling Java non static methods from XSLT

["Mailing Lists Mail daktapaal@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

That did not answer my question. Thanks for your time


On Sat, Jun 4, 2016 at 12:54 AM, Wolfgang Laun wolfgang.laun@xxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> If one "Node" (whatever that is) can be processed in one microsecond, a
> trillion of them will take more than ten days. If it's several trillion, the
> bears sure will have chased the bulls away before the analysis is over...
>
> -W
>
>
> On 4 June 2016 at 00:16, Mailing Lists Mail daktapaal@xxxxxxxxx
> <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>>
>> Dear All,
>> we are having the following situation..
>> We are working with the some Stock Market Data where some of the
>> values we need are done by a complex algorithm that is written in Java
>> , typically for the forcast etc. The XSLTs are all compiled .. We
>> instantiate the object within the XSLT using the new() and then call
>> the Java methods of that object, which  returns some statistical
>> information.
>> Which one of the assumptions are correct? I  believe the assumption1
>> to be true but checking ..
>> Scenario :
>> I am using the XSLT on Trillions of Nodes .My situation demands that I
>> treat each Node individually and run the XSLT on each of these nodes
>> separately. This means these nodes will be diced first and then , the
>> XSLT will be called on them
>>
>> Assumption1
>> ==========
>> there will be trillion objects created, with each invocation of the
>> XSLT.  and the XSLTs being compiled has nothing to do with the Object
>> creation, as the objects will be created at run time?
>>
>> Assumption2
>> ==========
>>
>> Since I have precompiled the XSLTs, it should not create trillions of
>> java objects
>>
>> Any pointers please>
>>
>> Dr.Tapaal
>>
>
> XSL-List info and archive
> EasyUnsubscribe (by email)