> From: Christian Haul [mailto:[EMAIL PROTECTED]] > > On 03.Apr.2002 -- 04:04 PM, Jeremy Green wrote: > > I'm using cocoon to generate some forms based on info stored in a db. I > > can also generate a descriptor.xml file for use with the FormValidator > > that works like a charm. The problem is that if the info in the db > > changes, the form is regenerated correctly, but the FormValidator uses > > the descriptor it has cahced from last time instead of reading the new > > one. Is there any way to force the validator to check for a new > > configuration? > > It *should* be reread whenever the file changes. If it doesn't it > appears to be a bug. > > > As a side question: In order to get the validator to find my dynamically > > generated descriptor file, I had to give it a source of > > "http://localhost/whichForm/descriptor.xml";. I tried using "cocoon:/" > > and "context:/", "cocoon://" and "context://", and even "cocoon:///" and > > "context:///", but none of those seem to work. Am I missing something? > > Wait. If you obtain the file this way, that last modification time is > not available AFAIK.
Last modification date is available for cocoon: protocol, and for context also. > In this case it does not reload the file. The > correct URL should be cocoon:/descriptor.xml > IMHO there is a problem with resolving URLs in some actions. I (hope) fixed some issues with descriptor resolving in AbstractComplementaryConfigurableAction and in the form validation logicsheet. > It could > well be that it needs some more investigating. Now it needs testing, no investigating ;) Vadim > > Chris. > > -- > C h r i s t i a n H a u l > [EMAIL PROTECTED] > fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08 --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
