So,I've been playing around witht his a little bit more, but I still can't
get it to work...
On the OpenEJB site it states the following:
The service-jar.xml should be placed not in the META-INF but somewhere in
your package hierarchy (ours is in /org/apache/openejb/service-jar.xml)
which allo
Dain,
I am using OpenJPA. Do you know if, and how, they support per user
connections?
Paul Spencer
Dain Sundstrom wrote:
Assuming you are using straight JDBC or a persistence framework designed
for per-user connections, I believe that the
org.apache.commons.dbcp.datasources.PerUserPoolData
I'm trying to use a different Resource Adapter than the
ActiveMqResourceAdapter.
I cannot get it to work.
The openejb.log reports the following:
"Cannot find the ServiceProvider id in the service-jar.xml. Check that
your configuration file is point(ed) at the right service provider id."
So, my
Assuming you are using straight JDBC or a persistence framework
designed for per-user connections, I believe that the
org.apache.commons.dbcp.datasources.PerUserPoolDataSource pool can do
what you want, but I've never used per-user pools myself. Also, I bet
that c3p0 (http://sourceforge.ne
I have an application that requires a logged in user be restricted to a
schema within the database. For the sake of illustration, the
application is an address book and their is one schema per user. The
database structure of the table and views within each schema are exactly
same.
My questi
Hi Oliver,
In OpenEJB 3.0, each module (ejb-jar) that we discovered in the
classpath was treated as if it had been deployed individually as a
standalone app. This put the restriction in there that any
persistence units you referenced had to be in the same app (ejb-jar
module) and were no
Wilingson wrote:
>
> Your are right, thanks. In my code the class Server is an interface to a
> bean and its in a different bundle. If you move that class to the bundle
> where this piece of code is, it works fine. Its working now this way but
> some interfaces are provided by other bundles and
Hi,
I used OpenEJB 3.0 as embedded EJB3 container for unit tests in a Maven
project. Now I try to upgrade to OpenEJB 3.1 but I encounter problems I had
not seen before. Actually for some development organization reasons, my EJB3
entities are in many Maven projects, each one having its persistence
