Re: [xsl] Upgrade from XSLT1

["Vasudev Kandhadai vasu.kandhadai@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Yes.
This is what I suggested in the meeting.. That we jump to XSLT2 straight
away . There is a lot of clean up work required from their XSLT1 to 2
anyway. The XSLT3 was in the back of my mind and wanted to cross check the
approach.
Thanks.
Kandha


On Tue, May 27, 2014 at 3:02 PM, Wendell Piez wapiez@xxxxxxxxxxxxxxx <
xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> Kandha,
>
> It's difficult to say much that would be useful without getting up
> close, but why can't you upgrade the present XSLT 1.0 pieces to XSLT
> 2.0 now (for an immediate gain in performance without much, if any,
> rewriting), and migrate off the SAX splitters onto XSLT 3.0 when it is
> more stable and "real"?
>
> This way you would isolate any issues in migrating (as Liam and
> Dimitre both suggest, testing and due diligence may well constitute
> the bulk of the effort), and if at a later point there are more gains
> to be had from integrating your pipeline further (maybe doing the
> file-splitting and transformation together), you will be in a better
> position to do that.
>
> Cheers, Wendell
>
>
> On Tue, May 27, 2014 at 2:15 PM, Vasudev Kandhadai
> vasu.kandhadai@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
> wrote:
> > Thanks all.
> > I am good with the XSLT2 upgrade. Just worried about the XSLT3 upgrade.
> The
> > streaming templates dont work exactly like the other non streaming
> > templates.. So there is a different of approach.
> > Vasu
> >
> >
> > On Tue, May 27, 2014 at 2:07 PM, Dimitre Novatchev dnovatchev@xxxxxxxxx
> > <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> >>
> >> For upgrading to XSLT 2.0, see this:
> >>
> >>
> http://stackoverflow.com/questions/9387396/upgrading-xslt-1-0-to-xslt-2-0
> >>
> >> As for upgrading to XSLT 3.0, I would recommend making some
> >> experiments in controlled environment before trying this on a larger
> >> scale in production -- also have in mind that the specification may
> >> change and that the available implementations too. Not to speak that
> >> any current XSLT 3.0 implementation could be not too-stable and
> >> reliable yet.
> >>
> >>
> >> On Tue, May 27, 2014 at 10:25 AM, Vasudev Kandhadai
> >> vasu.kandhadai@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
> >> wrote:
> >> > Dear All,
> >> > After a lot of convincing , the architectural team finally agreed to
> >> > approve
> >> > Saxon9.5.  There is a bit of a relief, but I am having to make a
> >> > decision on
> >> > whether we upgrade from XSLT1.0 to XSLT3.0 directly? The code base is
> >> > not
> >> > very big and we are OK to rewrite to adapt to better coding practices
> >> > that
> >> > come with XSLT2 and 3.
> >> >
> >> > I am assuming that the coding paradigm is slightly different in
> XSLT3..
> >> > The
> >> > approach on how to write templates, the restrictive xpaths etc , could
> >> > be
> >> > backwards incompatible etc..
> >> >
> >> > I need advice on this/ Is it true that the coding approach is
> different
> >> > using the XSLT3 ?  I am fairly confident that the XSLT2 is a good
> point
> >> > to
> >> > start. The only reason XSLT3 was even in the discussion was because of
> >> > the
> >> > HUGE xml files. Currently we run a Sax Java splitter over the big XMLs
> >> > and
> >> > run XSLT1 files over the smaller chunks. This works well. My options
> >> > with
> >> > XSLT2 would be to change the XSLT1 to XSLT2 and keep remaining things
> >> > same..
> >> >
> >> > With XSLT3, we may consider removing the SAX splitters, as it may no
> >> > longer
> >> > be used. XSLT3 will probably take care of the memory issues with HUge
> >> > XML
> >> > files.
> >> >
> >> > Putting all my thoughts in,, Hopefully will get some clarity with the
> >> > expert
> >> > advices from you all..
> >> >
> >> > Kandha
> >> > XSL-List info and archive
> >> > EasyUnsubscribe (by email)
> >>
> >>
> >>
> >> --
> >> Cheers,
> >> Dimitre Novatchev
> >> ---------------------------------------
> >> Truly great madness cannot be achieved without significant intelligence.
> >> ---------------------------------------
> >> To invent, you need a good imagination and a pile of junk
> >> -------------------------------------
> >> Never fight an inanimate object
> >> -------------------------------------
> >> To avoid situations in which you might make mistakes may be the
> >> biggest mistake of all
> >> ------------------------------------
> >> Quality means doing it right when no one is looking.
> >> -------------------------------------
> >> You've achieved success in your field when you don't know whether what
> >> you're doing is work or play
> >> -------------------------------------
> >> To achieve the impossible dream, try going to sleep.
> >> -------------------------------------
> >> Facts do not cease to exist because they are ignored.
> >> -------------------------------------
> >> Typing monkeys will write all Shakespeare's works in 200yrs.Will they
> >> write all patents, too? :)
> >> -------------------------------------
> >> I finally figured out the only reason to be alive is to enjoy it.
> >>
> >
> > XSL-List info and archive
> > EasyUnsubscribe (by email)
>
>
>
> --
> Wendell Piez | http://www.wendellpiez.com
> XML | XSLT | electronic publishing
> Eat Your Vegetables
> _____oo_________o_o___ooooo____ooooooo_^