Romain Manni-Bucau wrote:
right
the question here is do we want to use it or not internally (cdi-query was
based on it no? and i think it avoid to repeat too much code, we could
handle the annotation indirection you speak about to be clearer in APIs)
if we dont' want to use it, it can wait
Mark Struberg
11 September 2012
1:59 AM
One of the credos is that you MUST NOT repackage for just
moving to a new server.Either this is in JNDI (same location) or
just use @Inject ProjectStage ps; to check on which server you are
running. I see no benefit of
On 24/08/2012, at 7:47 PM, Mark Struberg strub...@yahoo.de wrote:
Well, we might miss some explanation for this lines
@PersistenceContext(unitName=default)
private EntityManager entityManager;
This only works in SE. In an EE container you will get a Container Managed
EM, which is not
On 15/08/2012, at 11:20 PM, Pete Muir pm...@redhat.com wrote:
All, the CDI EG requires feedback on an item in the spec which is not clear,
and has been implemented differently between implementations, and is not TCK
tested. As Deltaspike contains lots of extensions authors, requesting
On 16/08/2012, at 12:41 AM, Pete Muir pm...@redhat.com wrote:
On 15 Aug 2012, at 15:30, Stuart Douglas wrote:
On 15/08/2012, at 11:20 PM, Pete Muir pm...@redhat.com wrote:
All, the CDI EG requires feedback on an item in the spec which is not
clear, and has been implemented
Just something to be aware of is that invoking this EJB actually does a fair
bit more than just start a transaction.
- Available java:comp and java:module entries may change, as it will be using
the EjbTransactionHelper JNDI namespace
- This EjbTransactionHelper may have interceptors applied
AFAIK java.lang.reflect.Proxy actually has its own internal cache of proxy
classes, so removing the cache should not result in the generation of any more
proxy class objects.
Also from the WeakHashMap javadoc:
The value objects in a
* ttWeakHashMap/tt are held by ordinary strong references.
+1
Looks good to me.
Stuart
