Mr. Jung & Mr. Molony
Quoted below are some e-mails that we going between yourselves
and Shane Curcuru with regard to Xalan/XSLTC and Trax/PDA
support. I am currently helping Todd in his work to implement
Trax support (with caching), and I will not be able to put much
focus on PDA support just yet.
I will be more than willing to assist you if you any time to
invest in this work. The compiler part of XSLTC was never
designed to run on a PDA (runs on J2 SE or EE), while the
compiled translet, the translet runtime library and the internal
dom were all initially done in Java1 - and we had a dedicated
version of the DOM from use on PDAs.
The work that must be done is:
a) determine which classes in the dom and runtime packages
that break with the J2ME APIs
b) determine which of these classes that need only minor
alterations and can be used on all JVMs (ME, SE and EE)
c) determine which classes we need separate versions of for
use on PDAs (this used to be only the DOMImpl class, but
now there may be more)
d) rewrite the classes in c)
It has also been suggested that we determine a set of XSLT
elements that can be compromised on the J2ME platform, and
thereby eliminating the need for rewriting some of the classes
in step d) above. I don't know how much I like the sound of
that, but I am sure you can shed some light on what XSLT
transformations will be used for on PDAs and if there are any
XSLT elements that probably will not be necessary.
If you are interested in looking into PDA support, then the
XSLTC detailed design docs will be your best starting point:
http://xml.apache.org/xalan-j/xsltc/index.html
Thanks,
Morten Jørgensen
> If you plan to support "the little guys" in the future, as it sounds like
> you do, in my opinion TransletDemo.prc should be put back in the
> distribution. Source code would be helpful too, but based on the current
> XSLTC source I don't see how it would be compilable. Perhaps that's why it's
> not there now...? The Sun distributions never included its source (as far as
> I know)
>
> Let my know any other way I might help out or contribute. I would very much
> like to see continued XSLTC support on information appliances.
>
> Sincerely,
> Eric H. Jung
> [EMAIL PROTECTED]
> Wrox Press contributing author
> 1-303-781-7947
>
> details soon (Tom A, Todd, Morten). A few general comments about Xalan
> futures and the specific integration:
>
> ---- you Jim Molony <[EMAIL PROTECTED]> wrote ----
> > However the main problem seems to be that classes and
> > interfaces required by XSLTC have since diverged from what is available
> on
> > the most up-to-date versions of Palm/J2ME configurations.
> ...
> >> From Eric:
> ...
> >> Here is the simplest code to execute a translet using XSLTC as it is
> >> released with Xalan-J 2.1.0, **not** XSLTC Alpha 5. This code does
> >> not utilize the TrAX-translet integration by G. Todd Miller:
> ...
> Some of this may be because we want to start integrating the xsltc model
> with the xalan model, which meant quickly bringing xsltc stuff upto DOM
> level 2, etc. Also, the TrAX-Translet integration is still very limited
> and meant for prototyping right now; obviously this will get much better
> over time.
>
> One side question: can anyone verify the CLDC-compatibility (or whatever
> other profile, etc.) of the various external standards we use? Namely TrAX
> -> javax.xml.* packages, the org.w3c.dom.* packages, and the org.xml.sax.*
> packages? If those standard interfaces can't run on small devices, then
> we'll have a harder time adopting to run there.
>
> >> This code is a subset or simpler version of the command-line translet
> >> "runner" that comes with XSLTC,
> >> org.apache.xalan.xsltc.runtime.DefaultRun. It's the DOMImpl object
> >> that causes us problems in the J2ME-CLDC-kjava environment (but no
> >> problems in J2SE and J2EE). The classes/interfaces that are not in
> >> the environment but upon which DOMImpl depends are:
> ...
> Any tips or education you can contribute to xalan-dev will definitely help
> here for us to get up to speed on these issues (although I imagine
> Tom/Todd/Morten already have a handle on this stuff).
>
> >> It's also worth noting that the TransletDemo.prc
> >> demonstration that came with XSLTC Alpha 5 and before has
> >> mysteriously disappeared from the Apache distribution!
> This may well simply be an oopsie on our integration. The xsltc folks gave
> us a big pile of files which we munged a bit as we fit them into the
> existing xalan source tree, and we may well have dropped some stuff,
> particularly if it wasn't a .java file or obvious documentation. Point out
> any specific files you think should still be there and an xsltc commmitter
> can add it back in.
>
> - Shane
