想知道永中在多大程度上还依赖于平台。
它通过了100％pure Java的认证了吗？

    我只能告诉你永中Office完全是用JAVA开发的，至于技术机密则是无法透露的

既然永中Office完全是用JAVA开发的
就该去申请一个100％pure Java的认证啊

这位朋友是不是觉得这样很有必要?

当然了，如同IT证书，多一个是一个
而且吹牛的时候也方便啊！
当然，如果以后希望依赖于特定平台，就别申请，
以免别人说你退步了。

呵呵，除非那个操作平台是垄断性的

我的理解pure java的认证不仅仅是代码全是java 的标记。也是一个产品质量的认可。
可惜没有找到关于该认证的材料。
不知道具体手续。
不过应该不会为了认证就需要交出源代码吧

的确也是一个产品质量的认可
但是不必交出源代码
100% PURE JAVATM CERTIFICATION-- QUESTIONS & ANSWERS



When the 100% Pure JavaTM Initiative was announced in December of last year it was a marketing program. Today it is an industry initiative with hundreds of companies having endorsed its objectives. The heart of the 100% Pure Java Initiative is the 100% Pure Java certification process which ensures ISVs, corporate developers, and end-users that products bearing the 100% Pure Java logo are truely platform independent.
In addition to being a valuable brand for customers, JavaSoftTM discovered that early participants in the certification tests are praising the quality assurance benefits of the test suites.
We asked the key members of JavaSoft's 100% Pure Java team to discuss the whys and hows of the 100% Pure Java certification process.
Q: First off, what does it mean for a program to be 100% Pure Java?
A: Basically, a pure JavaTM program is one that relies only on the documented and specified Java platform. That means no native methods, no external dependencies aside from the Java Core APIs, and some other requirements that are detailed in the developer's Certification Steps on our Web site. The certification process verifies that the code is in fact 100% Pure Java.
Q: So why should someone worry about whether or not their programs are 100% Pure Java?
A: A year or so ago you really did not have to worry about it. But now some technologies are surfacing that work to tie Java to only one platform, it is important to worry about 100% Pure Java. It is the only way to guarantee to both the developer and the end-user that the program really will run on multiple platforms.
The whole idea behind the certification program is to establish that whenever a program wears the 100% Pure Java logo, people can be sure it runs on any platform that has the Java compatible logo, which is for JavaTM Virtual Machines. All users have to do is match up the two logos and they can be confident the program will run.

Q: From a developer's or ISV's perspective, what are the certification steps?
A: The initial thing you need to do is get information on the requirements for 100% Pure Java -- how to develop a new program or how to convert an existing program to be 100 percent pure. You can get that in our Certification Steps.
There is also a free purity check you can use to get started. It's called JavaPureCheckTM and you can download it from the Web.

