FrontierSuite for JDO by ObjectFrontier 201 12.3 FrontierSuite for JDO by ObjectFrontier Contact addresses: www.ObjectFrontier.com and sales@ObjectFrontier.com FrontierSuite for JDO is a trademark of ObjectFrontier Inc. 12.3.1 About ObjectFrontier ObjectFrontier is a provider of component and service oriented enterprise software. ObjectFrontier s products focus on transparent persistence for Java objects and have been providing persistence solutions for the J2EE and J2SE platforms for the past several years. FrontierSuite, the company s flagship product, is a powerful JCA compliant persistence engine and a Model Driven Architecture (MDA) based development environment for designing, developing, and deploying enterprise applications. FrontierSuite has a mature persistence technology for both the J2SE and J2EE (both EJB 1. 1 and EJB 2. 0) environments. ObjectFrontier brings the mature persistence technology and the experience gained in providing persistence in various platforms into FrontierSuite for JDO, claiming it to be the first product with a comprehensive development environment for building JDO applications. 12.3.2 About FrontierSuite for JDO FrontierSuite for JDO provides four modules for building and running JDO applications using different approaches. 12.3.3 Product Family 12.3.3.1 FrontierSuite for JDO (Forward Engineering) In this approach, building a new JDO application from scratch is supported. The input for this approach is a UML based project model for persistent objects. The development environment provides tools for defining or importing UML object models. It then automates the entire process of generating PersistenceCapable classes from the object model through Frontier Builder, a code generator tool. Finally, mapping of the classes to an underlying RDBMS scheme is accomplished through Frontier Fusion, an object-relational mapping tool. 12.3.3.2 Frontier ReModeler for JDO (Reverse Engineering) This approach to JDO application building provides a migration path for enterprises moving to the JDO standards whilst re-using an existing database
Note: If you are looking for best hosting provider to host and run your tomcat application check Astra tomcat hosting services

200 JDO implementations 12.2.3.2 FastObjects j2 j2 Is a JDO-compliant pure Java embedded object database for smart devices. Concurrent sharing of data for multithreaded applications. Pure Java. Small footprint 450KB. Fault tolerance for mission-critical applications. 12.2.3.3 FastObjects e7 e7 is a JDO-compliant embedded object database for large-scale computer- controlled equipment. Secure sharing of data between processes. User authorization. Security add-on for data encryption. 12.2.3.4 FastObjects t7 t7 is a JDO-compliant multi-tier object database for large distributed applications. Secure sharing of data between hosts. User authorization. Client-side caching of objects. Pre-fetching of object graphs. Security add-on for data encryption. Fault-tolerance add-on for mission-critical applications. 12.2.4 Supported data stores FastObjects databases are specifically built to work in non-managed embedded environments. Typical FastObjects applications are turnkey software applications and computer-controlled equipment. 12.2.5 Supported application servers FastObjects t7 is a multi-tiered version that works within J2EE application servers. Example application servers include JBoss and Borland AppServer.
Note: If you are looking for best hosting provider to host and run your tomcat application check Astra tomcat hosting services

FastObject by Poet Software 199 12.1.3 Supported data stores Versant ODBMS. 12.1.4 Supported application servers The following application servers are supported: IBM WebSphere BEA WebLogic. 12.2 FastObjects by Poet Software Contact addresses: www.fastobjects.com and sales@fastobjects.com FastObjects is a trademark of Poet Software Corporation. 12.2.1 About Poet software Poet Software provide embedded database components for smart devices and turnkey software applications. FastObjects embedded databases improve the reliability and performance of sophisticated data-intensive applications. Unlike general-purpose data engines, FastObjects is built to meet the specific needs of OEMs with features that improve ease of operation and simplify lifecycle management of durable long-lived products. 12.2.2 About FastObjects All FastObjects embedded databases share the following features: easily accepts any data structure; rapid data storage, search, and retrieval for Java; ensures consistency of data; fully automated maintenance; support for field-upgradable products; compliant with JDO standard. 12.2.3 Product family Each member of the FastObjects product family augments the standard features as follows. 12.2.3.1 FastObjects j1 j1 is a JDO-compliant pure Java community edition object database. Free for non-commercial development.
Note: If you are looking for top 10 and very good webhost to host and run your jsp application check Actions jsp hosting services

