From user-return-14138-apmail-geronimo-user-archive=geronimo.apache.org@geronimo.apache.org Tue Oct 27 23:12:46 2009 Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 39573 invoked from network); 27 Oct 2009 23:07:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 27 Oct 2009 23:07:23 -0000 Received: (qmail 19265 invoked by uid 500); 27 Oct 2009 22:05:22 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 19238 invoked by uid 500); 27 Oct 2009 22:05:22 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 19230 invoked by uid 99); 27 Oct 2009 22:05:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Oct 2009 22:05:22 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=SPF_PASS,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [98.136.44.63] (HELO smtp108.prem.mail.sp1.yahoo.com) (98.136.44.63) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 27 Oct 2009 22:05:14 +0000 Received: (qmail 80111 invoked from network); 27 Oct 2009 22:04:52 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Message-Id:From:To:In-Reply-To:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:X-Mailer; b=U2qLA0hYJB4B/cFcdn9mbEs6qfBG23+TDwXsxXBMp2cB/1m0QedMtNwb1Tooian7nSuMGZRocjyCMamiP91+1Jbe725jNxzI86DRyqAFfOIl/V1gD1gbVzDVTHAGAmdrrba1DeIK/f/1fcMF04bZPdTcxLsw/hYLXiuTtthDOKI= ; Received: from 076-076-148-215.pdx.net (david_jencks@76.76.148.215 with plain) by smtp108.prem.mail.sp1.yahoo.com with SMTP; 27 Oct 2009 15:04:52 -0700 PDT X-Yahoo-SMTP: .9oIUzyswBANsYgUm_5uPui0skTnzGJXJQ-- X-YMail-OSG: k4BwYZYVM1loQ7iHpGeWfAlLSDBhZhQ7uKdo30hmRu9bxP_et1JD.xPL1oXmd1RmKJWHjZONAJh4Q94NRKAvIBoPVanvRPXpGZimGHWCGIzGt59po8IpTcKdxQvQuZBcZjr7A_GCnDsG3p4TKCHgXHXktL3cdrNiEhpST2JlvXzM5ch9cfh3x155d5X3CJt5W4eixxzyHh8cnvdGq00qYz0RMcS3dqLLVhFj2dERJcVw3cL1Am8VH0VVcTZZocKH X-Yahoo-Newman-Property: ymail-3 Message-Id: From: David Jencks To: user@geronimo.apache.org In-Reply-To: <1f3854d50910271214n3168d421s5c6d7e2baacf0e76@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: JavaEE/EJB Spec and Deploying Date: Tue, 27 Oct 2009 15:04:50 -0700 References: <1f3854d50910271214n3168d421s5c6d7e2baacf0e76@mail.gmail.com> X-Mailer: Apple Mail (2.936) X-Virus-Checked: Checked by ClamAV on apache.org On Oct 27, 2009, at 12:14 PM, Quintin Beukes wrote: > Hey, > > Two questions on deploying. > > 1. What does the spec specify regarding deployment? almost nothing useful, and IIUC the ee6 spec is backtracking and removing the standardized deployment support. Basically there's not spec concept of dependencies, and you get basic ops like install, start, undeploy, redeploy (can't remember all the names). It's jsr88 if you want to investigate further. It also has slightly bizarre support for plan editors that AFAIK few vendors have implemented and no one uses (although our console's connector plan editor uses this stuff). > > 2. The table generation of JPA providers. Does the spec specify > anything regarding this? nothing. > > I'm basically asking because if my table generation is set to > drop-create then my tables are dropped/created whenever I restart the > app or the server. Not only when I deploy/undeploy. I understand this > will be even more so with the OSGi Geronimo, because from what I can > gather from the mails the full deployment process will be executed > whenever a bundle is started. I hope not :-) and don't see that as a likely outcome. Currently the osgi effort is working very similarly to the current 2.2 server in that deployment generates a bundle with all the processed g metadata such as the config.ser inside. Even with something like a rfc 66 web container there's a good chance the first time you start the bundle we'd construct such a config.ser and store it. With openjpa there are several different settings, one is drop/create whenever possible, one is update the schema to match the entities, one is to do no DDL. Not sure about other jpa providers. thanks david jencks > > Q