ObjectFrontier Releases FrontierSuite for JDO 1.0


News: ObjectFrontier Releases FrontierSuite for JDO 1.0

  1. ObjectFrontier announced that they have released FrontierSuite for Java Data Objects (JDO) version 1.0. The product is fully JDO 1.0 compliant and is built on top of ObjectFrontier's mature O/R Mapping and distributed caching technology, supports forward and reverse engineering (from DB Schema's), and integrates with the major appservers.

    Check out FrontierSuite for JDO 1.0.

    Press Release
    ATLANTA--(BUSINESS WIRE)--June 13, 2002--ObjectFrontier, Inc., a provider of component and service oriented enterprise software, announced that they have released FrontierSuite for Java Data Objects (JDO) version 1.0, a JDO implementation, for general availability today.

    This product is one of the first products to comply with the recently approved JDO 1.0 specification and is the only major product with a comprehensive development environment to support developers.

    FrontierSuite for JDO is a JDO implementation with a powerful JCA compliant persistence engine and a Model Driven Architecture (MDA) based development environment for designing, developing, deploying and running JDO applications. It provides transparent persistence to data using any JDBC compliant RDBMS as the data store, in both managed and non-managed environments. It is the latest addition to the flagship product of the company, FrontierSuite, and brings the tested, proven, mature persistence technology of ObjectFrontier in the field of O/R mapping and transparent java persistence into the JDO world.

    "FrontierSuite for JDO is the first product, I believe, with a comprehensive development environment for building JDO applications and one of the very few that support JDO 1.0 specification. It will cut into the development lifecycles of enterprises engaged in the process of building JDO applications. We at ObjectFrontier believe our modularized approach to building and running JDO applications will provide a variety of enterprises an easy and cost effective way to migrate to JDO standard based persistence solutions for their enterprise needs," said Dominic Savio, CTO at ObjectFrontier.

    FrontierSuite for JDO 1.0 and other related products can be ordered online at www.ObjectFrontier.com. FrontierSuite family of products are priced attractively as follows: FrontierSuite for JDO - $1,299.00, FrontierSuite for J2EE - $4,599.00, FrontierSuite for J2SE - $2,599.00 are all priced per developer license with no runtime or server fees.

    About ObjectFrontier

    ObjectFrontier is a provider of component and service oriented enterprise software. ObjectFrontier's robust and scalable products are based on open standards and can easily be integrated with market leading applications. Global 2000 Companies, System Integrators and Independent Software Vendors are the primary users of ObjectFrontier technology.

    ObjectFrontier is a charter member of JDOCentral.com.

    For more information, contact us at 770-777-8180 or visit www.objectfrontier.com.

    Threaded Messages (6)

  2. Interesting....[ Go to top ]

    These guys also support EJB. Any performance metrics ie. Comparision between EJB and JDO would be very interesting? Any major App server vendors supporting JDO.
  3. Interesting....[ Go to top ]


    It looks like you have been reading our mind. One of our next initiative is to do some benchmarks between JDO vs EJB using our MDA compliant FrontierSuite. Being a single vendor supporting both EJB and JDO from the same tool "FrontierSuite" we can provide unbiased opinion on performance etc. Keep tuned for this.

    I am not sure if any major app server has come forward with support for JDO as of yet. FrontierSuite for JDO does support application servers like WebLogic, WebSphere, Oracle, JBoss etc both in a Managed and Non-Managed Environment. If you are interested we offer a free evaluation copy at www.ObjectFrontier.com.

    Some of the features of FrontierSuite for JDO are:

    * JMS based distributed caching with synchronization.
    * Complete life cycle states of the JDO (Mandatory states) are supported
    * Support for multiple transaction modes - Optimistic, DataStore-Exclusive (Pessimistic), DataStore-Shared(Optimistic/Blind-update) during data retrieval and storage.
    * Support for Non-transactional read/write operations
    * Prepared statement caching.
    * Support for relationships like inheritances, binary associations and aggregations
    * Persistence for JDO in managed environments, leveraging the transparentservices provided by the application servers, like transactions, connection pooling.

    Shirish Shetty
  4. No Runtime-Wow![ Go to top ]

    Finally. The press release says no runtime and I confirmed calling their office. I have used FrontierSuite for J2EE about 6 months back and we never went to production because they were charging runtime fees. Without runtime (and all the great features) I believe they should make the O-R landscape very interesting.
  5. Doesn't CMRs in EJB 2.0 make OR Mapping Tools redundant to a large extent?

  6. CMR defines a standard mechanism to do relationships. However, I would never want to hand edit the XML deployment descriptors to do this!

    I want to use a tool (be it XDoclet, or a GUI) to generate all of that *stuff* for me. Also, not all OR runtimes are equal, and we have to make sure that we get the performance that we need!
  7. Why do you need OR tools?[ Go to top ]

    Hi Chuck,

    CMR in EJB2.0 is a standard way of specifying container managed relationships. Most of the application servers do support EJB2.0 but they do not provide GUI based development tools and powerful runtime functionalities. For example,

    1) If you plan to migrate your existing application into EJB platform and want to reverse engineer your existing relational database into EJB2.0 model, then OR tools provide you the migration path.

    2) If yu want to start from Object Model and take it all the way to EJB2.0 code generation, mapping the object model to relational database, deployment file creation along with EJBQL validation before deployment - all these functionalities are provided by OR tools.

    3)OR tools also provide you the choice of choosing the persistence model, for example EJB2.0 or JDO1.0 or proprietory specification based, depending upon your requirements: performance, complexities, funtionalities.

    4)In the runtime, OR tools can provide you performance using optimistic concurrency control, process level caching and also distributed caching in a clustered environment .

    Most of the application servers apecify a DTD for you to provide the required mapping (with limited capabilities). It might look easy at first look. But when you are working on a project involving many entities, even with 50-100 entity objects, managing the xml file manually and providing life cycle management for your application development is not an easy task.

    Also, EJB2.0 is the only choice available with application servers now, where as you can choose JDO1.0 with OR tools for higher performance, ease of development as there is no interface contract, powerful optimization control for the developer and so on.

    I just tried outlining few points - why you need to consider using OR tools.

    Dominic Savio
    ObjectFrontier Inc