Hi all�

As i can read, your problem is locates at ojb.properties. Probably when you 
select PersistentField's implemetation to use.
I used to select default implementation, but you can read what are the options 
and what is the best for your project.

Anyway, you can download ojb-blank.war from ojb's homepage, and take this 
project to start yours.

And for your information: 
My ojb.properties PersistentField's implemetation....
--------------------------------------
#----------------------------------------------------------------------------------------
# Meta data / mapping settings
#----------------------------------------------------------------------------------------
# The PersistentFieldClass property defines the implementation class
# for PersistentField attributes used in the OJB MetaData layer.
# By default the best performing attribute/refection based implementation
# is selected (PersistentFieldDirectAccessImpl).
#
# - PersistentFieldDirectAccessImpl
#   is a high-speed version of the access strategies.
#   It does not cooperate with an AccessController,
#   but accesses the fields directly. Persistent
#   attributes don't need getters and setters
#   and don't have to be declared public or protected
# - PersistentFieldPrivilegedImpl
#   Same as above, but does cooperate with AccessController and do not
#   suppress the java language access check (but is slow compared with direct 
access).
# - PersistentFieldIntrospectorImpl
#   uses JavaBeans compliant calls only to access persistent attributes.
#   No Reflection is needed. But for each attribute xxx there must be
#   public getXxx() and setXxx() methods.
# - PersistentFieldDynaBeanAccessImpl
#   implementation used to access a property from a
#   org.apache.commons.beanutils.DynaBean.
# - PersistentFieldAutoProxyImpl
#   for each field determines upon first access how to access this particular 
field
#   (directly, as a bean, as a dyna bean) and then uses that strategy
#
#PersistentFieldClass=org.apache.ojb.broker.metadata.fieldaccess.PersistentFieldDirectAccessImpl
#PersistentFieldClass=org.apache.ojb.broker.metadata.fieldaccess.PersistentFieldPrivilegedImpl
#PersistentFieldClass=org.apache.ojb.broker.metadata.fieldaccess.PersistentFieldIntrospectorImpl
#PersistentFieldClass=org.apache.ojb.broker.metadata.fieldaccess.PersistentFieldDynaBeanAccessImpl
#PersistentFieldClass=org.apache.ojb.broker.metadata.fieldaccess.PersistentFieldAutoProxyImpl
#
# Here are the new upcoming PersistentField implementations. These classes will 
replace the
# 'old' ones on next release. They pass the test-suite, but should be tested by 
community too.
# The new implementations are about 50 times faster in handling nested fields.
PersistentFieldClass=org.apache.ojb.broker.metadata.fieldaccess.PersistentFieldDirectAccessImplNew
#PersistentFieldClass=org.apache.ojb.broker.metadata.fieldaccess.PersistentFieldPrivilegedImplNew
#PersistentFieldClass=org.apache.ojb.broker.metadata.fieldaccess.PersistentFieldIntrospectorImplNew
#PersistentFieldClass=org.apache.ojb.broker.metadata.fieldaccess.PersistentFieldAutoProxyImpl
#PersistentFieldClass=org.apache.ojb.broker.metadata.fieldaccess.PersistentFieldDynaBeanImplNew
#(DynaBean implementation does not support nested fields)
#

--------------------------------------

Best regards. I hope this helps you.




