We don't use stored procedures since they will result in a non-portable application. Our design allows, however, for stored procedures to be added elegantly--all you need to do is to provide an alternate Data Access Object that plugs into the application architecture and makes stored procedure calls. These are essentially a performance optimization that are particular to a specific application and its deployment environment.

No. To some extent, this falls into performance optimization. We do provide strategies such as using a Stateless Session Bean EJB to hold onto reuseable resources and the ServiceLocator pattern. We don't really address caching of application data very much. We also have some strategies for extending the petstore app to do some caching which have been discussed on the J2EE BluePrints interest list.

The purpose of the JavaTM Pet Store Demo is to illustrate design patterns and advanced coding strategies that relate directly to the Java programming language and specifically to the JavaTM 2 Platform, Enterprise Edition (J2EETM). A genuinely ported application would have to implement the same design patterns and same coding strategies to really be comparable.

The Java Pet Store Demo is designed to provide as much sample code as possible for the key aspects of the latest release of the J2EE platform. We deliberately added more code to create a flexible architecture that is fully object-oriented. We were trying to show off concepts and design patterns of Java Enterprise BluePrints, and hence there is more code. Our goal is to offer the developer community a well designed sample application.

The Java Pet Store Demo was not created to be a benchmark. The most important function of the Java Pet Store Demo is to educate. It was meant to illustrate design patterns and best practice guidelines for many important aspects of J2EE applications such as portability and maintainability: Portability gives the developer freedom of choice in selecting the optimal platform for their needs and in reducing the time and effort of migrating from one platform to another.

Yes. Sun has recently released the Java 2 Platform, Micro Edition (J2ME) Wireless Toolkit to support the development of client software running on cell phones, two-way pagers, and palmtops. The Java BluePrints program publishes guidelines for developing mobile applications using J2ME clients that connect to J2EE application servers. The Java Smart Ticket Demo illustrates those guidelines in the context of an electronic ticketing scenario.

They are complicated for the same reason that the dashboard of a fighter jet is more complicated than your car's dashboard: because you're controlling a lot more power and functionality. Deployment descriptors are complicated because they configure J2EE technology components and their containers. J2EE containers provide a high level of standard services (transactions, security, persistence, thread safety, etc.

The annual J2EE Deployathon clearly demonstrates that the Java Pet Store Demo is extremely portable. Java Pet Store Demo 1.1.2 has successfully been deployed on 9 different J2EE platform/operating system combinations. The Java Pet Store Demo can run on any operating system that supports the J2EE platform. It is possible to run implementations of the J2EE platform on Windows 98 but the recommended systems are Solaris, Linux, Windows NT, or Windows 2000.

Yes, the version 1.3.1 of Java Pet Store Demo demonstrates this. Sun has recently released new Java API standards on web services that illustrate the means for extending the Java Pet Store Demo.

In the proc table of the mysql system database. However, you should not access the tables in the system database directly. Instead, use SHOW CREATE FUNCTION to obtain information about stored functions, and SHOW CREATE PROCEDURE to obtain information about stored procedures. See Section 13.5.4.8, "SHOW CREATE PROCEDURE and SHOW CREATE FUNCTION Syntax", for more information about these statements. You can also query the ROUTINES table in the INFORMATION_SCHEMA database - see Section 22.

With Oracle, console output from System.out.println() statements will be written to trace files in the Oracle UDUMP destination directory.

We strive to make Wicket available for the largest possible number of developers. This means that we have to take into account those developers that don't have the luxury of running their application servers on Java 5. Many shops don't run on Java 5 yet. We would be doing ourselves and our users a great disservice when we would target Java 5 as our base platform. several members of our community have pointed out, there is a code converter for running Java 5 code on a Java 1.

The first reason being that initially a Java Virtual Machine was only available to users of 32 bit operating systems such as Windows/95 and so users of 16 bit operating systems such as Windows 3.1 would not be able to run the applets.

Yes. For a database named dbname, use this query on the INFORMATION_SCHEMA.ROUTINES table: SELECT ROUTINE_TYPE, ROUTINE_NAME FROM INFORMATION_SCHEMA.ROUTINES WHERE ROUTINE_SCHEMA='dbname'; The body of a stored routine can be viewed using SHOW CREATE FUNCTION (for a stored function) or SHOW CREATE PROCEDURE (for a stored procedure). See Section 13.5.4.8, "SHOW CREATE PROCEDURE and SHOW CREATE FUNCTION Syntax", for more information.

Unfortunately, the official specifications are not freely available (ANSI makes them available for purchase). However, there are books - such as SQL-99 Complete, Really by Peter Gulutzan and Trudy Pelzer - which give a comprehensive overview of the standard, including coverage of stored procedures.

Not in MySQL 5.1. We intend to implement the SQL standard SIGNAL and RESIGNAL statements in a future MySQL release.

MySQL implements HANDLER definitions according to the SQL standard. See Section 18.2.8.2, "DECLARE Handlers", for details.

Hopefully, NEVER! Every attempt has been made by the Cavalier Kennel Clubs to prevent Cavaliers from falling into the hands of puppy mills or anyone who would resell the dog. The Cavalier breeders adhere to the Code of Ethics which specifically excludes providing any puppies for resale. Responsible Cavalier breeders do their best to screen any prospective puppy buyer and often refuse to sell to a less than "ideal" home