Thomas Dudziak wrote:
I think the error comes from the XDoclet module, not from Torque.
The problem is that you should not redefine the field in the subclass
I haven't redefined it in the java code, so you think it should not
appear in the repository xml for the subclass?
The usual
Hi Neil,
this is a really strange error, seems that Oracle detect an
objectionable number of bound variables in a prepared statement.
You said that this error message doesn't arise in Resin+Oracle, thus it
can't be a problem of OJB's sql generator.
Does always the same error occur (same sql
Hi Armin,
It always occurs on same sql, and be reproduceable. It seems a code error,
even I doubt the prepared sql statement. However, it works fine in Resin+Oracle.
Is some neccessary configurations missing?
Before occurs the ORA-01008 error, there're some doubtful info in JBosss+Oracle.
But
On 10/26/05, Bernd Laengerich [EMAIL PROTECTED] wrote:
Thomas Dudziak wrote:
I think the error comes from the XDoclet module, not from Torque.
The problem is that you should not redefine the field in the subclass
I haven't redefined it in the java code, so you think it should not
appear
On 10/26/05, Warner Onstine [EMAIL PROTECTED] wrote:
Ok, I'm working on implementing the custom proxy class and am having
some issues. When I try and use my custom Proxy class I get the
following:
Unable to create proxy using class:org.kuali.module.chart.bo.AccountProxy
AccountProxy
Hello there,
we use in one case Informix and the
org.apache.ojb.broker.util.sequence.SequenceManagerHighLowImpl as the sequence
manager.
First it seemed good but then we must realize that we can't create a new record,
if we didn't create a record in the rdbms before using OJB.
So if we want to
Neil Jianguo Zhou wrote:
Hi Armin,
It always occurs on same sql, and be reproduceable. It seems a code error,
even I doubt the prepared sql statement. However, it works fine in Resin+Oracle.
Is the statement generated by OJB or by a user query (if so please post it)?
Does batch-mode=false
Hi Thomas,
Thomas Franke wrote:
Hello there,
we use in one case Informix and the
org.apache.ojb.broker.util.sequence.SequenceManagerHighLowImpl as the sequence
manager.
First it seemed good but then we must realize that we can't create a new record,
if we didn't create a record in the rdbms
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Armin,
Have a look in method
SequenceManagerHighLowImpl#lookupStoreSequence(PersistenceBroker broker,
FieldDescriptor field, String seqName)
this method is called to store/lookup a HighLowSequence instance.
OJB first lookup a
Hello people!
I'm creating a app for a mobile phone/PDA's/Palms. This app connect to
a servlet server and uses request/response to send/get the
information. The client is an AWT frame.
In the server, I'm using Struts to control my servlets and I'm
thinking about to use OJB to control my DAO's.
No one knows what could be causing this error?
-Original Message-
From: Lemke, Wesley [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 25, 2005 12:53 PM
To: OJB Users List
Subject: java.lang.Integer not found in OJB Repository
I am receiving the following error:
Error deleting object
Hi Wes,
seems OJB get the PK object instead the persistent object to delete.
Could you compile the ojb.jar with debug 'on' (call ant jar-debug in
OJB's base directory) so that we get line numbers in stack trace.
regards,
Armin
Lemke, Wesley wrote:
No one knows what could be causing this
Here is the entire stack trace with line numbers (this is OJB 1.0.2):
[10/26/05 10:18:21:951 CDT] 29592959 SystemErr R
com.lmig.pm.affinity.exception.SystemException occurred. Reason: Error
deleting object class com.lmig.pm.affinity.service.StateDiscountUpdater
(caused by:
On 10/26/05, Bernd Laengerich [EMAIL PROTECTED] wrote:
As for the error message, for now you can turn off the XDoclet check
using the checks attribute as described here:#
It's not XDoclet complaining, but Torque, so is this a Torque issue?
The error message and stack trace (with -debug)
Sorry, I didn't get the debug jar in the right directory. Here is the
correct stack trace, and it really has the line number this time!
[10/26/05 10:55:53:579 CDT] 2650265 BaseRuntimeEx W
com.lmig.pm.affinity.exception.BaseRuntimeException
com.lmig.pm.affinity.exception.SystemException
Lemke, Wesley wrote:
Sorry, I didn't get the debug jar in the right directory. Here is the
correct stack trace, and it really has the line number this time!
The most important part of the stack trace seems to be
org.apache.ojb.broker.core.PersistenceBrokerImpl.deleteCollections(Persi
Well, I was hoping that that would do the trick but no dice. I'm still
getting the error that it cannot create a proxy using my proxy class.
org.springframework.orm.ojb.OjbOperationException: OJB operation
failed; nested exception is
org.apache.ojb.broker.PersistenceBrokerException: Unable to
On 10/26/05, Warner Onstine [EMAIL PROTECTED] wrote:
Well, I was hoping that that would do the trick but no dice. I'm still
getting the error that it cannot create a proxy using my proxy class.
snip
Caused by: java.lang.NoSuchMethodException:
Hello,
I'am having trouble trying to find out what i am doing wrong, i have a
class user and a class role and a user has a collection of roles, this
kind of schema is working for other classes with the same kind of
relationship but not for this one.
OJB is trying to insert a null value in
Hi Jean-Yves,
in User the 1:n reference the auto-update setting is undefined and by
default OJB use 'link' for 1:n relations, thus I would expect that the
FK in Admin will be set.
Could you post the generated repository.xml for User, Admin, Role?
regards
Armin
Jean-Yves Sironneau wrote:
Not really sure, I just wiped out the classes directory and rebuilt
completely. Then I opened the class file generated and found the
appropriate method in the class file, so I know it's there (and it's
the only class named AccountProxy).
Just to satisfy my curiosity I set it up through a debugger
here is the extract of the repository file :
Oups i think i forgot to explain that Role is an abstract class, and
that Viewer inherits from Role, Author from Viewer and Admin from Author
here are the classes too :
public class Viewer extends Role {
public Viewer(DocumentBase base) {
Could you try to set auto-update=link in 1:n reference of User and run
your test again:
collection-descriptor
name=roles
element-class-ref=org.jys.clepsydra.data.users.Role
auto-update=link
auto-delete=true
inverse-foreignkey field-ref=userId/
i'am getting the same error.
i'am going to try to do it with a non abstract class maybe it can be that.
Armin Waibel wrote:
Could you try to set auto-update=link in 1:n reference of User and
run your test again:
collection-descriptor
name=roles
Alright so it does appear to have been caused by some weird classpath
issue. But now I'm running into another problem.
org.apache.ojb.broker.PersistenceBrokerException:
org.apache.ojb.broker.PersistenceBrokerException: Error invoking
method toString
at
I have an indirection table foo_bar that happily implements an
m:n relationship between foo and bar. the columns of foo_bar include
foo_id, bar_id, and a unique id for the association itself (mysql
backend, the id column is inserted automatically). This is because it
is relevant to my
On 10/27/05, Warner Onstine [EMAIL PROTECTED] wrote:
Alright so it does appear to have been caused by some weird classpath
issue. But now I'm running into another problem.
org.apache.ojb.broker.PersistenceBrokerException:
org.apache.ojb.broker.PersistenceBrokerException: Error invoking
On 10/27/05, Jason A. Lunn [EMAIL PROTECTED] wrote:
I have an indirection table foo_bar that happily implements an
m:n relationship between foo and bar. the columns of foo_bar include
foo_id, bar_id, and a unique id for the association itself (mysql
backend, the id column is inserted
Jean-Yves Sironneau wrote:
i'am getting the same error.
i'am going to try to do it with a non abstract class maybe it can be that.
I setup a similar test
Implementation odmg = OJB.getInstance();
Database db = odmg.newDatabase();
db.open(null, Database.OPEN_READ_WRITE);
BookShelf bookShelf
So i still don't get it, the workaround is to not use anonymous foreign
key and to set the userId myself...
As i don' t know in OJB where the anonymous key is supposed to be set i
can't really try to find the bug for now, but i'll try to take a look.
Thanks for your help.
Jean-Yves
Hi again,
a correction of my previous post (I don't realized that you use the
odmg-api). In the new upcoming version you have to set
auto-update=none and auto-delete=none or object when using the
odmg-api.
collection-descriptor
name=roles
I can not keep trying right now, but i will tomorrow, the visible
difference i see is that of storing the user i use the way :
Transaction tx = getImplementation().newTransaction();
tx.begin();
db.makePersistent(o);
tx.commit();
But the collections of roles is
On Oct 26, 2005, at 19:00, Thomas Dudziak wrote:
On 10/27/05, Jason A. Lunn [EMAIL PROTECTED] wrote:
I have an indirection table foo_bar that happily implements an
m:n relationship between foo and bar. the columns of foo_bar include
foo_id, bar_id, and a unique id for the association
Hi Armin,
2005/10/26, Armin Waibel [EMAIL PROTECTED]:
Neil Jianguo Zhou wrote:
Hi Armin,
It always occurs on same sql, and be reproduceable. It seems a code error,
even I doubt the prepared sql statement. However, it works fine in
Resin+Oracle.
Is the statement generated by OJB or
Fernando --
OJB can be configured to use Oracle packages/procedures for all CRUD
operations. See
http://db.apache.org/ojb/docu/howtos/howto-work-with-stored-procedures.html
for details on how. As far as using packages/procedures for queries, I
don't think support for that is present, or even
35 matches
Mail list logo
