On Oct 21, 2008, at 7:00 PM, suhaas wrote:
At this point in time, I have drilled down the problem to Spring
2.0 and
OpenEJB 3.0 integration.
As mentioned in the original problem statement older application
(without
OpenEJB) is using JSF -> backing bean -> service locator flow to
call
On Oct 22, 2008, at 3:15 AM, Bernhard Humm wrote:
David Blevins wrote:
In OpenEJB 3.0, when using the supplied HSQL datasource in a TestCase
we should be using an in memory database with the JdbcUrl of
"jdbc:hsqldb:mem:hsqldb". In OpenEJB 3.0 that sometimes worked and
sometimes didn't (d
On Oct 22, 2008, at 4:11 AM, Jean-Sébastien Scrève wrote:
Ok thanks for the tip David.
What I try to implement is "conversation" between Tapestry and
OpenEJB. This
"conversation" concept is already implemented into Seam.
Very interesting.
I store the stateful instance into a web session
On Oct 28, 2008, at 2:08 AM, Henri Gomez wrote:
Could it be done for 3.1 release ?
Hi to all,
In the 3.1 release changelog I could see :
EAR-style classpath application discovery groups individual modules as
an EAR allowing sharing of persistence units and improved connector
and custom MDB
> Could it be done for 3.1 release ?
Hi to all,
In the 3.1 release changelog I could see :
EAR-style classpath application discovery groups individual modules as
an EAR allowing sharing of persistence units and improved connector
and custom MDB deployment.
Did it what we discussed in this threa