From dev-return-4862-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Wed Jul 11 12:07:40 2007 Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 52398 invoked from network); 11 Jul 2007 12:07:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Jul 2007 12:07:39 -0000 Received: (qmail 4124 invoked by uid 500); 11 Jul 2007 12:07:42 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 3979 invoked by uid 500); 11 Jul 2007 12:07:41 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 3965 invoked by uid 99); 11 Jul 2007 12:07:41 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jul 2007 05:07:41 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of frank.jagla@skally.de designates 80.245.132.6 as permitted sender) Received: from [80.245.132.6] (HELO mail.micram.de) (80.245.132.6) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jul 2007 05:07:35 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.micram.de (Postfix) with ESMTP id 0C2B82E221 for ; Wed, 11 Jul 2007 14:07:13 +0200 (CEST) Received: from mail.micram.de ([127.0.0.1]) by localhost (mail [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20949-07 for ; Wed, 11 Jul 2007 14:07:12 +0200 (CEST) Received: from uranus.micram.de (uranus [10.0.0.2]) by mail.micram.de (Postfix) with ESMTP id EA5EC27871 for ; Wed, 11 Jul 2007 14:07:12 +0200 (CEST) Received: from [10.0.5.22] (wsot03.micram.de [10.0.5.22]) by uranus.micram.de (Postfix) with ESMTP id 8E41A2C526 for ; Wed, 11 Jul 2007 14:07:08 +0200 (CEST) Message-ID: <4694C7F1.9070607@skally.de> Date: Wed, 11 Jul 2007 14:07:13 +0200 From: Frank Jagla User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: dev@openjpa.apache.org Subject: Re: Kodo 4 JDO Mappingtool - propagation of jdbc-type info References: <46936F15.6030304@skally.de> <4693D202.2020707@bea.com> <7262f25e0707102055w59616d8fwb6fb9c0950f5ab93@mail.gmail.com> In-Reply-To: <7262f25e0707102055w59616d8fwb6fb9c0950f5ab93@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at micram.de X-Virus-Checked: Checked by ClamAV on apache.org Hi David, hi Patrick, I appreciate your advice, but nevertheless i would like to understand the inner workings of the mapping and schema tools. My intention is to develop a hot patch for use in my company that helps us over the next few weeks. And of course, OpenJPA is a fascinating peace of software thats a pleasure to study! So, please, if possible, can you give some hints where to look? Where do those extensions get consulted? Who decides on initial mapping / subsequent update? Cheers Frank Jagla plinskey@gmail.com schrieb: > FYI, the reason that you're not seeing the updates is because those > extensions are only consulted when doing the initial mapping > generation, not on subsequent updates. > > -Patrick > > On 7/10/07, David Ezzio (asmtp) wrote: >> Hi Frank, >> >> I would approach your problem in a somewhat different manner than you >> have taken. Here's why. >> >> Any solution that you create in either OpenJPA or by overriding Kodo >> classes may be fragile due to the evolution of the products. It is also >> likely to be difficult, as you're discovering, due to a lack of >> documentation of the internal workings of either OpenJPA or Kodo. >> >> I think it would be much easier to write your own JDO metadata >> manipulator, perhaps using a XSLT, to force the updating of on-site >> deployed ORM files. Such code could then be integrated into your update >> script that runs at customer sites. This code would be affected only by >> the evolution of the JDO ORM schema which will be slow and well >> documented. >> >> Cheers, >> >> David Ezzio >> >> >> Mit freundlichen Grüßen Frank Jagla