The first real certification step is to apply for certification by contacting KeyLabs, which is our independent testing facility for 100% Pure Java. Developers pay the certification fee and then download a full test suite, so they can begin internal tests.
As a developer, first you run the static test using JavaPureCheck to determine whether the code is pure Java. That generates a report that flags errors and exceptions. Developers have the option to annotate that report before sending it into KeyLabs, to explain why they did certain things. For example if there are native method calls, file names, or URLs, you get to explain why they are in there.
Next, you create and run the dynamic multi-platform tests. In order to pass, the dynamic test must cover a certain percentage of your program's methods. So an additional step before submission is for you to measure coverage of your methods.
Developers send off both tests as a final submittal to Key Labs, which reruns the tests themselves. The lab might call you if they have questions. The lab will then certify or reject the application for certification.
We had the JavaPureCheck program in the Hacker's Lounge at Java OneSM, and about 100 ISVs brought in applications and ran them through the purity check. Perhaps the most interesting thing to come out of that experience was that we found the test was very educational for the developers. ISVs found out there were things in their applications that they had no idea were there. Apparently no one had gone through and evaluated the applications as a whole to critique the way various developers added functionality.
So aside from being a purity check, we found it was a good quality control test to run the code through. Most of the ISVs were very positive, saying they thought the tests helped to get developers in touch with their applications. So we got some very positive feedback on the whole process.
Q: Is this quality control the reason so many companies are supporting the 100% Pure Java program?
A: The quality checks are a side-benefit, but really, the central reason people are supporting 100% Pure Java is the whole idea of cross-platform performance. The whole reason Java has taken off to such a degree is because of its cross-platform nature.
Again, there are forces at work that would change that, and make it just another proprietary technology. What the industry is saying is that they do not want that. They want something that is truly cross-platform. We want the Open Horizon's of the world to have just as big of a chance as an IBM or a Microsoft program of making a big splash in the marketplace.
Once you get rid of this proprietary architecture, and you look at the way the Web is revolutionizing distribution, then companies like Open Horizon really can compete against the big companies. No longer do they have to go through big retail distribution chains. And they do not have to be as worried about platform specific architecture, or porting their application to a whole bunch of different platforms. So Java really levels the playing field.
It is really interesting that big companies like IBM and like Oracle are just as supportive as smaller companies such as Bulletproof and Marimba. That is primarily because everybody -- well there may be a few exceptions -- wants this cross-platform capability to succeed. Certainly customers want it because it means they have a choice. They do not have to be locked into one architecture.
Q: Can you give more details about what testing procedures involve?
A: There are three testing tools: JavaPureCheck, JavaSpinTM, and a set of coverage reporting utilities. The first step is running JavaPureCheck. That spits out a report flagging a range of issues. Error messages note things that appear to be clear violations, like native calls. Warning messages point to things that may be a problem -- something with a slash in it may be a hard- coded path name, which is not acceptable, or it may be a perfectly acceptable URL.
When the firm is satisfied with its JavaPureCheck results it should then use JavaSpin to generate a script that automates running the code on multiple platforms. JavaSpin is a GUI-capture/replay tool. The developers run their product, capture the user interaction, and then generate a Java program as output.
That test script, which is a Java program itself, can be executed on multiple platforms, and the developers are expected to test it on several platforms.
What we are looking for from the multi-platform test is consistent behavior and adequate coverage.
The multi-platform test requirement is that the test script run to completion on two platforms. Those platforms are evolving as more Java Development Kit (JDKTM) 1.1-based VMs become available. Today the multi-platform script would have to run to completion on either Microsoft Windows NT or '95, and SolarisTM.
Everything has been designed so that developers can run all the tests in-house and know that they will pass the tests before submitting the materials to Key Labs to complete the certification. We wanted to eliminate as much as possible the back-and-forth that might occur between the lab and the developer. Thus the developers have all the tools they need to analyze their applications and we've been able to keep the lab charges to a minimum.

