Return-Path: X-Original-To: apmail-openjpa-users-archive@minotaur.apache.org Delivered-To: apmail-openjpa-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DCF409190 for ; Sat, 23 Jun 2012 09:17:37 +0000 (UTC) Received: (qmail 16811 invoked by uid 500); 23 Jun 2012 09:17:37 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 16562 invoked by uid 500); 23 Jun 2012 09:17:37 -0000 Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@openjpa.apache.org Delivered-To: mailing list users@openjpa.apache.org Received: (qmail 16519 invoked by uid 99); 23 Jun 2012 09:17:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Jun 2012 09:17:36 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bengt.rodehav@gmail.com designates 209.85.215.174 as permitted sender) Received: from [209.85.215.174] (HELO mail-ey0-f174.google.com) (209.85.215.174) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Jun 2012 09:17:29 +0000 Received: by eaak11 with SMTP id k11so876304eaa.33 for ; Sat, 23 Jun 2012 02:17:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=bhkJEuLIXf8Y6lwk8ApMPIouRBS5eiH+CP8ponl9pNI=; b=HgYVgZXsj4DhzbcCHUOKwmxEs7fKzzqzmmBQYIjPp63SfDVlRhwWCghqqPqLHg7qKN G7EKY6ObTPl14aQywt0q60OtrMHRwNZJ0wJQXLkzOOjBUCPnPJWhqOSib4KbHav0LyDJ FxtjLWbWwPg928LXrpyzE5wVptoQ7Q7nMMFVu0/YHq9ysjYjOw/Stu+/LM0cZQYv89FE rJfVIwRI9SShL0Vy0jnIHbCrdVhybR0EDGyGzyYBy30/FXWxug9ULdCSE1U9MBLHN0Jt qpr1Zbnhz7fXH4zc7frurYefQS2GOjxqXu+17cMM6kTC9+fAorfTeypD6IABrJCdGsjA TtZg== MIME-Version: 1.0 Received: by 10.14.37.134 with SMTP id y6mr973436eea.78.1340443029668; Sat, 23 Jun 2012 02:17:09 -0700 (PDT) Sender: bengt.rodehav@gmail.com Received: by 10.14.209.134 with HTTP; Sat, 23 Jun 2012 02:17:09 -0700 (PDT) In-Reply-To: <4FE499E6.3030405@spudsoft.co.uk> References: <4FE499E6.3030405@spudsoft.co.uk> Date: Sat, 23 Jun 2012 11:17:09 +0200 X-Google-Sender-Auth: gcWUUIdeAyAPcVIGwSk72DXRqys Message-ID: Subject: Re: OpenJPA Audit From: Bengt Rodehav To: users@openjpa.apache.org Content-Type: multipart/alternative; boundary=90e6ba6150a8a002d604c320361b --90e6ba6150a8a002d604c320361b Content-Type: text/plain; charset=ISO-8859-1 Hello there Jim, I was part of initiating that support for OpenJPA (Pinaki implemented it) but I haven't used it myself yet. The reason is that I couldn't get the class loading to work when running within OSGi. There is still an outstanding issue regarding this: https://issues.apache.org/jira/browse/OPENJPA-2052 What is your runtime platform? Also, does anyone know whether any progress is made regarding class loading within OSGI? Many people prefer OpenJPA over Eclipse and Hibernate because it works better in OSGi than those projects. However, the OSGi support in OpenJPA is unfortunately very fragile and really needs to be improved. For me, the lack of OSGi support is very frustrating. OSGi is a requirement for me and I really would like to use the new auditing functionality. /Bengt /Bengt 2012/6/22 Jim Talbut > Just want to say thanks. > > Some time ago I was involved in a discussion here about doing audit using > lifecycle listeners. > There are a whole bunch of problems with this approach and, although my > implementation worked, it was not specified that it would work. > > Yesterday I needed to add an audit facility to a system and noticed the > new @Auditable annotation (http://openjpa.apache.org/** > builds/2.2.0/apache-openjpa/**docs/ref_guide_audit.html > ). > Wow. > I spent some time worrying about how to write the data to the database - > assuming I'd have to use JDBC and worrying about how to inject the data > source. > Then I noticed that the Broker passed lets me persist a new Entity during > the audit. > > Thank you guys. > > Jim > --90e6ba6150a8a002d604c320361b--