Hello Michiel,
A little late, but I was just too busy with other things.
imo a major release is justified when we do a good implemtation of java
5. The api will change drasticly which makes it impossible to create a
drop-in replacement.
A good implementation should remove many of our convenience classes in
the bridge. E.g. a NodeList should just become List<Node> and not
NodeList<Node> I played around with this at the component weekend and
realized that it is impossible at the moment. The NodeList
implementation does also some conversion of objects. You can add any
object to the list and the NodeList will try to convert it to a Node. A
good discussion on the API is required I think.
Here are some informational PDF's to understand the java 5 migration
issues better.
http://www.agiledeveloper.com/download.aspx
* enums
* Java 5 Features - Part II
* Java 5 Features - Part I
* Generics in Java - Part III
* Generics in Java - Part II
* Generics in Java - Part I
Regards,
Nico
Michiel Meeuwissen wrote:
Hi,
In the light of the progresses in the 'component framework' project, the
idea rose to release the next version of MMBase not as 1.9, but as 2.0.
So an abstract of the release-plan of 2.0 could then be:
- transition to java 1.5
- first version of mmbase framework and component infrastructure
plus of course bugfixes, and other small improvements.
Completion of core changes ('core 2', see also 'MyVision'), would then
e.g. lead to an MMBase 3.0.
Michiel
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
