经验交流系列二：Java Pet Store Sample Application研究学习！！！

Version 1.3_01: (For J2EE SDK 1.3.)

先说，我还没研究过，近期准备
听一位J2EE高手说：study petStore is just the beginning
哎真惭愧啊

分析其构架，细到具体的code，各种J2EE技术如何应用，以及如何将他们集成为一个整体！

J2EE体系很庞大，单单从概念上区分EJB,JavaBeans,JDBC,JNDI,JSP,Servlet,JAAS,Java Web Start,RMI,CORBA,message-driven EJB,.....
确实头疼，同时理解上也因人而已，有些人会理解的到位一点，有些人会欠缺些，不过没关系，因为，我们知道，实践是检验真理的标准！！！幸好，http://java.sun.com/blueprints/提供了这样一个设计例子，Java Pet Store Sample Application，Version 1.3_01: (For J2EE SDK 1.3.)
其比较宏观的设计大概在：《Designing Enterprise Applications with the J2EETM Platform》
，second edition里面。http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/index.html提供了该书的pdf文件，book.pdf同时，
Java Pet Store Sample Application，Version 1.3_01: (For J2EE SDK 1.3.)的下载地址在：http://java.sun.com/blueprints/code/index.html#java_pet_store_demo我希望，大家在分析该例子时，先把book.pdf,好好学习一下！然后再将其发布到J2EE RI 1.3,上去！下载demo后，将其解压到特定目录，如：
E:\petstore1.3_01其目录结构为：
E:\petstore1.3_01>dir
驱动器 E 中的卷没有标签。
卷的序列号是 E026-ABEA E:\petstore1.3_01 的目录2002-05-09  19:47       <DIR>          .
2002-05-09  19:47       <DIR>          ..
2002-01-25  15:58                2,900 COPYRIGHT
2002-01-25  15:58                9,570 LICENSE
2002-01-25  15:58              801,215 petstore.ear
2002-01-25  15:58              128,153 opc.ear
2002-01-25  15:58              111,491 supplier.ear
2002-01-25  15:58              461,147 petstoreadmin.ear
2002-01-25  15:59               14,980 setup.xml
2002-01-25  15:59                2,499 setup.sh
2002-01-25  15:59                2,199 setup.bat
2002-05-09  19:47       <DIR>          docs
2002-05-09  19:47       <DIR>          src
2002-05-09  21:39                  453 cloudscape.LOG
              10 个文件      1,534,607 字节
               4 个目录  3,615,268,864 可用字节E:\petstore1.3_01>demo的发布说明文件在docs目录下，希望大家按照说明，将demo配好！！！

bea weblogic6.1中有这个PetStore，使用起来比较方便。

但其版本比较低，我们的研究对象为：Version 1.3_01: (For J2EE SDK 1.3.)更何况，在新版本中，改动很多！http://java.sun.com/blueprints/code/jps13/datasheet.html其新加了如下几方面的特性：JMS integration with EJB technologyEJB container-managed persistence ("CMP")Local interfaces for EJB componentsLocal interfaces for EJB componentsJFC/Swing clients deployed using JavaTM Web StartJavaTM APIs for XML

