Hello
This problem has been discussed earlier (Edson Richter/m:n mappings), but it
seems to be still there and I didn't find anything about it in Jira. Maybe I'm
missing something, but the problem is that OJB generates a query that doesn't
work in all DB platforms for collections applying an i
Bob Damato wrote:
I don't think so. There's only one copy of the jar on the system. The app is a
portal app, and I've tried the following scenarios:
1. db-ojb.jar in /PORTAL-INF/lib
OJB.properties and repository.xml in /PORTAL-INF/classes
2. db-ojb.jar in /PORTAL-INF/lib
OJB.properties a
I don't think so. There's only one copy of the jar on the system. The app is a
portal app, and I've tried the following scenarios:
1. db-ojb.jar in /PORTAL-INF/lib
OJB.properties and repository.xml in /PORTAL-INF/classes
2. db-ojb.jar in /PORTAL-INF/lib
OJB.properties and repository.xml in
Hi Bob,
Bob Damato wrote:
We're using OJB 1.0.1 successfully in many different scenarios (different
jvm's, ide's and app servers). We are experimenting with integrating it with
SAP's Application Server for a portal and I'm getting the error below. I'm
using the same configuration files that I
We're using OJB 1.0.1 successfully in many different scenarios (different
jvm's, ide's and app servers). We are experimenting with integrating it with
SAP's Application Server for a portal and I'm getting the error below. I'm
using the same configuration files that I'm successfully using elsewhe
