Hopefully the Xalan committers from the xsltc team will chime in with more
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