http://java.sun.com/features/2002/05/2mil.htmlTWO MILLION AND COUNTING
The JavaTM 2 Platform, Enterprise Edition (J2EETM) celebrates another million developer downloadsby Laurie Weber Fritz
May 13, 2002 -- On April 8, Java technology achieved yet another milestone, the two-millionth download of the Java 2 Platform, Enterprise Edition (J2EE) Software Developer Kit (SDK), proving that the Java platform is one of the most successful industry collaborations ever.It's an event that could not have happened without great minds involved in the creation of this very technology, the Java Community ProcessSM program (JCPSM). From its early days, Sun initiated and participated in standard-setting efforts, from the Network File System (NFS), to CORBA, to Java technology. Now nearly a $2 billion et, the community's continued growth and the sheer number of downloads demonstrates the success of the open standards approach.At the core of Java platform is the "Write Once, Run AnywhereTM" premise. The fact that applications can be developed and deployed on standard desktop platforms, as well as on massive servers from Sun and other vendors, has resulted in a seamless, highly productive development model along with a highly scalable deployment model.In terms of extensibility, the Java platform has proven that it has the ability to evolve to meet industry requirements. The J2EE 1.3 release added the J2EE connector architecture for better integration with enterprise information systems. This specification also includes the Java Messaging ServiceTM (JMS) API and Message-Driven Enterprise JavaBeansTM (EJBTM) specification to support loosely coupled applications and improve the container-managed persistence features introduced in the first version of the platform.Today, the JCP program continues to create and enhance a compatible, comprehensive and extensible services platform. Technologists and business people representing multiple industries and ets are maintaining and extending the Java platform, keeping it cutting-edge, complete, and compatible. Compatibility levels the playing field for the Java community, because open standards provide a common foundation that enables companies to compete on implementation. The community can now compete on what's really important to customers: features, performance, security, and scalability.As Judith Lilienfeld, Senior Product Manager for Sun's J2EE Compatible Markets, stated, "Java is all about freedom of choice. It's about open products, platforms, components, and applications." Attaining compatibility isn't easy, but it's worth the effort because it can help enlarge a company's et share. The Compatibility Test Suite (CTS) assures that application servers and applications written for them conform to specification and are portable. A total of 13 vendors have passed the J2EE 1.3 specification compatibility test, and their products have passed 15,000 tests. At this point, more than 35 J2EE Compatible products are offered. "Sun did not just go out there with a specification. We had a reference implementation, compatibility testing, and the Java BlueprintsTM program," said Lillienfeld. We actually built what we specified."Grassroots Support from Day One.Interestingly, the groundswell of interest among developers and partners in Java technologies on the server started even before the platform became available. First came JDBC technology for the enterprise, which was a huge success. Then, Java Servlets and JavaServer PagesTM (JSPTM) technology, which extended the platform's support for Web application development, were quickly adopted by server vendors. The addition of EJB technology, with a component-based model for transactional application development, was the final piece in the puzzle.Today, the J2EE standard represents collaboration between leaders from throughout the enterprise arena. Sun's software partners include OS and database management system providers, middleware and tool vendors, vertical-et applications and component developers. These companies have helped define a robust, flexible platform that can be implemented on the wide variety of existing enterprise systems currently available, and that supports the range of applications IT organizations need to keep their enterprises competitive.J2EE Platform Statistics:
The Platform of Choice for Networked Applications80% of all enterprises use the Java language (Gartner)
92% of companies that choose J2EE technology for enterprise computing are happy with their choice (Forrester)
78% of executives view J2EE technology as the most effective platform for building and deploying Web services (Giga poll)
58% of developers choose Java technology for Web services (above SOAP, LDAP, WSDL, UDDI) (Evans).
The J2EE platform et is $2 billion strong and growingIn fact, J2EE technology has established itself as the platform of choice for building networked enterprise applications and services. Application server software companies, in particular, have adopted J2EE as the foundation for their products because of its flexibility and scalability. Using a branded J2EE-compatible implementation, companies can build networked applications and services that connect with their legacy applications and data, allowing them to leverage their 30-year investment in programs and data via the network.In addition, as part of the larger Java platform, J2EE also interoperates seamlessly with the Java 2 Platform, Micro Edition (J2ME [TM]) to connect enterprises, carriers, and service providers with modern clients. These include newly empowered devices such as cell phones, PDAs, and smart cards that are joining the traditional client -- the PC -- to create a new, end-to-end networked services paradigm. Several working groups in the Java Community Process are currently defining individual extensions to the Java platform that support Web services.Tracey Stout, Sun's Vice President of Marketing for Java and XML Software explained, "While we celebrate the success of Java technology on the server with this J2EE download milestone, the real winners are the millions of developers who recognize that it's all one platform, from smart cards to mobile devices to rich clients like desktops to massive server complexes. Those developers' Java platform development skills apply across the whole spectrum."Java Technology Enables One World of Communication.Rather than a world of technical fragmentation, where each vendor's offering is proprietary, or a world of monolithic technology, where choice is minimized to a single vendor, Java technology empowers a range of possibilities in smart cards, on palm tops, in wireless phones, on the desktop, and on the server. By seamlessly integrating these devices -- and more importantly, the high-value services they provide to users -- Java technology enables more and more people to remain effective, in touch, and in charge of the world they live in."Wireless and mobile applications play a big part in this growth," continued Rich Green, Sun's Vice President and General Manager of Java and XML software, "When people talk about Java technology in the mobile space, they tend to focus on the client. Of course, we have a great story there, with J2ME technology in phones and PDAs. But when millions of devices are making billions of transactions, the heavy lifting happens on the server, where the Java platform rules."Now the Java platform is the foundation for Web and networked services. Its openness and flexibility have positioned it as the cornerstone of the SunTM Open Net Environment (SunTM ONE) -- Sun's vision, platform, architecture, and expertise for delivering Services on Demand today and tomorrow.

