hi @ all,
i've committed [1] a refactored version of @Transactional as well as
@TransactionScoped (for @Transactional).
i'll add some details to the documentation soon (we can't copy it, because
the new behaviour is a bit different (easier)).
furthermore, i've committed several tests (which
Following up on all emails sent so far on this thread:
* I like Mark's priorities - @Transactional is definitely the item most
requested
* I like the design of plugging in different persistence strategies
* Agreed that the standardised stuff for configuring datasources is a mess, we
don't
+1 for deferring the CRUD work until a later release. Let's get the
basics right and out in the wild first.
On Tue, May 8, 2012 at 5:58 AM, Pete Muir pm...@redhat.com wrote:
Following up on all emails sent so far on this thread:
* I like Mark's priorities - @Transactional is definitely the
...@yahoo.de]
Gesendet: Montag, 7. Mai 2012 00:04
An: deltaspike-dev@incubator.apache.org
Betreff: Re: AW: AW: AW: AW: AW: AW: AW: [DISCUSS] deltaspike-jpa module
features
Thought about such a thing as well. The problem here is: how do you tell the
persistence.xml about our Qualifiers?
In fact the whole JPA
:
Sent: Saturday, May 5, 2012 11:29 PM
Subject: Re: [DISCUSS] deltaspike-jpa module features
With my note on datasourcedefinition i wanted to avoid to add sthg new.
I'd
prefer to fix existing API/specs.
Adding sthg new simply creates another mess...no?
- Romain
Le 5 mai 2012 22:39
: [DISCUSS] deltaspike-jpa module features
@Mark: today using your own datasource implementation with
@datasourcedefinition you answer your need. The drawback compared to producers
is you need to test the env where producers will have stereotypes but it does
the job even for complicated envrt.
- Romain
...@openknowledge.de
To: deltaspike-dev@incubator.apache.org
deltaspike-dev@incubator.apache.org
Cc:
Sent: Sunday, May 6, 2012 11:17 AM
Subject: AW: [DISCUSS] deltaspike-jpa module features
Hi,
I think we have different dimensions here:
1. Who manages the transaction: JTA vs. RESOURCE_LOCAL
]
Gesendet: Sonntag, 6. Mai 2012 08:09
An: deltaspike-dev@incubator.apache.org
Betreff: Re: [DISCUSS] deltaspike-jpa module features
@Mark: today using your own datasource implementation with
@datasourcedefinition
you answer your need. The drawback compared to producers is you need
On May 6, 2012, at 2:37 AM, Mark Struberg wrote:
In plain Tomcat or
Jetty servers this needs to be configured in a container-specific way.
The problem with the container specific stuff is that every container serves
the xml configured datasource on a different location in JNDI! So you
Struberg strub...@yahoo.de
Cc:
Sent: Sunday, May 6, 2012 1:25 PM
Subject: Re: [DISCUSS] deltaspike-jpa module features
On May 6, 2012, at 2:37 AM, Mark Struberg wrote:
In plain Tomcat or
Jetty servers this needs to be configured in a container-specific way.
The problem
Message -
From: David Blevins david.blev...@gmail.com
To: deltaspike-dev@incubator.apache.org; Mark Struberg
strub...@yahoo.de
Cc:
Sent: Sunday, May 6, 2012 1:25 PM
Subject: Re: [DISCUSS] deltaspike-jpa module features
On May 6, 2012, at 2:37 AM, Mark Struberg wrote:
In plain
yes, that crashes the container...
From: Romain Manni-Bucau rmannibu...@gmail.com
To: Mark Struberg strub...@yahoo.de; deltaspike-dev@incubator.apache.org
Sent: Sunday, May 6, 2012 1:52 PM
Subject: Re: [DISCUSS] deltaspike-jpa module features
Mark, did
...
From: Romain Manni-Bucau rmannibu...@gmail.com
To: Mark Struberg strub...@yahoo.de; deltaspike-dev@incubator.apache.org
Sent: Sunday, May 6, 2012 1:52 PM
Subject: Re: [DISCUSS] deltaspike-jpa module features
Mark, did you try providing a name starting with java:?
- Romain
Le 6 mai
Subject: Re: [DISCUSS] deltaspike-jpa module features
No, the container is NOT buggy, because it's simply NOT defined!
That's the whole mess about JNDI...
LieGrue,
strub
From: Romain Manni-Bucau rmannibu...@gmail.com
To: Mark Struberg strub...@yahoo.de
Sent
From: Mark Struberg strub...@yahoo.de
To: Romain Manni-Bucau rmannibu...@gmail.com; deltaspike
deltaspike-dev@incubator.apache.org
Sent: Sunday, May 6, 2012 2:14 PM
Subject: Re: [DISCUSS] deltaspike-jpa module features
No, the container is NOT buggy, because it's simply NOT defined
, May 6, 2012 2:37 PM
Subject: Re: [DISCUSS] deltaspike-jpa module features
I understand. On another side how many differeny locations are there? Isnt it
manageable?
- Romain
Le 6 mai 2012 14:29, Mark Struberg strub...@yahoo.de a écrit :
PS: I _fully_ agree that this mess should best get
...@yahoo.de;
deltaspike-dev@incubator.apache.org
Sent: Sunday, May 6, 2012 2:37 PM
Subject: Re: [DISCUSS] deltaspike-jpa module features
I understand. On another side how many differeny locations are there?
Isnt it manageable?
- Romain
Le 6 mai 2012 14:29, Mark Struberg strub...@yahoo.de
Struberg strub...@yahoo.de;
deltaspike-dev@incubator.apache.org
Sent: Sunday, May 6, 2012 2:37 PM
Subject: Re: [DISCUSS] deltaspike-jpa module features
I understand. On another side how many differeny locations are there?
Isnt it manageable?
- Romain
Le 6 mai 2012 14:29, Mark Struberg strub
-Ursprüngliche Nachricht-
Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
Gesendet: Sonntag, 6. Mai 2012 14:49
An: Mark Struberg; deltaspike-dev@incubator.apache.org
Betreff: Re: [DISCUSS] deltaspike-jpa module features
ConfigurableDataSource doesnt solve it. If you build the emf from
An: deltaspike-dev@incubator.apache.org
Betreff: Re: AW: [DISCUSS] deltaspike-jpa module features
How do you manage it from persistence.xml if you dont repackage your archive as
Mark said?
Personally i agree ;)
- Romain
Le 6 mai 2012 15:06, Arne Limburg arne.limb...@openknowledge.de a écrit :
OK
[mailto:rmannibu...@gmail.com]
Gesendet: Sonntag, 6. Mai 2012 15:14
An: deltaspike-dev@incubator.apache.org
Betreff: Re: AW: [DISCUSS] deltaspike-jpa module features
How do you manage it from persistence.xml if you dont repackage your
archive as Mark said?
Personally i agree ;)
- Romain
Le 6 mai 2012
Manni-Bucau [mailto:rmannibu...@gmail.com]
Gesendet: Sonntag, 6. Mai 2012 15:14
An: deltaspike-dev@incubator.apache.org
Betreff: Re: AW: [DISCUSS] deltaspike-jpa module features
How do you manage it from persistence.xml if you dont repackage your
archive as Mark said?
Personally i agree
: AW: AW: AW: [DISCUSS] deltaspike-jpa module features
Cdi is in jee so jee containers scans cdi beans and same for resources
(@persistencontext).
Le 6 mai 2012 15:36, Arne Limburg arne.limb...@openknowledge.de a
écrit :
If not, we can use other annotations, but I think jee containers just
@incubator.apache.org
Betreff: Re: AW: AW: AW: [DISCUSS] deltaspike-jpa module features
Cdi is in jee so jee containers scans cdi beans and same for resources
(@persistencontext).
Le 6 mai 2012 15:36, Arne Limburg arne.limb...@openknowledge.de a
écrit :
If not, we can use other annotations, but I think
...@gmail.com]
Gesendet: Sonntag, 6. Mai 2012 15:49
An: deltaspike-dev@incubator.apache.org
Betreff: Re: AW: AW: AW: AW: [DISCUSS] deltaspike-jpa module features
The container will scan persistencecontext annotation with no link with
cdi.
Le 6 mai 2012 15:46, Arne Limburg arne.limb
An: deltaspike-dev@incubator.apache.org
Betreff: Re: AW: AW: AW: AW: AW: [DISCUSS] deltaspike-jpa module features
It tomee we create the entitymanagerfactory associated.
Le 6 mai 2012 15:53, Arne Limburg arne.limb...@openknowledge.de a écrit :
OK and the meaning of this annotation at class-level would
-
Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
Gesendet: Sonntag, 6. Mai 2012 16:00
An: deltaspike-dev@incubator.apache.org
Betreff: Re: AW: AW: AW: AW: AW: [DISCUSS] deltaspike-jpa module features
It tomee we create the entitymanagerfactory associated.
Le 6 mai 2012 15:53, Arne
: AW: AW: AW: AW: AW: [DISCUSS] deltaspike-jpa module features
Yep but an em needs an emf ;)
Le 6 mai 2012 16:05, Arne Limburg arne.limb...@openknowledge.de a écrit :
OK, I think, this is not correct since it expresses a dependency to an
EntityManager and not to an EntityManagerFactory
:00
An: deltaspike-dev@incubator.apache.org
Betreff: Re: AW: AW: AW: AW: AW: [DISCUSS] deltaspike-jpa module features
It tomee we create the entitymanagerfactory associated.
Le 6 mai 2012 15:53, Arne Limburg arne.limb...@openknowledge.de a
écrit :
OK and the meaning of this annotation
with this properties...
- Arne
-Ursprüngliche Nachricht-
Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
Gesendet: Sonntag, 6. Mai 2012 16:10
An: deltaspike-dev@incubator.apache.org
Betreff: Re: AW: AW: AW: AW: AW: AW: [DISCUSS] deltaspike-jpa module
features
Yep but an em
On May 6, 2012, at 1:32 PM, David Blevins wrote:
I recall your app and I'd guess the heart of your distaste is that you
essentially configure two datasources and then pick one at runtime.
In static code, this is possible (there is equivalent xml):
@DataSourceDefinition(name =
@incubator.apache.org; Mark Struberg strub...@yahoo.de
Cc:
Sent: Sunday, May 6, 2012 3:07 PM
Subject: AW: [DISCUSS] deltaspike-jpa module features
OK,
but do we really need a container-independent way for JNDI-DataSources?
What's the use case for it?
The user always knows his container and thus his
assume.
LieGrue,
strub
- Original Message -
From: Arne Limburg arne.limb...@openknowledge.de
To: deltaspike-dev@incubator.apache.org
deltaspike-dev@incubator.apache.org
Cc:
Sent: Sunday, May 6, 2012 3:48 PM
Subject: AW: AW: AW: AW: [DISCUSS] deltaspike-jpa module features
@incubator.apache.org
deltaspike-dev@incubator.apache.org
Cc:
Sent: Sunday, May 6, 2012 4:19 PM
Subject: AW: AW: AW: AW: AW: AW: AW: [DISCUSS] deltaspike-jpa module features
Never mind ;-)
Maybe it is better to provide qualifiers for all the JPA properties? Like
this:
public class
@incubator.apache.org
deltaspike-dev@incubator.apache.org
Cc:
Sent: Sunday, May 6, 2012 3:48 PM
Subject: AW: AW: AW: AW: [DISCUSS] deltaspike-jpa module features
If so, what would be the semantic of such definition?
Btw. that classes would only become CDI beans when the deployment is in
the
correct
...@openknowledge.de
To: deltaspike-dev@incubator.apache.org
deltaspike-dev@incubator.apache.org; Mark Struberg strub...@yahoo.de
Cc:
Sent: Sunday, May 6, 2012 3:07 PM
Subject: AW: [DISCUSS] deltaspike-jpa module features
OK,
but do we really need a container-independent way for JNDI
@incubator.apache.org
deltaspike-dev@incubator.apache.org; Mark Struberg strub...@yahoo.de
Cc:
Sent: Sunday, May 6, 2012 3:07 PM
Subject: AW: [DISCUSS] deltaspike-jpa module features
OK,
but do we really need a container-independent way for JNDI-DataSources?
What's the use case
To: deltaspike-dev@incubator.apache.org
Cc:
Sent: Monday, May 7, 2012 12:10 AM
Subject: Re: [DISCUSS] deltaspike-jpa module features
t he issue is at spec level, IMO DS shouldnt be a container too much
otherwise it will replace the specs so if you have such an issue update
the
spec to make
!
How would such a scenario work using the @DataSourceConfig?
LieGrue,
strub
- Original Message -
From: Romain Manni-Bucau rmannibu...@gmail.com
To: deltaspike-dev@incubator.apache.org
Cc:
Sent: Saturday, May 5, 2012 12:55 AM
Subject: Re: [DISCUSS] deltaspike-jpa module
Hi,
Big +1 for all suggestions from Mark.
Also +1 for some util classes for common operations like CRUD and
pagination. Maybe inspiration from Seam Application Framework (Home, Query,
Controller) in Seam 2 [1] or from DataValve [2].
Regards,
Paul.
[1]
With my note on datasourcedefinition i wanted to avoid to add sthg new. I'd
prefer to fix existing API/specs.
Adding sthg new simply creates another mess...no?
- Romain
Le 5 mai 2012 22:39, Paul Dijou paul.dijou@gmail.com a écrit :
Hi,
Big +1 for all suggestions from Mark.
Also +1 for
Subject: Re: [DISCUSS] deltaspike-jpa module features
With my note on datasourcedefinition i wanted to avoid to add sthg new. I'd
prefer to fix existing API/specs.
Adding sthg new simply creates another mess...no?
- Romain
Le 5 mai 2012 22:39, Paul Dijou paul.dijou@gmail.com a
écrit
Hi!
It's time to start the discussion about our deltaspike-jpa module I think ;)
a.) where
I suggest that we create a ee-modules project with submodules jsf, jpa, etc
b.) what
*) @Transactional
*) TransactionalInterceptor with SimplePersistenceStrategy,
JtaPersistenceStrategy
*)
hi @ all,
@ a)
+1
@ b)
+1 for the basic concepts, however, @Transactional and @TransactionScoped
need to be refactored (i'm currently working on it).
furthermore, we should discuss a thin query layer which supports e.g.
pagination,... easily (we also need it for a security-jpa module).
Hi,
isn't the ConfigurableDataSource in JEE6? (datasourceconfiguration by
annotation or in the web.xml)?
a really really big +1 for a pagination solution (typically a hades light
is a must have!)
- Romain
2012/5/4 Gerhard Petracek gerhard.petra...@gmail.com
hi @ all,
@ a)
+1
@ b)
+1
45 matches
Mail list logo
