On Aug 16, 2005, at 7:31 PM, Thomas Skjølberg wrote:
> On Fri, 12 Aug 2005 07:26:08 +0200, Changshin Lee
> <iasandcb_at_gmail.com> wrote:
>
>
>>
>> On Aug 12, 2005, at 9:13 AM, Thomas Skjølberg wrote:
>>
>>
>>>
>>>
>> I checked necessary classes from SAX API in the CVS repository, so
>> now all you need in order to build FIME is StAX ME. Please refer
>> to readme.txt in FIME module.
>>
>
> My current build problems are:
>
> import org.apache.mirae.util.CharacterUtil missing in
> BuiltInEncodingAlgorithm.
CharacterUtil is src/mirae/stax in Mirae SVN.
>
> interface javax.xml.namespace.NamespaceContext (several places in
> com.sun.xml.fime.stax package) is not j2me compatible (enumeration
> vs Iterator) and should be renamed.
Could you point the problems exactly? I already replaced every
Iterator with an enumeration in both FIME and StAX ME. Note that
NamespaceContext for Java SE is not compatible with FIME. You need
NamespaceContext in Mirae (src/mirae/stax).
>
> classes staxinputfactory and staxoutfactory do not compile because
> they implement non-j2me-compatible 'factory' inferfaces. Several
> final strings from those two classes need to be moved as factory
> classes are deleted.
It's very strange because the current FIME is well built with Sun's
WTK 2.2 (MIDP 2.0). Please make sure that you get a right (meaning
latest) copy of Mirae StAX from its SVN. Those factories in FIME are
completely compliant with factories defined in StAX ME in Mirae. In
fact, my FIME project in EclipseME relies on Mirae StAX project as a
required project. WTK 2.2 + Eclipse ME 1.0 + Eclipse 3.1 is a
wonderful development environment for Java ME :-)
>
> javax.xml package issue:
> midp 2.0 does not permit user-defined system classes; this
> apparently also applies to javax.xml (quick google: http://
> www.google.com/search?hs=xUP&hl=no&client=opera&rls=en&q=%22Cannot
> +create+class+in+system+package%22&btnG=S%C3%B8k&lr= ).
This is a known problem and we as phone users can't do anything for
that. I tested Mirae StAX and found it running well on my Nokia 6230,
so the system package issue (java and javax) depends on devices. If
you "really" want to run your Java standard packages on a device that
doesn't allow you to do so, obviously you need to rename all the
packages or get some phone for (serious) developers. Note that Sun's
WTK itself has no such a problem.
>
> If there is a StAX-ME library please include it in the FIME dir.
StAX ME is managed in Mirae, so I'd like to recommend checking its
source code in from Mirae SVN to your workspace (so you can build
your own StAX ME jar or classes with a preverifier).
>
>>
>>
>>>
>>> As for the classes/interfaces that does not exist in CLDC (Map,
>>> List, etc), obiously one needs to change the FI code or start
>>> deleting more FIME classes. I guess some of the J2SE interfaces
>>> may be implemented using CLDC Vector/HashTable/Enumerator but I
>>> don't know how smart that would be. So what is 'the plan'? What
>>> is the preformance gain of using J2SE Map/List etc over normal
>>> Hashtable/Enumerator/Vector in the J2SE FI?
>>>
>>
>> I'm slightly confused with your question because FIME doesn't
>> depend on Java Collection Framework. FIME has been developed from
>> FISE, and what I've done for that is removing all the usages of
>> Java Collection Framework and replace with classic Vector and
>> Hashtable. Therefore, I have no plan regarding your point and the
>> question about Java SE is irrelevant to FIME.
>>
>
> Ok, then I guess changing the J2SE code to make if J2ME compatible
> is out of the question (*)
>
>
>> Regarding FIME StAX, all the supported features are the same of
>> those of FISE, so please refer to FISE StAX.
>>
>
> (*) so that improvements in FISE will have to be manually
> propagated to FIME. I'd for one like to see support for StAX
> Location, however I unsure how compression complicates things.
>
>
>> This workability is a basis for FIME's future, and we have to
>> research on enhancing FIME.
>>
>
> Is there a forum for that? I'd like to work on integers instead of
> strings. Also, I need to skip sub trees like a mad man.
>
> I'm a little surprised by all the 'xxxArray' classes in the util
> package. Why are there so many? When I first read about FI I
> thought that it would be all about String arrays.
>
> Cheers,
>
The rest of questions are answered by Paul, thanks!
Cheers,
Ias
>
>
> Thomas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_fi.dev.java.net
> For additional commands, e-mail: dev-help_at_fi.dev.java.net
>
>