Q: What is 100% Pure Pending?
A: There are many ISVs whose applications are based on the older version of the JDK and may contain some native method calls. For these developers, we will be offering an interim 100% Pure Pending logo. A developer who is pending certification has the opportunity to participate in co-marketing activities. Make no mistake: Only applications, components and applets that contain 100% Pure Java will be 100% Pure Java certified. We issued a statement on this recently called 100% Pure Java certified == 100% Pure Java. Period.
Q: Can you describe the objectives of the 100% Pure Java Initiative?
A: We and our industry partners are trying to accomplish five things. We want to educate the market -- both developers and end-users -- on why this is important. The second goal is to train people -- ISVs and internal developers in particular -- on how to write 100% Pure Java applications. Third, we want to provide assistance in pre-testing their applications. Fourth, we want to certify and brand 100% Pure Java applications. And fifth, we want to market the brand and give ISVs ways to promote their products to the marketplace. Certification is the glue that makes everything hold together.
The 100% Pure Java Initiative was initially structured to be a combination of the "Intel Inside" program and the "Designed for Microsoft Windows 95" program. It is both a co-op marketing program like Intel's, and it is an application logo program like Microsoft's.
Q: Have you had enough experience with the Initiative that you can point to some successes?
A: We have gotten a great deal of positive feedback about the testing process. Many of the firms said that the process resulted in some significant improvements to their code.
Corel is probably the biggest early success story. They saw this immediately as an important competitive advantage. All ISVs, including Microsoft, want to be able to use the Java logo just because of the power of the brand. We purposefully made it so that there is only one logo for applications. So you are either 100% Pure Java or you don't get to put a Java logo on your application. That was by design.
Corel Office for Java is a clear success story and a good example of how one company jumped on the 100% Pure Java Initiative as a clear competitive advantage to increase their share of the market.
100% Pure Java also means that developers can scale their applications to attack new markets that would otherwise be too expensive to tackle. You hear product managers for Lotus Notes talk about how 100% Pure Java will enable them to take a look at PDA applications, for instance. That's another real-life example of someone who is jazzed about the new doors pure Java is opening up for their products.
And you just recently heard Marc Andreeson announce that Netscape plans to develop a 100% Pure Java version of Communicator. This is phenomenal. If you think about the amount of engineering resources Netscape has to commit in order to port software to all those platforms and then think about focusing those resources on adding new features and functionality rather than porting its not hard to see why developing in 100% Pure Java would be a big competitive for Netscape.
Q: You mentioned earlier that developers were understanding their code better as a result of the testing process. Can you elaborate on that?
A: It's a combination of things. One comment made was basically, "I didn't know that was in there. I'm going to fire the guy that put that in there when I get back to the office." Now, we think he was only kidding, but it's an example of how a manager that may have perhaps 20 developers working on a program, simply cannot know what everyone is doing at all times.
So this is really a good QA procedure, which is somewhat unexpected. We looked at this a hurdle for firms to pass to prove they coded pure Java applications. We were not thinking of this as QA step for developers, but that is really what this is turning out to be.
Q: Some Java developers talking about their experience mention having to break C++ programming habits, or some other programming habits. It sounds like you're finding cases where non- Java elements or programming styles are creeping into programs inadvertently.
A: Exactly. And a lot of people will take the easy way out, even though it may not be the best solution. Folks are human and they gravitate to what they already know, or what is easiest to do. So this is a way for managers or developers to confirm that what they think is in the application is really there. It is a great safety check to make sure there is nothing lurking in the application.
Q: Is there a specific URL where certified companies will be listed.
A: There will be a 100% Pure Java Hall of Fame that will not only list all the companies certified, but will also profile in some depth, about half a dozen companies a month. Once that is ready the Hall of Fame will be accessible from the JavaSoft Web site.
Q: You mentioned Microsoft several times. Is the whole 100% Pure Java program an anti-Microsoft campaign?
A: No, it really isn't. It may look that way to some people and we've been questioned about that, but that really is not our goal. We are against anything that makes the technology proprietary. It doesn't matter who it is. We are against anything that would make Java programs work on just one platform because that is not what Java is all about.
The whole purpose of Java and what the 100% Pure Java program is designed to ensure, is that a pure Java program will run anywhere there is a Java VM. The whole idea is to make it transparent. The user should not have to care what kind of machine they have and developers shouldn't have to care what machines their target customers are on.
We are against the status quo style of computing where you have your platform and I have mine, and now we have to find out how to make them talk to one another. That is what we're against.
Q: Software development going back to the early UNIXTM days has always wrestled with the tension of portability and cross-platform support, versus platform-dependent tweaks for various purposes. Is this a way to get people focused on the real goal and to take a long- term view of application development?
A: That is definitely part of it. Again we are talking about an Internet where a company can talk not only to their own employees, who use a lot of different platforms, but also to their customers and suppliers. So yes, it is important to take a longer term view of things.
Q: You mentioned companies have to pay a fee for the certification. Why is that?
A: Originally we were going to use the honor system and have ISVs certify their own applications. The more we thought about it the more we recognized all the problems that might arise. Once we decided we were going to use an outside testing house it was pretty automatic that we would have to charge for certification. That is a fairly standard industry practice used for Microsoft Windows and Novell certification.
There is a flat fee for the initial certification and then a smaller fee to certify new versions of the product.
This is not a royalty payment for use of the 100% Pure Java logo. It is a payment for the labor and equipment that KeyLabs puts into the certification process.
None of those funds come back to JavaSoft. Since the tools have proven so useful we hope the ISVs will see this as a QA service as well as certification.
Q: Can a program be pure Java -- everything done according to spec. -- and still have inappropriate variations?
A: Yes. That is one of the reasons we are doing these tests. And that is why writing a program entirely in Java does not necessarily translate into cross-platform performance. There are things you can do in Java that will limit cross-platform capabilities. That is one reason why we wanted independent certification.
Q: Once a developer thinks the application is ready to go, how long does certification take?
A: Once it is submitted to KeyLabs it takes five working days -- ten days tops. Key Labs is committed to a five working day turn around, but we are not holding them to that yet. No one has ever tried to do multi-platform certification before. Everything has always been targeted to one specific platform.
Q: You've described the testing procedure. What other kinds of things do businesses need to do to prepare for certification?
A: There are several things freely available to developers even before they decide to register to begin the certification process.
The developer's Certification Steps mentioned earlier are available free on the Web. That is a good source of dos and don'ts, and technical descriptions.
The certification guide that details the steps the developers must go through and the steps that KeyLabs will perform is also available on the Web so that developers can understand the process.
And finally we've also made JavaPureCheck freely available to developers. It can be downloaded from SunTestTM's web site.
Q: Are there types of Java products that are not appropriate for the 100% Pure Java certification program?
A: There certainly are differences and there will be different criteria for certification. We have separated applets from applications, and both of those from components, or JavaBeansTM. So we are trying to take each major category and look at it carefully to see what fits.
Today we have requirements in place for applications, applets, and class libraries. Class libraries are a good example of some of the fine tuning that needs to be done. Class libraries are things other ISVs may use to build their own applications, so the requirement as far as how much of the code is covered in the automated test driver is much stricter for class libraries. We think it is important for ISVs to be confident that if a class library is certified as 100% Pure Java it will not introduce any impurities into an application that uses it.
Q: What about non-ISVs? Does 100% Pure Java certification make sense for people who are not reselling the software they write?
A: We expected the program to appeal mostly to ISVs, but since we announced the program in December 1996 at Internet World, we've had 4,000 people complete the request for information on our Web site and 40 percent of those have been corporate developers.
They are telling us that they want help on how to write 100% Pure Java applications. Obviously the marketing assistance and the logo are far more important to ISVs.
Internal developers want to be sure that the applications they write will run across their intranet or in their business partners' desktops across the Internet. Of course, Java's security model is also very important to these developers.
Corporate developers that register for the certification program also get access to the multi-platform test script generator and the multi- platform test software.
Q: What does the 100% Pure Java logo indicate for software that is certified?
A: It is an assurance of a true cross platform application that can run any place there is a Java-compatible VM. It is also important to point out that 100% Pure Java applications guarantee that Java's much-touted security model isn't corrupted.
Q: Is there anything that the 100% Pure Java brand does not guarantee?
A: Yes. It does not guarantee how well the application will do what it claims to do. Take the example of a calculator. We don't test whether punching in two plus two gives the correct answer of four. We do test that the result is the same across every platform. So we do not guarantee that developers have written a good application. The 100% Pure Java program does provide assurance that it will run the same on all the Java platforms.
Q: Is there anything you wanted to say that I didn't give you the chance to say?
A: This effort is evolving more and more into an industry initiative with key partners, the ISV community and end-users. IBM is now offering pre-testing in their Validation Centers. Soon we'll see Novell and Oracle following suit. So our partners are working with us very closely to grow the support and services that the Initiative offers.

楼顶是北大的高才生？@_@

低才生。
我在个人资料中好像没有写我是哪里的吧。
难道是看我的ip？

：）你很聪明，不过猜对了一半

就一个 200kb 的 hyperlink.dll ？