Here are some differences that I have noticed about this Beta release based on release notes:
1. Here are some official "what's new" from the
release notes
* Admin Console GUI enhancements
* Web Services Security
* WS-I Profile 1.1
* Migration Tool
2. Beyond that I found a few other changes when comparing to Sun Java System Application Server Platform Edition 8 Update Release 1 release notes:
* NetBeans plugin for AS PE 8 2004Q4 (new)
* Updated JDK to 1.4.2_05
* Additional JDBC driver support, specifically DataDirect drivers were added.
* Oracle 10g support
This small list probably barely scratch the surface on the differences and enchancements that the product team has done. A while ago, I was told that this release will have a lot of enchancements under the surface. I'll try to write more about this when time permits.
If you are curious, then you should definitely check it out. The
installation insructions can fit into my small 15" screen without scrolling, which is really short and simple to get started.
Back in June, I published an
article. Since then, I received many positive and constructive feedback. I would like to thank everyone who provided the feedback. With the feedback I received, I have rethinked through the article. I'll try to put some of my new thoughts down in this blog and you are welcome to tell me what you think.
I attended the Open Source Summit yesterday and I heard about many valuable experiences and opinions from some great contributors of Open Source community. Major participants on the panel or speakers worked in some of the well known organizations or projects such as Apache, Mozilla, NetBeans, OpenOffice, Tonic (Open Source Solaris) and many others. After heard from many of these great intellectuals' talks, I was able to relate their wisdoms gained from Open Source effors to technology adoption. Here are some principles and success factors for an Open Source project that can also apply to technology adoption:
Build trust
- Be a good citizen of the Open Source community.
- There is no such a thing as stupid question attitude.
- Treat others as equal status to you. Allow others to participate in the decisions and activities that are core to the project.
- Give others ownership of the project so that they feel they have the responsbility to make the project successful.
- Lead by doing
- Build a win-win work model so participants will think the changes or thir work will be for their own benefit also.
- You can not expect others to commit on a task if they are not willing to do so. This leads to use of other persuasive factors to assist a project to deliver on time. For example, a participant could have a depending product that need this project to deliver on time and willing to assist fix the last couple show stopper bugs in this project.
- Be consistent
Lower cost of entry
- If a newbie has to spend one month to get started on an Open Source project, there is no way that person will spend that much effort.
- Good documentation.
- Core engineers need to have the patience to take time and train the new comers so they will learn the necessary skills to take up responsibilities within the project. (Teach others to fish)
- Provide access to the tools you have.
- For some situations, a company should provide easier access to necessary hardware for participants. For example, a company may provide some testing iPaq for developers to test their Linux software.
I am excited to hear about the experiences and opinions from some great contributors of Open Source community. I was sitting next to Brian Behlendorf and talked briefly to Hideya Kawahara. There are also many other intellectuals, who made many inspiring and interesting points today. I'll need to sort out my notes before I can say more interesting things.
If you want to get a sneak preview of the up coming release of Sun's Application Server, check the following blogs:
20040806,
20040811