> 1- Sun wants to delegate some part of the java development because server
> side java
> (servlet, JSP) is considered minor and Sun prefers to concentrate its team
> on
> a more strategic aspect of java.
Nope. In fact our Servlet and JSP staff are on the rise. Not too long
ago, there was just me doing the spec, ri, etc for servlets. Now we've
got 2 addt'l full time people and an intern on engineering, a set of QA
folks, and documentation is coming on line. On the JSP side we've grown
from 1 to many as well in a diverse bunch of people. All of these people
that are joining our group will be working on this project via Jakarta.
This isn't about "getting somebody to do our work for us".
Sun is doing this as
1) Apache is a vital channel to the web development community
-- they do have the majority of servers on the planet;
2) to help out on Apache, we have to participate according to
Apache's rules;
3) we increase the odds that the same engine (jakarta) will
show up in many other commercial products. IBM has pledged
support as has Oracle and others. If these folks use the
jakarta engine, it's only good news for the users.
> 2- Sun attempts to convince everybody (and the ISO consortium) that java is
> really
> open and public. But it seems java will never be normalized... so it is a
> waste of time.
This had *NOTHING* to do with why we are doing this. The RI will be
developed under the open apache process. The specifications will still
be developed using the Java Community Process (and not in the apache
process). I won't get into a debate about the JCP here.
> 3- Sun just wants to do good and REALLY doesn't expect anything in return
> (my favorite!)
Oh, we want to do good -- but we do expect a few things in return:
1) Jakarta will be a world class servlet engine
2) builds of Apache will be available with Jakarta and
these will get into wide use in the ISP and other
communities
3) As many industry leaders will get involved in the
project so that instead of focusing on building
lots of different engines that do things differently
we'll have a number of high quality engines
based on jakarta source.
This is why we are taking this step -- jakarta and the, for us, unusual
way of getting there are required stepping stones to get there. Sun
typically will take the best path for any particular problem.
Just keep in mind that the reasons that we do things with our licensing
of the software have very little to do with "profit" or "greed" -- they
have *everything* to do with maximizing the promise of WORA, preventing
fragmentation, and putting Java everywhere we can. In the case of
servlets and JSP -- this is the best way to do it.
.duncan
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
