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 CE41C965C for ; Fri, 23 Dec 2011 00:02:32 +0000 (UTC) Received: (qmail 24144 invoked by uid 500); 23 Dec 2011 00:02:32 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 24111 invoked by uid 500); 23 Dec 2011 00:02:32 -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 24103 invoked by uid 99); 23 Dec 2011 00:02:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Dec 2011 00:02:32 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kwsutter@gmail.com designates 74.125.83.46 as permitted sender) Received: from [74.125.83.46] (HELO mail-ee0-f46.google.com) (74.125.83.46) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Dec 2011 00:02:24 +0000 Received: by eekc4 with SMTP id c4so9561272eek.33 for ; Thu, 22 Dec 2011 16:02:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=vNjSVY6t/TyByJonniVS0VCuwsLz5USZzluQ6+3O4Uw=; b=QZZSFHj3tFaro+q28NMaX7UfuWNv0zXiNzPe5IAv3/WF+ZWGX1h5rIGtydAvJp1nld 4/TRxbvg0treV72mCf+5l+tQJgaekHSrUqUrPs2Suz3U3g+ZJ40zMj9p2Xoo6Fx3nSKl ZrTyMB0Mqdx4Du4iWNw82UQBqguV2vsNkoyUU= Received: by 10.213.4.202 with SMTP id 10mr87301ebs.100.1324598524317; Thu, 22 Dec 2011 16:02:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.14.99.69 with HTTP; Thu, 22 Dec 2011 16:01:43 -0800 (PST) In-Reply-To: <1324595396.45747.YahooMailNeo@web30508.mail.mud.yahoo.com> References: <1324591905.18997.YahooMailNeo@web30501.mail.mud.yahoo.com> <1324595396.45747.YahooMailNeo@web30508.mail.mud.yahoo.com> From: Kevin Sutter Date: Thu, 22 Dec 2011 18:01:43 -0600 Message-ID: Subject: Re: Will OpenJPA 2.1.x ever be incorporated into a WAS7 feature pack? To: users@openjpa.apache.org, Ron Grabowski Content-Type: multipart/alternative; boundary=0015174bf1b68310b304b4b7207b X-Virus-Checked: Checked by ClamAV on apache.org --0015174bf1b68310b304b4b7207b Content-Type: text/plain; charset=ISO-8859-1 Hi Ron, The WebSphere JPA documentation relies on the Apache OpenJPA documentation (and the JPA specification itself) for much of the documentation. We didn't want to repeat (and maintain) all of the information that was already available. But, what is documented in the WebSphere InfoCenter are the extensions and features that WebSphere provides beyond the basic Apache OpenJPA deliverable. These WebSphere features are built on top of the Apache OpenJPA binaries. So, anything that is written against Apache OpenJPA will function as is when running within WebSphere. The added benefit is that you can also take advantage of the WebSphere extensions such as DB2 features, pureQuery, NLS translated messages, extended debugging capabilities, etc. Here's a link to the InfoCenter for the OSGi/JPA 2.0 Feature Pack: http://publib.boulder.ibm.com/infocenter/wasinfo/fep/topic/com.ibm.websphere.jpafep.multiplatform.doc/info/ae/ae/tjpa2_ep.html To get to your first question... Each Apache OpenJPA service stream (branch) has an owner or manager. This manager determines which fixes are allowed into a given stream. New development (whiz-bang features) are normally developed in trunk, not one of the service streams. But, there have been occasions where a new feature is requested in a service stream. Each request is processed separately -- that is, there is no cut-and-dried rules as to when or if a feature is allowed into a service stream. Welcome to WebSphere's JPA solution based on Apache OpenJPA! I hope your experience is a positive one. :-) Kevin On Thu, Dec 22, 2011 at 5:09 PM, Ron Grabowski wrote: > Sounds reasonable. Historically have issues been the only thing that have > prompted new snapshots of OpenJPA 2.0.x to be included in WAS7 fixpacks? If > the OpenJPA community writes a new whiz-bang feature in the 2.0.x stream > could it qualify for inclusion in a fixpack or has WAS7+OpenJPA 2.0.x > entered a "no updates unless its broke" phase? > > Does anyone know if IBM maintains its own WebSphere JPA documentation? The > "Getting Started with the Feature Pack for OSGi Applications and JPA 2.0" > RedBook [1] states: > > > " > JPA for WebSphere Application Server comes with two JPA 2.0 persistence > providers: > - Apache OpenJPA persistence provider > - JPA for WebSphere Application Server persistence provider > " > > Is there documentation on-line for "JPA for WebSphere Application Server > persistence provider" or is it the exact same as the documentation found on > the OpenJPA site [2]? > > Sorry mailing-list for the IBM specific questions...feel free to passive > aggressively point to me archived threads if this has already been > discussed. My team recently moved from another vendor's JPA implementation > to OpenJPA for its WAS compatibility and we're trying to learn the lay of > the land. > > Thanks, > Ron > > [1] - http://www.redbooks.ibm.com/redbooks/pdfs/sg247911.pdf > > [2] - http://openjpa.apache.org/documentation.html > > > ________________________________ > From: Kevin Sutter > To: users@openjpa.apache.org; Ron Grabowski > Sent: Thursday, December 22, 2011 5:26 PM > Subject: Re: Will OpenJPA 2.1.x ever be incorporated into a WAS7 feature > pack? > > > Hi Ron, > WebSphere continues to support their JPA solutions via improvements to the > corresponding OpenJPA offerings. The OSGi/JPA 2.0 Feature Pack is based on > the OpenJPA 2.0.x service stream. WebSphere's v8 solution is based on the > OpenJPA 2.1.x service stream. > > If issues are discovered in any of these environments, then an appropriate > fix is developed for the Apache OpenJPA service stream and that is > ultimately pulled into an iFix or fixpack for the WebSphere product. An > issue that is discovered in WAS v8, for example, can normally be > back-ported to previous releases, such as the OSGi/JPA 2.0 Feature Pack (as > it applies). > > New features for one release (ie. WebSphere v8) are not normally > candidates for back-porting to previous releases (ie. OSGi/JPA 2.0 Feature > Pack). > > Hope this helps, > Kevin > > > On Thu, Dec 22, 2011 at 4:11 PM, Ron Grabowski > wrote: > > I couldn't find anything on the OpenJPA or IBM WAS website(s) about > how/if/when IBM decides to package OpenJPA improvements into future feature > packs. Does anyone know if a future WAS7 feature pack will include OpenJPA > 2.1.x? Along those same lines, is WAS8's JPA implementation based on > OpenJPA 2.1.x? > --0015174bf1b68310b304b4b7207b--