Júlio Cesar de Melhado e Lima wrote:
I'm using Tomcat 5.0.28, Postgres 7.4 and OJB 1.0.1.
So, I made available a JNDI Resource mydatasource, and this resource
is accessable ( I wrote a tiny jsp page to lookup for this object and
everything looks fine ).
Then a change the file
I just upgraded from OJB 1.0.1 to 1.0.3 and I keep getting an
java.io.InvalidClassException:
org.apache.ojb.broker.util.collections.RemovalAwareCollection; local class
incompatible: stream classdesc serialVersionUID = -7915096023416965226, local
class serialVersionUID = 6853709708973269593
Bobby Lawrence wrote:
I just upgraded from OJB 1.0.1 to 1.0.3 and I keep getting an
java.io.InvalidClassException:
snip/
I have NOT changed my OJB.properties file, could this have something to
do with it?
Without looking to deeply into the stacktrace you sent;
it is always recommended to
Rahul Srivastava wrote:
Hi
i am having a rpoblem with JDO . please help me for this.
snip/
[java] com.sun.jdori.enhancer.util.InternalError: assertion failed:
cannot
find class file for class: org/apache/ojb/tutorial5/Product
snip/
BUILD FAILED
D:\ojb-blank\ojb-blank\build.xml:226: Java
Philippe Guillard wrote:
Thanks Charles,
Unfortunately i get the same result without parameter. ( I use JDO 1.01
form Sun, OJB as integrated in cocoon framework).
You guess right i 've built the DB by hand before and adapted a
repository later. It is not supposed to be used at runtime, but i
Martin Kalén wrote:
The index-descriptor is (as Charles pointed out) only used if you generate
DDL/SQL with OJB using Torque.
If you create your database by hand, you can remove all index-descriptor
attributes to get a cleaner OJB repository.
Clarification: The index-descriptor attribute is
Wang Lei wrote:
At first ,thank you for your reply.
I tried it as you wrote.
The result keeps the same.
Are you still running multithreaded test runner from the initial post?
If so, it's just a fact that you are asking for 500 brokers at approximately
the same time in your test runner (as
Hey
Has anyone successfully gotten Derby to work with OJB, and if so what
platform did you use to specify OJB to use?
I have it set to DB2 right now, but I'm not getting any love from it,
OJB is complaining that the schema does not exist, but in my little
test JSP it indeed does exist
Martin Kalén wrote:
Most important is: exactly which test runner
code are you using at the moment and exactly what are the semantics you
are trying to test
Attached you will find a slight modification of your original code that
will run two loops:
1. 500 store-ops in sequence
2. 500 store-ops
