Scott Ferguson at caucho fixed it for the next build, but that's not out yet. It works fine in 3.0.4.
R
Thomas Dudziak wrote:
On Sun, 22 Feb 2004, marc salvetti wrote:
Tom, i finally got shell access from my isp, here is the interesting part of the log :
[org.apache.ojb.broker.metadata.RepositoryXmlHandler] DEBUG: > reference-descriptor
[org.apache.ojb.broker.metadata.RepositoryXmlHandler] DEBUG: name: rootMessage
[org.apache.ojb.broker.metadata.RepositoryXmlHandler] DEBUG: class-ref: bo.
ForumMessage
[org.apache.ojb.broker.metadata.RepositoryXmlHandler] DEBUG: proxy: null
[org.apache.ojb.broker.metadata.RepositoryXmlHandler] DEBUG: proxy-prefetching-limit: null
[org.apache.ojb.broker.metadata.RepositoryXmlHandler] DEBUG: refresh: null
[org.apache.ojb.broker.metadata.RepositoryXmlHandler] DEBUG: auto-retrieve: null
[org.apache.ojb.broker.metadata.RepositoryXmlHandler] DEBUG: auto-update: null
[org.apache.ojb.broker.metadata.RepositoryXmlHandler] DEBUG: auto-delete: null
[org.apache.ojb.broker.metadata.RepositoryXmlHandler] DEBUG: otm-dependent: null
[org.apache.ojb.broker.metadata.RepositoryXmlHandler] DEBUG: > foreignkey
[org.apache.ojb.broker.metadata.RepositoryXmlHandler] DEBUG: field-ref: rootMessageID
[org.apache.ojb.broker.metadata.RepositoryXmlHandler] DEBUG: < foreignkey
[org.apache.ojb.broker.metadata.RepositoryXmlHandler] DEBUG: < reference-descriptor
since the default value for auto-retrieve is true, do you think the auto-retrieve:null might be the cause of the problem ?
and if so, is it a resin problem or an ojb problem ?
There seems to be some trouble with parsing the class descriptor (and probably other parts of the configuration) which is likely to be some problem with the combo resin + ojb. Are there other messages from ojb like '... not found, using default values' or somesuch ? If you can, then you should try this with a local installation of resin 3.0.6 (should be no problem as you're allowed to use resin free of charge for development) or if you do not use specific features of resin, another servlet container like jetty or tomcat might do. This will enable you to debug this issue, and you can see where the problem is located (path issues, xml parsing problems etc.).
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
