3 ms·

I believe that is basically it. They won't be participating in writing specifications, but I don't think that anyone will be stopping Apache (or anyone else) fr

by lenni 16y ago

I believe that is basically it. They won't be participating in writing specifications, but I don't think that anyone will be stopping Apache (or anyone else) from implementing any of the JSRs. If a hypothetical Java Servlet API v4.0 would be released they could still make Tomcat be compliant with it. On the other hand Tomcat is very widely used in the not-quite-huge-enterprise companies and it is obviously helpful for a spec if all implementers can agree on some common ground before it is written. ECMA probably wouldn't see a point in doing ES5 if Microsoft and Mozilla would not talk to them.

yesno 16y ago
It might be a matter of time before Oracle decided to cut all of the oxygen lines for these open source solutions judging from Ellison's comment about RedHat business models. What do you think would happen in order for a library to be certified (passed a certain TCK) would require to pay Oracle a huge amount of money? Oracle can get more money from IBM, RedHat, SpringSource (SS uses a modified Tomcat for their tcServer) and a slew bunch of other companies. Whether they'll do it or not, I don't know.