Return-Path: X-Original-To: apmail-db-jdo-dev-archive@www.apache.org Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 46AB910C3F for ; Thu, 22 Aug 2013 14:12:38 +0000 (UTC) Received: (qmail 56096 invoked by uid 500); 22 Aug 2013 14:12:33 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 56063 invoked by uid 99); 22 Aug 2013 14:12:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Aug 2013 14:12:30 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [209.85.212.180] (HELO mail-wi0-f180.google.com) (209.85.212.180) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Aug 2013 14:12:22 +0000 Received: by mail-wi0-f180.google.com with SMTP id l12so718705wiv.1 for ; Thu, 22 Aug 2013 07:11:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc :content-type; bh=i8DDLtpEqoMaDRnuq70eP0MyOSKZH2Huv/sXi3iwZsk=; b=LlbXP4v4UBSJgI71R3/Eqze+2QHn2+QtXtH1pRYZkCyAOp6qaIVY4SLtJ7MYOC8WDs gHOsVfT6rU1UyC1oJj44qSraAyYZsVzWHFXDWxKw7ktQEzNeRyArSp+DeoUbT7Tvlkby 2nOVV0ZNMHQTVN+ey18GwNSNEdlp0JZ6iKo/xUHOTuczFCloaINzOLuUCu19Pf9xacA7 Kt9ZPD5ZMFWMXhygPj70+3i6Bua9skc3KCZ7u6e4XFv5vAj6Y2Eo06xnxjAtRmlyl6b5 37bC5Jmcm+A4CfxrlU3yeGUG+/ONRdD6PgB2hVQ/ZKktuJ/dzaidSCadtfLNJZhd1P3m 16pA== X-Gm-Message-State: ALoCoQnjRWie38GwbCbNQohAtJSzbrGPrQNVg5qXO2PbuSNPgLjQEId1ZnVOQ/mEZyQzIXcZVxUE X-Received: by 10.180.11.37 with SMTP id n5mr20965523wib.25.1377180702191; Thu, 22 Aug 2013 07:11:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.39.130 with HTTP; Thu, 22 Aug 2013 07:11:22 -0700 (PDT) From: Matthew Adams Date: Thu, 22 Aug 2013 09:11:22 -0500 Message-ID: Subject: [persistence] To: peter.kriens@aqute.biz Cc: "jdo-dev@db.apache.org" Content-Type: multipart/alternative; boundary=001a11c25b488bba2d04e489dedf X-Virus-Checked: Checked by ClamAV on apache.org --001a11c25b488bba2d04e489dedf Content-Type: text/plain; charset=ISO-8859-1 *Note: copying the JDO developers alias.* I saw your poston using persistence technologies, and would like to extend you an offer to attend the JDO expert group's weekly conference call to discuss the matter. Here are the conference call coordinates. (CRAIG/MICHAEL/MICHELLE: can you please confirm the time for Peter? I can't tell if we've changed from 9 AM PT to 10 AM PT.) Dial-in numbers are: US Toll free: 866 682-4770 Germany Frankfurt 069222216106 Germany Toll free: 08006648515 (Other countries by request) To place the call: 1. Call the toll free number. 2. Enter the conference number 939-3689# 3. Enter the security code 1111# I have been a member of JDO since 2000, and was the primary driver for the 3.0.1 point releasethat added OSGi headers to the JDO API jar, so I can sympathize with your dilemma. While I suspect that the JDO specification itself, under the auspices of the JCP, should not address OSGi, I do believe that it's appropriate for the Apache JDO project to produce bits that help implementations better export the PersistenceManagerFactory and other interfaces. I would suggest that you work directly with the JDO implementations as well, especially DataNucleus (the JDO reference implementation), which I think has already done a fairly good job of supporting OSGi. Sincerely, Matthew -- mailto:matthew@matthewadams.me skype:matthewadams12 googletalk:matthew@matthewadams.me http://matthewadams.me http://www.linkedin.com/in/matthewadams --001a11c25b488bba2d04e489dedf--