我这里有chm形式的源码格式需要的话，留下EMail

多谢,多谢！
[email protected]

多谢！多谢！多谢！
[email protected]

pet store1.3.01我看的差不多了，完全是一个半月苦读代码的结果。我现在正在用他的架构做项目。
1.3.01变了好多东西，看起来真要命。

怎么没有高手进来讨论那？是否大家都没有研究过？还是觉得自己水平高，不屑于和我们交流？希望高手们多多指教？同时还可以谈谈如何研究pet store入手，毕竟pet store里面包含了33个EJB！我在配置时，按照DOC首先，完成一些初始化工作结果如下：E:\petstore1.3_01>setup.bat
Buildfile: setup.xmlinit:help:create_jms_queues:
     [echo] Creating JMS Queues ....
     [java] JmsDestination
     [java] --------------
     [java] < JMS Destination : jms/Topic , javax.jms.Topic >
     [java] < JMS Destination : jms/queue/opc/OrderQueue , javax.jms.Queue >
     [java] < JMS Destination : jms/queue/supplier/PurchaseOrderQueue , javax.jm
s.Queue >
     [java] < JMS Destination : jms/queue/opc/OrderApprovalQueue , javax.jms.Que
ue >
     [java] < JMS Destination : jms/topic/opc/InvoiceTopic , javax.jms.Topic >
     [java] < JMS Destination : jms/queue/opc/MailQueue , javax.jms.Queue >
     [java] < JMS Destination : jms/queue/opc/MailOrderApprovalQueue , javax.jms
.Queue >
     [java] < JMS Destination : jms/Queue , javax.jms.Queue >create_users:
     [echo] Creating users ....
     [java] Group default has been added successfully.
     [java] This change will take effect after starting the J2EE server.
     [java] User jps_admin has been added successfully.
     [java] This change will take effect after starting the J2EE server.
     [java] User rcvr has been added successfully.
     [java] This change will take effect after starting the J2EE server.create_petstore_db:create_supplier_db:create_opc_db:core:
     [echo] The J2EE SDK is now successfully configured to run the petstore appl
ication. Please restart cloudscape and the j2ee servers, and deploy all the ear
files. You can do this by issuing the following commands:
     [echo] change directory to j2sdkee1.3/bin; start RI and Cloudscape in separ
ate windows
     [echo] cloudscape -start
     [echo] j2ee -verbose
     [echo] change directory to petstore1.3 to deploy the EAR files
     [echo] setup.bat deploy (or on Unix, setup.sh deploy)BUILD SUCCESSFULTotal time: 1 minute 51 seconds

各位大侠都把email留下吧
以后有j2ee问题可以向大家请教亚
我的email:[email protected]

然后，启动服务器，配置pet store应用程序！E:\petstore1.3_01>setup deploy
Buildfile: setup.xmlinit:deploy:
     [echo] Deploying ears ....
     [java] Deploy the application in petstore.ear on the server localhost savin
g the client jar as null
     [java] Sender object Deploy Tool : Deploy PetStoreEAR on localhost
     [java] Remote message: Contacted Server....
     [java] Remote message: Application PetStoreEAR transferred.
     [java] Remote message: PetStoreEAR has 15  ejbs, 1 web components to deploy
.
     [java] Remote message: Deploying Ejbs....
     [java] Remote message: Processing beans ....
     [java] Remote message: Making server JARs ....
     [java] Remote message: Making client JARs ....
     [java] Remote message: Contact the web server and ask it to run: e:\j2ee1.3
.1\repository\luoshifei\applications\PetStoreEAR1020946116516Server.jar .
     [java] Remote message: Web Components Deployed..
     [java] Remote message: Deployment of PetStoreEAR is complete..
     [java] Sender object Deploy Tool : client code at http://10.11.12.120:9191/
PetStoreEARClient.jar
     [java] Deploy the application in opc.ear on the server localhost saving the
client jar as null
     [java] Sender object Deploy Tool : Deploy OrderProcessingCenterEAR on local
