I think your extent-class declaration cause the problem (Or OJB's
handling of extent clases).
EmployeeRhBr is an interface that extends Employee interface?
EmployeeRhBrImpl is an extent of Employee AND EmployeeRhBr. Why?
Maybe this cause the problem.
Of course this causes the problem : When
Hello,
I'm using OJB R5 and would like to use the support for using stored
procedures.
I'm using the following declaration in my class descriptor
insert-procedure name=vmojb.insInstance include-all-fields=true
/insert-procedure
It looks like the code doesn't take any parameters
Hi,
It works great except when it comes to extents.
In this case,
*EmployeeRhBr extends Employee = How should I reflect this in the
repository mapping? Do I make some mistake somewhere?
Add EmployeeRhBr as extent to Employee class-descriptor.
Additional you can refactoring your extent
Hi Luis,
Luis Cruz wrote:
Hello,
To use the Optimistic Locking feature provided by OJB does the
ACKOPTLOCK column have to be added to every table, or just the ones
defined in the user mapping?
You have to add a version column only for those classes that have an
optimistic locking attribute (=
Hi,
Can someone tell me how to set a reference-descriptor for a foreign key?
Below is an excerpt of my repository-user.xml file. I always get the error
message: ClassPersistenceNotCapableException: java.lang.Integer not found in
repository.xml ... I have no clue what to do. Thx,
Dirk
Since,
all discussions on reloading/refreshing an persistent object somehow
ended up on different topics. Therefore I'm trying to formulate it as
simple as possible:
What are the exact steps to refresh the attributes of a single
persistent object without generating a new instance?
- What
I think your problem is in the name of the reference-descriptor it has the
same name that field 4. Try to change the name and I think it will work
fine.
-Original Message-
From: Dirk Manske (Service Respond)
[mailto:[EMAIL PROTECTED]
Sent: segunda-feira, 29 de Dezembro de 2003 18:43
To:
Thanks for your answer. When I change the reference name to I get a
MetadataException which states that it can't find a member in
de.plato.app.activity.entity.ModuleModel. Of course there is no member
in this class since I declared all attributes already in the
class-descriptor.
Please,
Can anyone send to me some resource.xml source code fragment where is
declared the jdbc-connection-descriptor for a postgresql jdbc?
I am a newbie and my bigest problems is to start to use it on my Web
application. I couldnt find any samples how to use it on Web
Applications. Some codes
I assume you mean repository.xml
If so:
jdbc-connection-descriptor
jcd-alias=test-database
default-connection=true
platform=PostgreSQL
jdbc-level=2.0
driver=org.postgresql.Driver
protocol=jdbc
Sebastian wrote:
Since,
all discussions on reloading/refreshing an persistent object somehow
ended up on different topics. Therefore I'm trying to formulate it as
simple as possible:
What are the exact steps to refresh the attributes of a single
persistent object without generating a new
Look, as you defined
field-descriptor id=4 name=intActivityIdFK column=ACTIVITY_ID
jdbc-type=INTEGER /
you can't have (or you will always get ClassCastException!!!)
reference-descriptor name=intActivityIdFK
class-ref=de.premiere.plato.app.activity.entity.ActivityModel
Sebastian wrote:
The following seems to work, but I have no clue if it's the best way to
reload an object:
public void reload(Object obj)
{
ClassDescriptor cld = pb.getClassDescriptor(obj.getClass());
cld.setAlwaysRefresh(true);
pb.getObjectByQuery(new QueryByIdentity(obj));
}
Any
Hi Dirk,
ModuleModel should have an attribute of type ActivityModel. This is the attribute
name the reference descriptor is looking for. It also appears that your package names
do not correspond
de.premiere.plato.app.activity.entity.ActivityModel != de.activity.entity.ActivityModel
I
Hi Edson,
this information was exactly what I have been looking for. Now it is
working. Thanks a lot.
Dirk
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Gesendet: Montag, 29. Dezember 2003 20:59
An: OJB Users List
Betreff: Re: AW:
Hi,
I am executing the following code:
OQLQuery query = impl.newOQLQuery();
query.create( [THEQUERY] );
DList results = (DList)query.execute();
Iterator iterator = results.iterator();
If I change some column with an external tool and then execute the code,
the updated column is not
Are you working with DefaultCacheImpl or EmptyCacheImpl?
If you are working with DefaultCacheImpl, take a look at config parameters.
Otherwise, are there any exceptions (stack trace), messages (they can be very usefull
if you
enable higher level of logging as DEBUG).
Best regards,
Edson Richter
Thanks for your quick answer, I cheched the OJB.properties file an I
was using DefaultCacheImpl I change it to ObjectCacheEmptyImpl and now
it is working as I was expecting.
Now just to learn the reasons for the previous behaviour:
A comment in OJB.properties:
# The ObjectCacheClass
In real, I'm not an specialist in caches ;), but I've used with success object-cache
..
tag inside class-descriptor, no elsewhere.
I think I've read somewhere that is possible to configure the object-cache for the
connection (or the alias), but I never reade more, and now I'm not sure. Give a
19 matches
Mail list logo