-----Mensaje original-----
De: Bikram B Kapoor [mailto:[EMAIL PROTECTED]
Enviado el: jueves, 25 de noviembre de 2004 11:02
Para: OJB Users List
Asunto: Re: OJB in Tomcat


Hi Morales de Fr�as,
I am new to the Struts+OJB combination (but not new to Struts), somehow I
managed to get hold of Beer4All sample provided at sourceforge and made it
work, but When I try to develop my own package exactly on the same lines and
the same structure I get the following error

[BOOT] ERROR: The specified class
"org.apache.ojb.broker.metadata.PersistentFiel
dDefaultImpl" does not implement the interface
org.apache.ojb.broker.metadata.fi
eldaccess.PersistentField, which is a requirement for the key
"PersistentFieldCl
ass". Using default class class
org.apache.ojb.broker.metadata.fieldaccess.Persi
stentFieldDirectAccessImpl
[org.apache.ojb.odmg.OJB] ERROR: ConfigurableFactory configuration key class
for
 key'ImplementationClass' does not exist.

Since past two days I am not able to figure out what might be the problem I
compared my whole code with that of the sample, its exactly the same. I had
earlier posted the same question Thomas pointed out the location of the
OJB.properties and the repository.xml
/repository_user.xml/repository_internal.xml might not be in the correct
folder but they are (web-inf/classes).
After a lot of googling I found out that this may be due to some error in
the Properties file. I checked that again, but to no result :(

Can anybody please help me solve this problem.

Morales de Fr�as it would be great if you can give me some pointers or some
sample read or write code to DB using struts.

Any help would be greatly appreciated

Thanks
Bikram B Kapoor



----- Original Message ----- 
From: <Morales de Fr�as>; "David" <[EMAIL PROTECTED]>
Newsgroups: gmane.comp.jakarta.ojb.user
Sent: Thursday, November 25, 2004 7:42 PM
Subject: RE: OJB in Tomcat


I have worked with with netBeans 3.5 and 3.6. Struts + ojb + netbean's
tomcat (4 and 5). And i have no problem.

-----Mensaje original-----
De: Edson Carlos Ericksson Richter
[mailto:[EMAIL PROTECTED]
Enviado el: jueves, 25 de noviembre de 2004 12:40
Para: OJB Users List
Asunto: Re: OJB in Tomcat


Have you tryied NetBeans 3.6? I'm using OJB without problems, in
standalone and web apps with 3.6. I know NetBeans 4 B2 has some flaws in
this area... I think you test latest Q build too..

Richter


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
----------------------------------------------------------------------------
---------------------------------------
Este correo electr�nico y, en su caso, cualquier fichero anexo al mismo,
contiene informaci�n de car�cter confidencial exclusivamente dirigida a su
destinatario o destinatarios. Queda prohibida su divulgaci�n, copia o
distribuci�n a terceros sin la previa autorizaci�n escrita de Indra. En el
caso de haber recibido este correo electr�nico por error, se ruega notificar
inmediatamente esta circunstancia mediante reenv�o a la direcci�n
electr�nica del remitente.

The information in this e-mail and in any attachments is confidential and
solely for the attention and use of the named addressee(s). You are hereby
notified that any dissemination, distribution or copy of this communication
is prohibited without the prior written consent of Indra. If you have
received this communication in error, please, notify the sender by reply
e-mail
----- Original Message ----- 
From: <Morales de Fr�as>; "David" <[EMAIL PROTECTED]>
Newsgroups: gmane.comp.jakarta.ojb.user
Sent: Thursday, November 25, 2004 7:42 PM
Subject: RE: OJB in Tomcat


I have worked with with netBeans 3.5 and 3.6. Struts + ojb + netbean's
tomcat (4 and 5). And i have no problem.

-----Mensaje original-----
De: Edson Carlos Ericksson Richter
[mailto:[EMAIL PROTECTED]
Enviado el: jueves, 25 de noviembre de 2004 12:40
Para: OJB Users List
Asunto: Re: OJB in Tomcat


Have you tryied NetBeans 3.6? I'm using OJB without problems, in
standalone and web apps with 3.6. I know NetBeans 4 B2 has some flaws in
this area... I think you test latest Q build too..

Richter


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
----------------------------------------------------------------------------
---------------------------------------
Este correo electr�nico y, en su caso, cualquier fichero anexo al mismo,
contiene informaci�n de car�cter confidencial exclusivamente dirigida a su
destinatario o destinatarios. Queda prohibida su divulgaci�n, copia o
distribuci�n a terceros sin la previa autorizaci�n escrita de Indra. En el
caso de haber recibido este correo electr�nico por error, se ruega notificar
inmediatamente esta circunstancia mediante reenv�o a la direcci�n
electr�nica del remitente.

The information in this e-mail and in any attachments is confidential and
solely for the attention and use of the named addressee(s). You are hereby
notified that any dissemination, distribution or copy of this communication
is prohibited without the prior written consent of Indra. If you have
received this communication in error, please, notify the sender by reply
e-mail


---------------------------------------------------------------------
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]

Reply via email to