host
     [java] Remote message: Contacted Server....
     [java] Remote message: Application OrderProcessingCenterEAR transferred.
     [java] Remote message: OrderProcessingCenterEAR has 11  ejbs, 0 web compone
nts to deploy.
     [java] Remote message: Deploying Ejbs....
     [java] Remote message: Processing beans ....
     [java] Remote message: Compiling wrapper code ....
     [java] Remote message: Compiling RMI-IIOP code ....
     [java] Remote message: Making server JARs ....
     [java] Remote message: Making client JARs ....
     [java] Remote message: Deployment of OrderProcessingCenterEAR is complete..     [java] Sender object Deploy Tool : client code at http://10.11.12.120:9191/
OrderProcessingCenterEARClient.jar
     [java] Deploy the application in supplier.ear on the server localhost savin
g the client jar as null
     [java] Sender object Deploy Tool : Deploy SupplierEAR on localhost
     [java] Remote message: Contacted Server....
     [java] Remote message: Application SupplierEAR transferred.
     [java] Remote message: SupplierEAR has 6  ejbs, 1 web components to deploy.     [java] Remote message: Deploying Ejbs....
     [java] Remote message: Processing beans ....
     [java] Remote message: Making server JARs ....
     [java] Remote message: Making client JARs ....
     [java] Remote message: Contact the web server and ask it to run: e:\j2ee1.3
.1\repository\luoshifei\applications\SupplierEAR1020946743876Server.jar .
     [java] Remote message: Web Components Deployed..
     [java] Remote message: Deployment of SupplierEAR is complete..
     [java] Sender object Deploy Tool : client code at http://10.11.12.120:9191/
SupplierEARClient.jar
     [java] Deploy the application in petstoreadmin.ear on the server localhost
saving the client jar as null
     [java] Sender object Deploy Tool : Deploy AdminEAR on localhost
     [java] Remote message: Contacted Server....
     [java] Remote message: Application AdminEAR transferred.
     [java] Remote message: AdminEAR has 1  ejbs, 1 web components to deploy.
     [java] Remote message: Deploying Ejbs....
     [java] Remote message: Processing beans ....
     [java] Remote message: Compiling wrapper code ....
     [java] Remote message: Compiling RMI-IIOP code ....
     [java] Remote message: Making server JARs ....
     [java] Remote message: Making client JARs ....
     [java] Remote message: Contact the web server and ask it to run: e:\j2ee1.3
.1\repository\luoshifei\applications\AdminEAR1020946969342Server.jar .
     [java] Remote message: Web Components Deployed..
     [java] Remote message: Deployment of AdminEAR is complete..
     [java] Sender object Deploy Tool : client code at http://10.11.12.120:9191/
AdminEARClient.jar
     [echo] The petstore application is now installed.
     [echo] Please restart your cloudscape database and the J2EE server, and the
n point your browser to http://localhost:8000/petstore to access petstore.BUILD SUCCESSFULTotal time: 19 minutes 32 seconds

别老讨论了，老老实实看看sun提供的guideline文档吧，太经典了！太经典了！太经典了！太经典了！太经典了！太经典了！太经典了！太经典了！
另外，建议从petstore1.0.1开始，那个东西，比较简单，
可以从中理解，前台控制器，Event,模版拼装等诸多东西，
然后，再看petstore1.3.1就容易多了，理解也深刻多了。java.sun.com/blueprints/
可以下载sun提供的两个版本的guideline文档，
one for 1.0.1, one for 1.3.1,all cool~

我仔细看了一下
petstore1.3和1.2的不同之处有这么几个
1. 1.3大量采用了CMP,这样在1.2中广泛采用的DAO模式我感觉在1.3中没有原来那么重要
2. 1.3中加入了message driver bean
3. JMS在1.3中好像也有不少应用
1.3的配置在不同服务器上有很多麻烦
我遇到的最主要的一点就是CMP的表主键在不同应用服务器上可能有很多种不同的方法，最主流的就使用一个序列的表，weblogic7.0已经可以自动生成这样一个表
建议大家结合weblogic7。0关于petstore的例子学习他，最好是把petstore重新修改编译然后放在不同的服务器上
最后一点,java的跨平台这个我感觉很搞笑，连不同服务器之间都要做很多调整，甚至修改源代码

[email protected];
我要.chm 各式的源代码，谢谢

调试易

经验交流系列二：Java Pet Store Sample Application研究学习！！！

解决方案 »