RE: [A5:RT] Minimum J2ME Specs and Strategy

What's wrong with it? 
As long as it runs the component's lifecycle and does not crash it IMO
works.  It's of course only the first step and we will have to add to it
later. Also, the container will of course have certain limitations, e.g. no
role management, just null or console logging and no logging configuration,
no component handlers (only thread-safe services), no life cyle extensions
and so on.  Just barebone component lifecycle support.  To further optimize
it, we can add lazy loading and memory optimized configuration handling to
the container so that it does not overpower the actual application. 

> -----Original Message-----
> From: Leo Simons [mailto:[email protected]]
> Sent: Friday, January 03, 2003 4:27 PM
> To: [email protected]
> Subject: Re: [A5:RT] Minimum J2ME Specs and Strategy
> 
> 
> Marc Schier wrote:
> > We could use Tweety as the J2ME container and add
> > kXML configuration and mandate that all J2ME compliant 
> components must be
> > thread-safe and we will have our j2me compliant container today.
> 
> hey peeps, not knowing much about J2ME or feeling like 
> investigating it 
> atm, but as a footnote: really, the only useful thing in the tweety 
> codebase is the docs. It doesn't actually work very well :D
> 
> - Leo
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:[email protected]>
> For additional commands, e-mail: 
> <mailto:[email protected]>
>