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

It can't run the component lifecycle properly. If you throw in a few 
components with dependencies, you get ConcurrentModificationExceptions. 
The only way a container can really support service() and compose() is 
by using a Directed Acyclic Graph or a similar mechanism, and Tweety 
doesn't have one. We had a thread about this some time ago, and I came 
to the conclusion it'd be better to invest time in doccing existing 
containers rather than modding tweety to be more powerful.

IOW: it crashes by design :D

cheers,

- Leo

Marc Schier wrote:
> What's wrong with it? 
> As long as it runs the component's lifecycle and does not crash it IMO
> works.

Leo Simons wrote:
>>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