Mailing-List: contact deltaspike-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: deltaspike-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.de;
  h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=nKisLi7ry7mtOHktdkzx5VunhAdIXHGKuayUp+gkFqFTTeCu4XGnGdVRmTDhCAY+XZ5WRprWJ27LGR1yx1NjFB2ZJibn4Gud+6wEVDbLhUgbpCGIYWVFmYlGFjx/p5OL2w/gFTQWJM0bptjipsccv+nFjci80XdxD5gzigk0nqE=;
References: <1336161394.18186.YahooMailNeo@web171506.mail.ir2.yahoo.com>
 <CAGJtJfHN4-qxaP9aa=ZfpK8QOh+gqBAM2O4CmLBbRGuG60T3yg@mail.gmail.com>
 <CACLE=7Pz8tPn4qyrkUqrK64rSEJOYL_XU1xhpU5v5zUr=0tueA@mail.gmail.com>
 <CACLE=7PpKNBY3h2EqNCgjg6N1kd1SOVe9iMG6JSu6Cftk+LHhQ@mail.gmail.com>
 <CANH=8OivDUBhy7pNOuMYeNJZyHfh+gHKi5AfG3k=LWZyzu53aA@mail.gmail.com>
 <CACLE=7OGpq4dU3Pbb923CyNhR1NZz9KgfE8KGCmMibT6TK2kxw@mail.gmail.com>
 <1336256074.7979.YahooMailNeo@web171501.mail.ir2.yahoo.com>
 <0CDEF12E-81F5-4AC1-881F-D46EFE359FF3@gmail.com>
 <CACLE=7NbJcSXQo5BLPgcrcEt4GD3=rmZop7vh-3_gBzDuQuJ5w@mail.gmail.com>
 <20120506091455.63736164642@mx01.openknowledge.de>
 <1336297074.71396.YahooMailNeo@web171506.mail.ir2.yahoo.com>
 <30B9F2A0-8D05-4052-86AA-3922E993B6B4@gmail.com>
 <1336304910.18504.YahooMailNeo@web171504.mail.ir2.yahoo.com>
 <3870ED98-65FF-4826-B3A6-03EF6C7035E4@gmail.com>
 <C6048113-12AE-4652-8562-AA8BB61E03A9@gmail.com>
Message-ID: <1336342298.88555.YahooMailNeo@web171506.mail.ir2.yahoo.com>
Date: Sun, 6 May 2012 23:11:38 +0100 (BST)
From: Mark Struberg <struberg@yahoo.de>
Reply-To: Mark Struberg <struberg@yahoo.de>
Subject: Re: [DISCUSS] deltaspike-jpa module features
To: "deltaspike-dev@incubator.apache.org"
 <deltaspike-dev@incubator.apache.org>
In-Reply-To: <C6048113-12AE-4652-8562-AA8BB61E03A9@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi David!=0A=0AThanks for this valuable input!=0A=0AI guess I need to think=
 about that and put it up in a sample app to test it's usability.=0A=0AI al=
ways need some piece of code to verify if it is _really_ working. =0A=0A=0A=
Btw, are we still d'accord that we like to support EE5, EE6 and EE7 servers=
 with our stuff?=0AMaybe we could provide a 'legacy path' for EE5 and anoth=
er one for EE6 and 7 servers?=0AWe should also make sure that this way does=
 work _without_ any EE server as well - means with pure JPA. Because that i=
s was is used in most unit tests.=0A=0A=0ALieGrue,=0Astrub=0A=0A=0A=0A-----=
 Original Message -----=0A> From: David Blevins <david.blevins@gmail.com>=
=0A> To: deltaspike-dev@incubator.apache.org; Mark Struberg <struberg@yahoo=
.de>=0A> Cc: =0A> Sent: Sunday, May 6, 2012 10:47 PM=0A> Subject: Re: [DISC=
USS] deltaspike-jpa module features=0A> =0A> =0A> On May 6, 2012, at 1:32 P=
M, David Blevins wrote:=0A> =0A>>  I recall your app and I'd guess the hear=
t of your distaste is that you =0A> essentially configure two datasources a=
nd then pick one at runtime.=0A>> =0A>>  In static code, this is possible (=
there is equivalent xml):=0A>> =0A>> =A0 =A0 @DataSourceDefinition(name =3D=
 "java:app/test/ds" ....)=0A>> =A0 =A0 @DataSourceDefinition(name =3D "java=
:app/prod/ds" ....)=0A>> =A0 =A0 @Resource(name =3D "java:app/ds", =0A> loo=
kup=3D"java:app/prod/ds")=0A>> =A0 =A0 public class SomeCdiBean {=0A>> =A0 =
=A0 }=0A>> =0A>>  Two datasources are declared and one symlink that the app=
lication can use =0A> safely.=A0 Clearly the above "symlink" is still hardc=
oded, so to get =0A> some more dynamic behavior you could potentially put t=
he "@Resource" =0A> link on a separate class in a separate jar.=A0 Perhaps =
a "prod.jar" to =0A> hold all the mappings for production and a "test.jar" =
to hold all the =0A> mappings for test, then make sure only one of them is =
in the application at any =0A> given time.=0A>> =0A>>  Still limited of cou=
rse as changing the archive is required and often that =0A> isn't allowed b=
etween test and production.=0A> =0A> For the sake of completeness, I should=
 also say that swapping the descriptors =0A> out without modifying the arch=
ive is the reason for the alternate deployment =0A> descriptor functionalit=
y (alt-dd) all full profile certified servers support.=A0 =0A> So even that=
 concept has been addressed at the spec level.=0A> =0A> One of the things n=
ot supported by plain Tomcat or Jetty, so also not commonly =0A> known or u=
sed.=0A> =0A> =0A> -David=0A>