198 JDO implementations In addition to the textual information, each vendor was invited to supply a list of supported features for their GA release (general availability as at March 2002), and for their next planned release if they wished. Most vendors supplied this information, which is collated in Table 12.1. Since this information was sourced, two further JDO implementations have been announced. These are JDOGenie and FrontierSuite for JDO , each of which is discussed during this chapter but does not feature in the comparison table. This information is intended to raise awareness of the various companies and products that are active in the JDO community. It is interesting to note that, with JDO only recently finalized, many vendors already have commercial products that will shortly implement almost the entire specification. This is in stark contrast to previous efforts by the ODMG to standardize access to object databases, for which the vendors of the day provided only partial support. Finally, please note that a number of factors must be borne in mind in choosing an implementation. Even though a vendor may claim that their implementation supports every optional feature in the specification, this does not mean that the features are efficiently implemented. Nonfunctional characteristics must also be considered, including, but not limited to, factors such as performance, scalability, support, ancillary services (e.g. training), and cost. 12.1 enJin by Versant Contact addresses: www.versant.com and sales@versant.com enJin is a trademark of Versant Corporation. 12.1.1 About Versant Versant Corporation (NASDAQ: VSNT) has led the industry in highly scalable, reliable object management solutions for complex, enterprise-level systems since its founding in 1988. The company s ODBMS serves as the core database for fraud detection, yield management, real-time data collection and analysis, operation support systems, and other large-scale applications in the telecommunications, financial services, transportation, and defense industries. 12.1.2 About enJin Versant enJin speeds the development and performance of applications requiring transactional storage, distribution, and caching of objects from EJBs and JSPs/Servlets in the middle tier.
Note: If you are looking for top 10 and very good webhost to host and run your jsp application check Actions jsp hosting services

JDO implementations 197 Table 12.1(Continued) Optional feature support, as at March 2002 Product LiDO Open Orient PE.:J Fusion Version 1.2 1.3 1.1 2.x 2.0 2.1 2.0 3.0 Status GA Plan GA Plan GA Plan GA Plan TransientTransactional .. .. .. .. NontransactionalRead …. .. .. NontransactionalWrite …. …. RetainValues …… .. RestoreValues …. …. Optimistic …… .. ApplicationIdentity .. …. .. DatastoreIdentity .. .. .. .. NondurableIdentity …. …. ArrayList .. .. .. .. HashMap …. .. .. Hashtable …. .. .. LinkedList .. .. …. TreeMap …. …. TreeSet …. …. Vector .. .. .. .. Map …. .. .. List .. .. .. .. Array …. .. .. NullCollection .. …. .. ChangeApplicationIdentity …… .. JDOQL .. …. ..
Note: If you are looking for cheap and quality provider to host and run your java application check Astra java hosting services

JDO implementations 12 Our examination of JDO 1.0 is now complete. This penultimate chapter gives the reader an introduction to some of the most important JDO Implementations and the companies behind them. For each vendor there is a page or two about the company, their products, and the extent of their support for various data stores and application servers. Some of the products listed are object-relational mapping implementations which work with an underlying relational database. Others are themselves fully fledged object databases for which a JDO interface is provided. Table 12.1 Optional feature support, as at March 2002 Product Fast Objects JRelay Kodo JDO IntelliBO Version Status GA Plan 2.0 GA 2.1 Plan 2.2 GA 2.5 GA 3.0 Plan TransientTransactional .. ….. NontransactionalRead .. ….. NontransactionalWrite .. ….. RetainValues .. ….. RestoreValues .. ….. Optimistic .. ….. ApplicationIdentity .. ….. DatastoreIdentity .. ….. NondurableIdentity .. ….. ArrayList .. ….. HashMap .. ….. Hashtable .. ….. LinkedList .. ….. TreeMap .. ….. TreeSet .. ….. Vector .. ….. Map .. ….. List .. ….. Array .. ….. NullCollection .. ….. ChangeApplicationIdentity .. ….. JDOQL .. …..
Note: If you are looking for cheap and quality provider to host and run your java application check Astra java hosting services

