Hi Carlos!
> ...
> You were wright. The isKey attribute was not there, because the table
> itself did not have that field as a primary key and so, the dbtool did
> not pick that information automaticaly.
> I can now navigate without problems.
> After that, I roamed the User guide doc file and did not find that
> requirement. It should be added !
Maybe this is time to look for someone to maintain the
user manual until Philip comes back.
What about you, Carlos? Could you:
- integrate new chapters written by developers
(Currently Henner and I have written something )
- have a look at the list and add minor extensions
like this one
- Publish the new version as doc as well as pdf
Would not be neccessary to write new chapters yourself.
Joe has to be contacted to be able to do the last task.
Needed Software : Word or Staroffice or OpenOffice
Pdf-Tool like PDFWriter or Destiller or GhostScript
> I propose at least adding to the CommonMistakes "Forgetting to add
> isKey="true" attribute to fields that are referenced in nested forms"
Maybe you could start a FAQ containing CommonMistakes as a section?
Just maintain it and encourage others to send you questions (with answers :) ).
> By the way, is this a problem with nested forms only ?
>
I don't understand the internals enough to answer this question, sorry,
but I did not see this problem anywhere else.
> Now I have another problem. The parent form has maxRows="1" while the
> child form has maxRows="3". However the information in the parent body
> is getting rendered as many times has the child body. This is happening
> with Tomcat 4.1.12 but not with an older version that I have which is
> 4.0.1.
>
> >From one of your latest mails you say that there is a problem with
> taglib pooling in 4.1.x. Is this a manifestation of this problem ?
You _must_ currently deactivate pooling if you use dbforms. You might
have all kinds of strange effects if you do not. Don't oversee if this
is one, looks like not, but who knows?
> Is this a tomcat or a dbforms issue ?
more a dbforms problem, but other libraries face the same problem.
> Can you provide more insight into this ?
>
Mentioned yesterday:
- Correct dbforms to be able to work with
taglib pooling (tomcat 4.1.x)
Detected by Mark Dimon, see
thread [Jdbforms-developers] Anyone else having problems with
tomcat4.1.10 and readonly (2002-09-10)
summary Re: [dbforms] DbForms and Tomcat 4.1.x (2002-09-25)
see Mark's explanations, he pointed out this problem...
The base problem is: Tags have been programmed thinking that method
release() would be called before a tag instance is used again. Within
release() method reinitialization is done. But that is a misunderstanding and
new tomcat has a pooling mechanism that reuses tags without calling
this method. I think according to specs tomcat can do so, the problems
are within the taglibs.
Regards
Dirk
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
_______________________________________________
DbForms Mailing List
http://www.wap-force.net/dbforms
