Hi,
I got a external resource (string to define a path); All work fine for my
project (@resource injection) and the resource is declared into the
ejb-jar.xml :
resource-ref
res-ref-namethepath/res-ref-name
res-typejava.lang.String/res-type
/resource-ref
Resource value is set
Hi
META-INF/ejb-jar.xml of the module should work in embedded mode or
META-INF/env-entries.properties would too.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/10/29
Leo is currently preparing for the 2.2.0-beta release. We are currently VOTING
on it.
Please feel free to try it!
All you need to do is to replace the myfaces* jars in TomEE with the newest
version. We did not change any SPI in MyFaces afaik.
LieGrue,
strub
Hi Romain,
I've try many ways to set the value of the resource, but always got the
error :
org.apache.openejb.OpenEjbContainer$InitializationException:
java.lang.NullPointerException: name cannot be null
at
Hi
did you try with our snapshot (4.6.0-SNAPSHOT)?
can you reproduce it in a shareable sample?
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/10/30 amber
Thanks for your answer, I'll check your code later.
The client application is a JSE application calling Remote EJB over HTTPS.
--
View this message in context:
http://openejb.979440.n4.nabble.com/Remote-EJB-Client-With-Multiple-Certificates-tp4665780p4665806.html
Sent from the OpenEJB User
interesting response. well, tomcat 8 + myfaces 2.2 + some other components
= tomee (javaee 7), right? tomcat 8 and myfaces 2.2 have already released.
does tomee 1.7 (snapshot) = (possible) javaee 7 version/release?
On Wed, Oct 30, 2013 at 1:46 AM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:
this has been discussed on a lot of threads, we target 1.6 ATM then
see to do a +1 version (2, 5 maybe 7, still under discussion) but
this one will be obviously based on tomcat 8 + the whole apache EE 7
stack
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
well, i did try myfaces 2.2 snapshot about a week ago and worked with
Leonardo on MyFaces list, approx. 1(+) week(s) ago, on MyFaces 2.2 CDI
@ViewScoped @PreDestroy issue.
I am almost willing/motivated to try and push to production. :)
On Wed, Oct 30, 2013 at 4:01 AM, Mark Struberg
understood, thanks. :)
On Wed, Oct 30, 2013 at 7:34 AM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:
this has been discussed on a lot of threads, we target 1.6 ATM then
see to do a +1 version (2, 5 maybe 7, still under discussion) but
this one will be obviously based on tomcat 8 + the
Greetings, I'm using Apache TomEE 1.6.0-SNAPSHOT from a couple of
weeks ago. I am frequently seeing my @Lock(LockType.WRITE) @Singleton
@Startup MySchedule { @Schedule(/**/) public void run() { /* slowish
*/ } } have the following error:
WARNING [EjbTimerPool - 901]
i am doing the same (see the URLs below).
/**
*
* http://tomee.apache.org/examples-trunk/access-timeout/README.html
* http://tomee.apache.org/examples-trunk/access-timeout-meta/
* http://docs.oracle.com/cd/E19798-01/821-1841/gipsz/index.html
*/
@Singleton
@Lock(LockType.WRITE)
Here the sample cdi-basic modified like I do for my project :
- adding cdi-basic\src\main\resources\META-INF\ejb-jar.xml with resource-ref
declaration
- adding cdi-basic\src\test\resources\META-INF\ejb-jar.xml with env-entry
declaration
same error
thx to point me on my mistake :)
yes it is needed by almost all implementations backed by a RDBMS
you can workaround it if your business allows the usage of a
stateful + extended persistence context.
to lazy load a relationship you need an entity parent but if you
aren't in a transaction you are detached and then don't know if
oups, message sent too quickly ...
SUPPORTS is usually fine as a default for finder methods.
As soon as there is no transaction, an entity is detached when returned by
the entity manager.
Even with SUPPORTS btw
When REQUIRED (or any transaction) is used, the entity remains attached and
managed
From http://docs.oracle.com/javaee/6/tutorial/doc/bncij.html
Supports Attribute
If the client is running within a transaction and invokes the enterprise
bean’s method, the method executes within the client’s transaction. If the
client is not associated with a transaction, the container does not
Hi
is your entity manager created manually or managed?
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/10/30 José Luis Cetina maxtorz...@gmail.com:
From
Is injected @PersistenceContex
@Stateless
@TransactionAttribute(TransactionAttributeType.REQUIRED)
@TransactionManagement(TransactionManagementType.CONTAINER)
public class MenusFacade implements MenusFacadeLocal {
@PersistenceContext(unitName =
shouldn't work with BEAN exepted if called from a bean which started a tx
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/10/30 José Luis Cetina maxtorz...@gmail.com:
Is
Ok
2013/10/30 Romain Manni-Bucau rmannibu...@gmail.com
shouldn't work with BEAN exepted if called from a bean which started a tx
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github:
In resume, then i need always a transaction in my own method or in the
client that invokes any method that need to fetch any other entity.
2013/10/30 José Luis Cetina maxtorz...@gmail.com
Ok
2013/10/30 Romain Manni-Bucau rmannibu...@gmail.com
shouldn't work with BEAN exepted if called
Hi!
I have just tested replication in tomee-1.6.0-20131030.065404-219. OWB Bug
seems to be fixed, but there is new one.
The First replication works perfect, but after session migration to another
node I've got following exeception:
java.io.NotSerializableException: null is not serializable
Hi
Normally no, can be related to the resource adapter BTW
Le 30 oct. 2013 20:29, um umano...@mib.com a écrit :
I am using MDBs deployed on tomEE that reads from websphere MQ. I have
configured and installed the websphere MQ resource adapters. From my tests,
I am finding that MDBs are
Hi
In a war no idea, maybe active tomcat FINE logs
Le 30 oct. 2013 19:14, dmitry.vol...@eiskonzept.com a écrit :
Hi!
I have just tested replication in tomee-1.6.0-20131030.065404-219. OWB Bug
seems to be fixed, but there is new one.
The First replication works perfect, but after session
I found the right way to do :
- p.setProperty(openejb.altdd.prefix, test-)
- rename the ejb-jar.xml (the one with env-entry located in /src/test/...)
to test-ejb-jar.xml and move it to \src\main\resources\META-INF\
Why openEJB can't find the file from src/test/.. ?
(I remember doing the same
Hi romain,
just build with snapshot : same error.
Something I don't understand :
I have a ejb-jar.xml into \src\main\resources\META-INF with the resource-ref
declaration :
resource-ref
res-ref-namethepath/res-ref-name
res-typejava.lang.String/res-type
/resource-ref
For tests
Thanks for that information, Howard.
Even with @AccessTimeout(-1) which should cause it to wait forever, I
still take the aforementioned Exception. It seems that some of my
transactions can take upwards of an hour to complete and that Apache
TomEE deems this unacceptable.
On Wed, Oct 30, 2013 at
Hi
1h? You customized the timeout of the transaction manager?
That said you have a biggest issue if you processing is longer than your
scheduling. In particular in write mode. We have a retry config but maybe
check you do what you want cause all technical solutions about this timeout
will be
String are not resources. You can set it without config this way:
public class StringResource {
public String create() {return foo;}
}
Then in container properties set:
resourceid=new://Resource?type=java.lang.Stringclass-name=StringResourcefactory-name=create
About test ejbjar it is seen but
to give some details it happens when an interceptor is not
serializable (see last method of
https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-impl/src/main/java/org/apache/webbeans/intercept/DefaultInterceptorHandler.java)
it should be easy to debug this method to see just the level
30 matches
Mail list logo