Bootstrapping JDO in the managed environment 195 BusinessPartner bp = i.next(); %> <%= bp.getPartnerId() %> <%= bp.getName() %> <%= bp.getAddress() %> <%= bp.class.getName() %> <% } e.close(i); t.commit(); pm.close(); %> Note that a proper JSP should contain as little Java code as possible, instead delegating to helper classes through custom tag libraries. The above example ignores this precept for the sake of brevity. It is possible that future versions of JDO will include a library of JSP tags specifically for persistence management. 11.11 Bootstrapping JDO in the managed environment All of our discussions in this chapter have presumed that an appropriately configured PersistenceManagerFactory instance has already been instantiated and registered with the naming service, ready to be looked up through JNDI. But how is this achieved? Unfortunately there is no standard method. If JDO were to be accepted as part of the next release of J2EE, provision would be made for this bootstrapping through the J2EE configuration file resource.properties. In the interim, however, the mechanics of registering factories on application server startup must be addressed in conjunction with advice and documentation from the vendors of your chosen application server and JDO implementation products. What s next? In the next chapter I present a survey of the non-reference JDO implementations available as at March 2002.
Note: If you are looking for cheap and quality provider to host and run your java application check Astra java hosting services

194 J2EE integration public class PMFHolder { PersistenceManagerFactory pmf; public void setJNDIName(String jndiName) { Context ic = new InitialContext(); Context env = ic.lookup(”java:comp/env”); pmf = (PersistenceManagerFactory) env.lookup(jndiName); } public synchronized PersistenceManager getPersistenceManager() { return pmf.getPersistenceManager(); } } Here then is the JSP page itself. BusinessPartnerList.jsp <%@ page import javax.jdo.* %> <%@ page import com.ogilviepartners.jdobook.op.Product %> <%! PersistenceManagerFactory pmf %> <% OrderProcessingPMFHolder.setJNDIName ("OrderProcessingPMF"); %>

List of Business Partners

<% PersistenceManager pm = OrderProcessingPMFHolder. getPersistenceManager(); Transaction t = pm.currentTransaction(); t.begin(); Extent e = pm.getExtent(BusinessPartner.class, true); Iterator i = e.iterator(); while (i.hasNext) {
Note: If you are looking for cheap and quality provider to host and run your java application check Astra java hosting services

Posted in java | No Comments »

“); out.println(”“); out.println(”“); out.println(”“); out.println(”“); out.println(”“); } //end of table and document out.println(”

ID	Name	Address	Type
” + bp.getPartnerId() + “	” + bp.getName() + “	” + bp.getAddress() + “	” + bp.class.getName() + “

“); // output complete out.flush(); e.close(i); t.commit(); pm.close(); } } The above example employs JDO transactions, which does not rely on any specific J2EE transaction support from the servlet container. If the servlet were invoking EJB components for some of its processing, it would be unusual for it to access persistent objects directly as well. Instead, all access to JDO would typically be delegated to the EJB tier. However, if necessary, the servlet can look up the UserTransaction though JNDI and then demarcate J2EE transactions. With such an approach, the persistence manager must not be obtained from the factory until the J2EE transaction has been commenced. That s all I wish to say regarding servlets. We now look briefly at the same example rendered as a JSP. 11.10.2 JavaServer Pages In order to handle the JNDI lookup of the persistence manager factory, the JSP uses a bean called PMFHolder. This simple bean looks up the persistence manager factory according to the given JNDI name and then exposes a getPersistenceManager() method. The source code for the bean is shown below. PMFHolder.java package com.ogilviepartners.jdobook.op.j2ee; import javax.jdo.*; import javax.naming.*;
Note: If you are looking for good and quality webspace to host and run your java application check Actions java hosting services

192 J2EE integration public class BusinessPartnerServlet extends HttpServlet { PersistenceManagerFactory pmf; public void init(ServletConfig config) { super.init(config); Context ic = new InitialContext(); Context env; env = (Context) ic.lookup(”java:comp/env”); pmf = env.lookup(”OrderProcessingPMF”); } public void doGet(HttpRequest request, HttpResponse response) { processRequest(request, response); } public void doPost(HttpRequest request, HttpResponse response) { processRequest(request, response); } private void processRequest(HttpRequest request, HttpResponse response) { // get the persistence manager and begin transaction PersistenceManager pm = pmf.getPersistenceManager(); Transaction t = pm.currentTransaction(); t.begin(); // get the extent of BusinessPartner including // subclasses Extent e; e = pm.getExtent(BusinessPartner.class, true); Iterator i = e.iterator(); // commence output response.setContentType(”text/html”); PrintWriter out = response.getWriter(); // page header out.println(”